Notifications API: Mentions, Thread Replies, Tasks, and the Signed-in User's Inbox

A Notification tells one User that something in an Organization needs their attention. Each User has their own Notifications in each Organization they belong to. The app shows them in the Bandeja, a page of the Organization below Chat in the sidebar, with a badge that counts the unread ones. The sidebar offers Chat and Bandeja both in an Entity and in Grupo. A Notification has one of four kinds:

`kind`	When you get it	In the Bandeja
`mention`	Another Member mentioned you in a message of the Organization’s Chat or in a reply of an ERP Thread.	”Autor te mencionó”, over the message that mentions you.
`thread_reply`	Someone replied in an ERP Thread you take part in, without mentioning you.	”Autor respondió en un hilo en el que participas”, naming the reply’s author.
`task_assigned`	Another Member assigned you a Task.	The Task’s text, over “Autor te la asignó”, or “Te la asignaron” when that Member’s account no longer exists.
`task_overdue`	The due date of a Task assigned to you passed and the Task isn’t completed. See Task Notifications.	The Task’s text, over “Venció el fecha”.

More kinds may come later, so read kind before you read the rest of a Notification. Every Role can use the routes on this page, viewer included. Only staff and client Members are assigned Tasks, so only they get the two Task kinds. Each route reads or marks only the caller’s own Notifications: the User of the session or of the API key.

Open in the app. This resource has a page in the Sintropix web app at https://app.sintropix.com/organizations/{organizationId}/notifications, where each id in braces is the same UUID as in the API route or response. It shows the signed-in User's Notifications in the Organization. Opening a Notification marks it read and opens its target: the Chat on that message's ERP Thread, or the Task in Tareas. The old /{entityId}/notifications and /{entityId}/chat URLs no longer open. When you mention a record to a user, include that link. See Link to the App for the full URL grammar.

Mention a Member

To mention a Member, write the token <@userId> in the text of a message you send with POST /organizations/:organizationId/chat/messages. The app writes the same token when you pick a name after typing @, and draws it as the Member’s name.

{
  "id": "4f1d8a2c-6b9e-4c3a-8d7f-2e5b1a9c0d64",
  "parentMessageId": null,
  "text": "<@5e8a1c3f-2b7d-4f9e-8a6c-0d4b2e7f1a93> ¿puedes revisar la factura 10452?"
}

When the message is saved, each User it mentions gets one mention Notification, even when the message names them more than once. These rules apply:

Mention only other Members of the Organization. You can’t mention yourself.
A message that breaks a rule is refused with 422 and saves nothing, neither the message nor any Notification.

Status	`code`	`params`	When
`422`	`ERP_MESSAGE_MENTION_OF_SELF_ERROR`	`{}`	The message mentions its author.
`422`	`ERP_MESSAGE_MENTION_OF_NON_MEMBER_ERROR`	`{ userId }`	The message mentions a User with no Membership in the Organization, for example someone removed after you read the Members.

In the app, type @ and pick a name, or type the name in full: @erwin, a Member’s full name, or their first name. Case and accents don’t matter. The typed name becomes the mention when a space or punctuation follows it, or when you send, as long as exactly one Member answers to it. A name that several Members share stays plain text.

GET `/api/organizations/:organizationId/chat/members`

List the Members a message can mention, ordered by name. Leave yourself out when you offer the list to the author. Response 200: an array of { userId, name }.

curl "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/chat/members" \
  -H "x-api-key: $SINTROPIX_API_KEY"

Follow the ERP Threads you take part in

When someone replies in an ERP Thread, its Participants get a thread_reply Notification, even when nobody tagged them. It works like following a thread in Slack. You don’t follow a thread by hand: you become a Participant by taking part. The Participants of an ERP Thread are:

The author of its first message.
Everyone who has replied in it.
Everyone mentioned in any of its messages.

Only current Members of the Organization count. These rules apply when a reply is sent:

The author of the reply gets no Notification.
A Participant the reply mentions gets only the mention, not a second Notification.
Each User gets at most one Notification per message.
Erwin is never a Participant. His answer in an ERP Thread notifies its Participants once, when his text arrives, not while he shows his progress. A later edit of his answer doesn’t notify again.

Talk about a record in its ERP Thread

An Invoice, a Bank Movement, or a Ledger Entry has at most one ERP Thread: the conversation about that record. It’s an ordinary ERP Thread of the Organization’s Chat, so mentions, thread_reply Notifications, and tagging Erwin work in it as anywhere else in the Chat. In the app, open the panel of an Invoice or a Bank Movement and click its Hilo tab, or scroll to the Hilo section of a Ledger Entry’s page. The first message about the record starts its ERP Thread, and later messages reply in it. In the Chat, the first message of a record’s ERP Thread shows a card with the record, and the card opens it. To write about a record through the API, send record instead of a parentMessageId in POST /organizations/:organizationId/chat/messages. You name the record, never the first message: when the record has no ERP Thread yet, the message starts it, and otherwise it becomes a reply in it.

