List a task's comments
The root comments, oldest first, { data, total, limit, offset }: total, limit and offset count roots. Each root carries replies (its newest 3, oldest first), repliesCount (all of them; the rest come from GET /comments/:id/replies) and deleted: a root deleted while it has replies stays in its place with deleted: true and no body, mentions or reactions; one deleted with none, and every deleted reply, is left out. Every comment has parentId, the root it answers or null. limit defaults to 50 and is capped at 200. An entity the caller cannot see is a 404.
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}$limit?|11 <= value <= 200offset?|10 <= value <= 9007199254740991Unauthorized: missing or invalid credentials.
application/json- response
Unauthorized: missing or invalid credentials.
error*stringcurl -X GET 'http://localhost:3000/api/v1/tasks/string/comments'{ "error": "string"}List a project's comments GET
The root comments, oldest first, `{ data, total, limit, offset }`: `total`, `limit` and `offset` count roots. Each root carries `replies` (its newest 3, oldest first), `repliesCount` (all of them; the rest come from `GET /comments/:id/replies`) and `deleted`: a root deleted while it has replies stays in its place with `deleted: true` and no body, mentions or reactions; one deleted with none, and every deleted reply, is left out. Every comment has `parentId`, the root it answers or null. `limit` defaults to 50 and is capped at 200. An entity the caller cannot see is a 404.
Edit a comment PATCH
The author, the person who owns the agent that wrote it, the agent of the person who wrote it (not a sibling agent of the same owner), or an admin (the `admin` scope of the credential) rewrites the body: 403 for anyone else, 404 for a deleted comment or one on an entity the caller cannot see. Stamps `editedAt` and `editedBy` and reads the mentions again; only a mention the edit ADDS subscribes that user and goes in `meta.mentionedUserIds` of `comment.updated`. The same body again changes nothing and records nothing. Answers the comment with `notifications`: what the mentions the edit took out did to the notifications they had caused, in the same write (`[]` when no mention was taken out). 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`.