Bot is allowed — every endpoint on this page accepts bot authentication via the
Authorization: <user_id> <token> header. See the Bots guide.The Reaction Object
Every reaction endpoint returns one or more reaction objects with the following fields.A message can have at most 50 reactions across all users and emoji. Reacting with the same emoji you have already used on a message is a no-op — the server returns your existing reaction without creating a duplicate.
Endpoints
Fetch reactions — POST /api/reactions/get
Returns all reactions for one or more messages in a single request. You can pass a single message ID or an array of up to 200 IDs; the response is keyed by message ID string so you can merge it into your local state efficiently.
Request body
Batch of message IDs to fetch reactions for. Mutually exclusive with
id. Maximum 200 IDs per request.Single message ID. Use this as a shorthand when you only need one message. Ignored when
ids is present.200
An object whose keys are message ID strings and whose values are arrays of reaction objects.
Add a reaction — POST /api/reaction/create
Adds an emoji reaction to a message. If you have already reacted with that emoji, the server returns the existing reaction unchanged (idempotent).
Request body
Response 200 — the reaction object.
Remove a reaction — POST /api/reaction/delete
Deletes a reaction you own. You can identify the reaction either by its row id (option A) or by the combination of message + emoji (option B) — useful when your UI stores the emoji but not the reaction row ID.
Request body — option A (by reaction ID)
Request body — option B (by message + emoji)
Response 200 — "Success"
Error responses
Real-Time Events
Clody pushes reaction changes over Socket.IO on the main/ namespace. You receive these events only for channels you are a member of.