Field	Type	Required	Description
`id`	uuid	Yes	Client-generated message id.
`parentMessageId`	null	Yes	Must be `null` when you send `record`. A message names a parent or a record, never both.
`text`	string	Yes	The message, with `<@userId>` for each mention and `<@erwin>` to tag Erwin.
`record`	object or null	No	The record the message is about: `{ kind, entityId, id }`. `kind` is `invoice`, `bank_movement`, or `ledger_entry`. `entityId` is the record’s Entity, which must belong to the Organization, and `id` is the record’s id. Defaults to `null`, a message about no record.

curl -X POST "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/chat/messages" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "8b2e4f1a-3c5d-4e7f-9a1b-2c3d4e5f6a7b",
    "parentMessageId": null,
    "text": "Confirmé con el proveedor: la OC corresponde a este mes.",
    "record": {
      "kind": "invoice",
      "entityId": "0192a8b4-0000-7000-8000-000000000010",
      "id": "0192a8b4-0000-7000-8000-000000000042"
    }
  }'

Response (201): the ERP Message. The first message of a record’s ERP Thread carries the record in entityId and in one of invoiceId, bankMovementId, or ledgerEntryId, and its parentMessageId is null. A reply carries the first message’s id in parentMessageId, and its record fields are null.

Status	`code`	`params`	When
`400`	—	—	The message sends both a `parentMessageId` and a `record`.
`404`	`ERP_MESSAGE_RECORD_NOT_FOUND_ERROR`	`{ kind, recordId }`	The record doesn’t exist in that Entity, or the Entity isn’t one of the Organization’s.

Deleting a record deletes its ERP Thread with it. The Invoice and Bank Movement listings filter by erpThread: with keeps only the records that have an ERP Thread, and without only those with none. Each row carries hasErpThread. See GET /invoices/pages and GET /movements.

Task Notifications

Tasks notify their assignee:

Assigned. Assigning a Task to another staff or client Member sends them a task_assigned Notification that names who assigned it. Assigning yourself, saving the same assignee again, or unassigning notifies nobody.
Overdue. Just after midnight in Santiago (Chile) time, Sintropix sends a task_overdue Notification for each assigned Task whose due date has passed and that isn’t completed. Each Task notifies once per due date. If you move the due date and the new one passes too, the assignee is notified again. A change of assignee doesn’t send a new overdue Notification.

Opening a Task Notification in the app marks it read and opens the Task in Tareas. Deleting the Task deletes its Notifications.

The Notification object

Field	Type	Description
`id`	UUID	Notification id.
`kind`	string	`mention`, `thread_reply`, `task_assigned`, or `task_overdue`.
`readAt`	ISO datetime or null	When the User first read it. `null` while unread.
`createdAt`	ISO datetime	When the Notification was written.
`message`	object	On a `mention`, the message that mentioned the User. On a `thread_reply`, the reply. See below. Absent on the Task kinds.
`task`	object	On a `task_assigned` or `task_overdue`, the Task as `{ id, text }`. Absent on the message kinds.
`actorName`	string or null	On a `task_assigned` only: the name of the Member who assigned the Task. `null` when their account no longer exists.
`dueDate`	string	On a `task_overdue` only: the due date that passed, `YYYY-MM-DD`. It keeps that date when the Task’s due date later moves.

The message object carries:

Field	Type	Description
`id`	UUID	The message id.
`text`	string	The message text, with each mention as a `<@userId>` token.
`parentMessageId`	UUID or null	The main Chat message the reply answers, or `null` for a message of the main Chat.
`byErwin`	boolean	Whether Erwin wrote the message.
`authorName`	string	Name of the Member who wrote it, or Erwin’s when `byErwin` is `true`.
`mentionedUserIds`	array of UUID	The Users the message mentions.
`mentionedUserNames`	array of string	Their names, in the same order as `mentionedUserIds`. Use them to draw each token as a name.
`createdAt`	ISO datetime	When the message was sent.

