Kitsu’s notification system keeps users informed about comments, mentions, task assignments, and replies on tasks they’re involved with.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/cgwire/zou/llms.txt
Use this file to discover all available pages before exploring further.
Notification Types
Notifications are created automatically for various events:comment- New comment on a subscribed taskmention- User mentioned in a commentreply- Reply to a comment threadreply-mention- User mentioned in a replyassignation- Task assigned to userplaylist-ready- Playlist ready for client review
Get User Notifications
Query Parameters
Filter notifications created after this date (ISO 8601 format)
Filter notifications created before this date (ISO 8601 format)
Filter by task type UUID
Filter by task status UUID
Filter by notification type (comment, mention, reply, assignation, etc.)
Filter by read status (true for read, false for unread)
Filter by watching status
Example Requests
Response
Array of notification objects
Notification UUID
Notification type (comment, mention, reply, assignation, etc.)
Whether the notification has been read
Whether this notification represents a status change
UUID of the person who triggered the notification
UUID of the notification recipient
UUID of the related comment (if applicable)
UUID of the related reply (if applicable)
UUID of the related task
UUID of the related playlist (for playlist-ready notifications)
Notification creation timestamp (ISO 8601)
Last update timestamp (ISO 8601)
Example Response
Get Specific Notification
Path Parameters
UUID of the notification
Example Request
cURL
Response
Update Notification
Path Parameters
UUID of the notification
Request Body
Mark notification as read (true) or unread (false)
Example Requests
Response
Mark All Notifications as Read
Example Requests
Response
Task Subscriptions
Users can subscribe to tasks to receive notifications about comments and changes.Check Task Subscription
Path Parameters
UUID of the task
cURL
Response
Subscribe to Task
Path Parameters
UUID of the task to subscribe to
Response
Unsubscribe from Task
Path Parameters
UUID of the task to unsubscribe from
Response
Returns HTTP 204 No Content on success.Sequence Subscriptions
Subscribe to all tasks of a specific type within a sequence.Check Sequence Subscription
Path Parameters
UUID of the sequence
UUID of the task type
cURL
Subscribe to Sequence
Path Parameters
UUID of the sequence
UUID of the task type
cURL
Unsubscribe from Sequence
cURL
Get Sequence Subscriptions
Path Parameters
UUID of the project
UUID of the task type
cURL
Response
Real-time Notification Events
When a new notification is created, a real-time event is emitted through the WebSocket event stream:How Notifications Are Created
Comment Notifications
When a comment is posted on a task:- All users assigned to the task receive a notification
- All users subscribed to the task receive a notification
- All users subscribed to the parent sequence (if applicable) receive a notification
- The comment author does not receive a notification
Mention Notifications
When a user is @mentioned in a comment or reply:- The mentioned user receives a
mentionorreply-mentionnotification - An email is sent to the mentioned user (if email notifications are enabled)
Assignment Notifications
When a task is assigned:- Each assigned user receives an
assignationnotification - An email is sent to the assigned users (if email notifications are enabled)
- The assigner does not receive a notification for their own assignment
Playlist Ready Notifications
When a playlist is marked as ready for client review:- All clients with access to the project receive a
playlist-readynotification - Optionally filtered by studio and/or department
- An email is sent to notify clients
Best Practices
-
Poll for New Notifications: If not using WebSockets, poll the
/data/user/notifications?read=falseendpoint periodically (e.g., every 30-60 seconds) to check for new notifications. - Mark as Read Promptly: When a user views a notification or the related content, mark it as read to keep the notification list clean.
- Use Bulk Operations: Use the mark-all-as-read endpoint when appropriate rather than updating notifications one by one.
- Filter Intelligently: Use query parameters to fetch only relevant notifications based on context (e.g., only unread, specific task type).
- Subscribe to Relevant Tasks: Encourage users to subscribe to tasks they’re interested in to stay informed without being overwhelmed.
- WebSocket Integration: Use the WebSocket event stream for real-time notification delivery in the UI for the best user experience.