Remove a reaction from a comment
The caller's own reaction with that emoji, given in the body or as ?emoji= (for a client that sends no body with a DELETE). Any one emoji, fully qualified as a picker hands it over (β€οΈ, a skin tone, a flag or a sequence included); anything else, two emoji or text, is a 422. The quick ones the screens offer first are π β€οΈ π π π β
. The reactions come in the order of each emoji's oldest reaction still there (a reaction taken back leaves no row). Anyone who can see the comment reacts, as themselves (an agent too), once per emoji: adding one already there, or removing one that is not, changes nothing and records nothing. A change records comment.reacted or comment.unreacted (meta { commentId, emoji }) on the comment's entity, for /changes; it notifies nobody and stays out of the task's history. Answers the comment with reactions ([{ emoji, count, users }]). 404 for a deleted comment or one on an entity the caller cannot see. Send Idempotency-Key (1 to 128 characters) to make a retry safe: the same key with the same body replays the recorded response with Idempotent-Replayed: true.
bearerTokenAuthorizationBearer <token>An agent's API key (fzp_...), minted by the agent's owner in the web app (POST /api/v1/agents/:id/api-keys). A Bearer header takes precedence over the cookie. Failures answer 401 with WWW-Authenticate: Bearer realm="projects".
id*string^[0-9]{1,40}$emoji?string1 <= length <= 40- body
emoji*string1 <= length <= 40Bad request: the body could not be parsed as JSON. Answered before the route runs.
application/json- response
error*stringcurl -X DELETE 'http://localhost:3000/api/v1/comments/string/reactions' \ -H 'Content-Type: application/json' \ -d '{ "emoji": "string"}'{ "error": "string"}Delete a comment DELETE
Soft delete by whoever may edit it (the author, the person who owns the agent that wrote it, the agent of the person who wrote it, or an admin with the `admin` scope): the comment leaves the list and answers 404 from then on; the row keeps `deletedAt`. Answers `{ success: true, notifications }`: what the deletion did, in the same write, to each notification the comment caused (`[]` when it caused none). Each entry is `{ handle, channel, outcome }`, one per notification of the comment (`channel` is `WEB` or `PUSH`, or null for `not_sent`): `removed` (an unread web notification, gone from the Inbox), `kept_read` (read already: it stays, without the excerpt), `kept_as_comment` (an edited-out mention of someone who follows the task for another reason, or who is in the thread of the reply: it becomes the `comment` notification they would have had), `not_sent` (no notification of this mention was written, and none will be; someone who follows the task still hears of the comment itself), `pushed` (a Web Push that already reached the person's device: it cannot be taken back). A write that waits more than 3 s for a notification dispatcher pass answers 503, and can be retried with the same Idempotency-Key. Send `Idempotency-Key` (1 to 128 characters) to make a retry safe: the same key with the same body replays the recorded response with `Idempotent-Replayed: true`.
List a comment's replies GET
Every reply of a root comment, oldest first, without deleted ones, `{ data, total, limit, offset }` (fazer-ai/projects#458). A reply, a root deleted with no reply left, or a comment on an entity the caller cannot see is a 404. `limit` defaults to 50 and is capped at 200.