{
  "id": "a3c7e9b1-2d4f-4a6c-8e0b-5f1d3a7c9e28",
  "kind": "mention",
  "readAt": null,
  "createdAt": "2026-10-24T15:20:04.512Z",
  "message": {
    "id": "4f1d8a2c-6b9e-4c3a-8d7f-2e5b1a9c0d64",
    "text": "<@5e8a1c3f-2b7d-4f9e-8a6c-0d4b2e7f1a93> ¿puedes revisar la factura 10452?",
    "parentMessageId": null,
    "byErwin": false,
    "authorName": "Tomás Fuentes",
    "mentionedUserIds": ["5e8a1c3f-2b7d-4f9e-8a6c-0d4b2e7f1a93"],
    "mentionedUserNames": ["Camila Rojas"],
    "createdAt": "2026-10-24T15:20:04.498Z"
  }
}

A Task Notification carries the Task instead of a message:

{
  "id": "e2b9c4a1-7d3f-4e6a-9b8c-1f0d2a5e7c36",
  "kind": "task_overdue",
  "readAt": null,
  "createdAt": "2026-10-31T03:05:12.204Z",
  "task": {
    "id": "7c1e4b2a-9d3f-4a6e-8b0c-5f2d1e7a9c34",
    "text": "Ask the supplier for the credit note"
  },
  "dueDate": "2026-10-30"
}

GET `/api/organizations/:organizationId/notifications`

List your Notifications in the Organization, newest first, one page at a time. Query parameters

Parameter	Type	Required	Description
`cursor`	UUID	No	The `nextCursor` of the previous page. Omit it for the first page.
`limit`	integer	No	Page size, 1 to 100. Defaults to 50.

Response 200: { notifications, nextCursor }. notifications is an array of Notification objects. nextCursor is the id to pass as cursor for the next page, or null on the last page. A cursor that isn’t one of your Notifications returns 404 with NOTIFICATION_NOT_FOUND_ERROR.

curl "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/notifications?limit=20" \
  -H "x-api-key: $SINTROPIX_API_KEY"

GET `/api/organizations/:organizationId/notifications/unread-count`

Count your unread Notifications in the Organization. Response 200: { "unreadCount": integer }.

POST `/api/organizations/:organizationId/notifications/:notificationId/read`

Mark one of your Notifications read. Marking it again keeps the first readAt. Response 200: the Notification object. A Notification that doesn’t exist, or that belongs to another User, returns 404 with NOTIFICATION_NOT_FOUND_ERROR.

curl -X POST "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/notifications/$NOTIFICATION_ID/read" \
  -H "x-api-key: $SINTROPIX_API_KEY"

POST `/api/organizations/:organizationId/notifications/read-all`

Mark every unread Notification of yours in the Organization read. This is Marcar todo como leído in the app. Response 200: an array of the Notification objects this call marked read, newest first. It is empty when nothing was unread.

Errors

Status	`code`	`params`	When
`404`	`NOTIFICATION_NOT_FOUND_ERROR`	`{ notificationId }`	The Notification, or the `cursor`, isn’t one of yours in the Organization.

Status codes

Code	Meaning
`200`	Success.
`400`	Validation error, such as a `limit` outside 1 to 100.
`401`	Unauthenticated.
`404`	Notification not found, or no Membership in the Organization.
`422`	A Chat message mentions its author or a non-Member.
`429`	Rate limit exceeded (25,000 requests per hour per API key).

Get Started

Ledger

Banking

Documents

Reports & Audit

Sources & Integrations

Platform

Notifications API: Mentions, Thread Replies, Tasks, and the Signed-in User's Inbox

Mention a Member

GET `/api/organizations/:organizationId/chat/members`

Follow the ERP Threads you take part in

Talk about a record in its ERP Thread

Task Notifications

The Notification object

GET `/api/organizations/:organizationId/notifications`

GET `/api/organizations/:organizationId/notifications/unread-count`

POST `/api/organizations/:organizationId/notifications/:notificationId/read`

POST `/api/organizations/:organizationId/notifications/read-all`

Errors

Status codes

​Mention a Member

​GET /api/organizations/:organizationId/chat/members

​Follow the ERP Threads you take part in

​Talk about a record in its ERP Thread

​Task Notifications

​The Notification object

​GET /api/organizations/:organizationId/notifications

​GET /api/organizations/:organizationId/notifications/unread-count

​POST /api/organizations/:organizationId/notifications/:notificationId/read

​POST /api/organizations/:organizationId/notifications/read-all

​Errors

​Status codes

Mention a Member

GET `/api/organizations/:organizationId/chat/members`

Follow the ERP Threads you take part in

Talk about a record in its ERP Thread

Task Notifications

The Notification object

GET `/api/organizations/:organizationId/notifications`

GET `/api/organizations/:organizationId/notifications/unread-count`

POST `/api/organizations/:organizationId/notifications/:notificationId/read`

POST `/api/organizations/:organizationId/notifications/read-all`

Errors

Status codes