EaserixDocs
DevelopersAPI referenceTasksComments

Delete a comment (author, or a workspace admin)

The comment's author may delete it, and so may a moderator — someone holding org.teams.manage, or leading the team the comment's issue belongs to. That is the path for removing a comment nobody else can, such as one carrying a pasted credential. Note the asymmetry with updateComment, which stays author-only with no override: an administrator may REMOVE someone's words but never rewrite them, because an edited comment still carries the original author's name. A moderator deletion is recorded in the audit log as `comment.moderated`; deleting your own is not, since that is ordinary use and would bury the entries that matter. Reach is bounded by the comment's issue, so a comment in another workspace is 404 for everyone including an admin — never 403, which would confirm the id names a real comment somewhere.

View as Markdown
DELETE
/v1/comments/{id}

Authorization

bearer
AuthorizationBearer <token>

In: header

Path Parameters

id*string
Formatuuid

Response Body

application/json

application/json

application/json

application/json

curl -X DELETE "https://example.com/v1/comments/497f6eca-6276-4993-bfeb-53cbbbba6f08"
{  "message": "string"}

Edit a comment (author-only)

Only the comment's author may edit it — anyone else in the org gets 403 ("only the author can edit a comment"), an administrator included. Unlike deleteComment there is deliberately NO moderator override here: removing someone's words is moderation, rewriting them under their own name is not. Editing sets the comment's modified timestamp (null until first edit — the "(edited)" marker).

List an issue's activity history

Property-change entries, oldest first, capped at 500, with the actor embedded. from/to hold raw values (ids, numbers, dates) that clients resolve for display.