The Notifications API surfaces in-app messages delivered to a user’s inbox. Messages are created by system events (task validations, invalidations, project broadcasts, team invitations, and more) and can also be sent directly by project managers or team managers. All endpoints require an authenticated session — each user can only read and manage their own messages.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/hotosm/tasking-manager/llms.txt
Use this file to discover all available pages before exploring further.
Notification Resources
List Notifications
GET /api/v2/notifications/
Returns a paginated list of messages for the authenticated user. Supports filtering by message type, sender, project, task, and read status, as well as configurable sort order.
Authentication: Required
Query Parameters
Filter by message type integer. Accepted values:
| Value | Type |
|---|---|
1 | System |
2 | Broadcast |
3 | Mention |
4 | Validation |
5 | Invalidation |
6 | Request team |
7 | Invitation |
8 | Task comment |
9 | Project chat |
10 | Project Activity |
11 | Team broadcast |
Filter messages sent from a specific username.
Filter messages associated with a specific project (by project ID or name).
Filter messages associated with a specific task ID.
Filter by read status. Accepted values:
read or unread.Field to sort results by. Options:
date, read, project_id, message_type.Sort direction:
asc or desc.Page number.
Number of results per page.
200 OK
Get a Single Notification
GET /api/v2/notifications/{message_id}/
Retrieves a single message by its ID. The message must belong to the authenticated user.
Authentication: Required
Path Parameters
The unique numeric message ID.
200 OK
| Status | Meaning |
|---|---|
403 | Message does not belong to the authenticated user |
404 | Message not found |
Delete a Notification
DELETE /api/v2/notifications/{message_id}/
Permanently deletes a single message. The message must belong to the authenticated user.
Authentication: Required
Path Parameters
The unique numeric message ID.
200 OK
| Status | Meaning |
|---|---|
403 | Message does not belong to the authenticated user |
404 | Message not found |
Notification Actions
Count Unread Notifications
GET /api/v2/notifications/queries/own/count-unread/
Returns the number of unread messages for the authenticated user since their last notification check. This is the lightweight endpoint intended for polling notification badges in the UI.
Authentication: Required
Response 200 OK
Update Notification Timestamp
POST /api/v2/notifications/queries/own/post-unread/
Updates the notification checkpoint datetime for the authenticated user, effectively resetting the unread counter baseline. Call this endpoint after the user opens their notification inbox.
Authentication: Required
Response 200 OK — returns the updated notification record.
Bulk Delete Notifications
DELETE /api/v2/notifications/delete-multiple/
Deletes a specified set of messages for the authenticated user in a single transactional operation. Only messages owned by the requesting user are deleted.
Authentication: Required
Request Body
Array of integer message IDs to delete.
200 OK
If
messageIds is empty the request succeeds immediately without modifying any data.Delete All Notifications
DELETE /api/v2/notifications/delete-all/
Deletes all messages for the authenticated user. An optional messageType filter can be supplied to delete only messages of a specific type.
Authentication: Required
Query Parameters
Optional message-type integer. When supplied, only messages of that type are deleted. Omit to delete all messages.
200 OK
Mark All Notifications as Read
POST /api/v2/notifications/mark-as-read-all/
Marks all messages for the authenticated user as read. An optional messageType filter limits the operation to a specific message type.
Authentication: Required
Query Parameters
Optional message-type integer. When supplied, only messages of that type are marked as read.
200 OK
Mark Multiple Notifications as Read
POST /api/v2/notifications/mark-as-read-multiple/
Marks a specific set of messages as read for the authenticated user.
Authentication: Required
Request Body
Array of integer message IDs to mark as read.
200 OK
Data Models
Unique numeric identifier for the message.
Subject line of the notification.
Full body text of the notification.
User ID of the sender.
Username of the sender.
Avatar URL of the sender.
ID of the related project, if applicable.
Title of the related project, if applicable.
ID of the related task, if applicable.
Human-readable message type label (e.g.
Validation, Broadcast, Invitation).ISO 8601 timestamp indicating when the message was sent.
Whether the authenticated user has read the message.