Skip to content

Comments API

Comments are threaded discussions on issues. Adding a comment notifies the issue assignee and any @mentioned users.

Endpoints

MethodEndpointDescription
GET/api/projects/{projectId}/issues/{issueId}/commentsList comments
POST/api/projects/{projectId}/issues/{issueId}/commentsCreate a comment
PUT/api/projects/{projectId}/comments/{commentId}Update a comment
DELETE/api/projects/{projectId}/comments/{commentId}Delete a comment

Create Comment

POST /api/projects/{projectId}/issues/{issueId}/comments

Request Fields

FieldTypeRequiredDescription
contentstringYesComment text, max 10,000 characters. Supports Markdown and @mentions.
bash
curl -X POST https://{tenant}.kendo.dev/api/projects/1/issues/42/comments \
  -H "Authorization: Bearer your-token" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "The pagination is working, but we should add a `per_page` parameter. @jasper what do you think?"
  }'
json
{
  "id": 10,
  "content": "The pagination is working, but we should add a `per_page` parameter. @jasper what do you think?",
  "user_id": 1,
  "issue_id": 42,
  "created_at": "2026-03-13T14:00:00.000000Z"
}

Update Comment

PUT /api/projects/{projectId}/comments/{commentId}

Request Fields

FieldTypeRequiredDescription
contentstringYesUpdated comment text, max 10,000 characters
bash
curl -X PUT https://{tenant}.kendo.dev/api/projects/1/comments/10 \
  -H "Authorization: Bearer your-token" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "The pagination is working. Added a `per_page` parameter in the follow-up PR."
  }'
json
{
  "id": 10,
  "content": "The pagination is working. Added a `per_page` parameter in the follow-up PR.",
  "user_id": 1,
  "issue_id": 42,
  "created_at": "2026-03-13T14:00:00.000000Z"
}

Delete Comment

DELETE /api/projects/{projectId}/comments/{commentId}

Returns 204 No Content on success.

bash
curl -X DELETE https://{tenant}.kendo.dev/api/projects/1/comments/10 \
  -H "Authorization: Bearer your-token"

See Also