Add a comment

POST /v1/feedback/:id/comments

Adds a comment to a ticket. Requires the vibe:feedback scope. Attachments can be added to a comment. No more than 20 comments per minute per key owner.

Parameters

Request fields (body)

Examples

curl — personal key

curl -X POST https://vibecode.bitrix24.com/v1/feedback/a1b2c3d4-1111-2222-3333-444455556666/comments \
  -H "X-Api-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "body": "Reproduced on an empty filter, attached the request log." }'

curl — OAuth application

curl -X POST https://vibecode.bitrix24.com/v1/feedback/a1b2c3d4-1111-2222-3333-444455556666/comments \
  -H "X-Api-Key: YOUR_APP_KEY" \
  -H "Authorization: Bearer USER_SESSION_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "body": "Reproduced on an empty filter, attached the request log." }'

JavaScript — personal key

const res = await fetch(
  'https://vibecode.bitrix24.com/v1/feedback/a1b2c3d4-1111-2222-3333-444455556666/comments',
  {
    method: 'POST',
    headers: { 'X-Api-Key': 'YOUR_API_KEY', 'Content-Type': 'application/json' },
    body: JSON.stringify({ body: 'Reproduced on an empty filter, attached the request log.' }),
  },
)
const { data } = await res.json()

JavaScript — OAuth application

const res = await fetch(
  'https://vibecode.bitrix24.com/v1/feedback/a1b2c3d4-1111-2222-3333-444455556666/comments',
  {
    method: 'POST',
    headers: {
      'X-Api-Key': 'YOUR_APP_KEY',
      'Authorization': 'Bearer USER_SESSION_TOKEN',
      'Content-Type': 'application/json',
    },
    body: JSON.stringify({ body: 'Reproduced on an empty filter, attached the request log.' }),
  },
)
const { data } = await res.json()

Response fields

Response example

{
  "success": true,
  "data": {
    "id": "61ae2a00-a7ac-416f-85cc-99873c767d3b",
    "authorType": "USER",
    "body": "Reproduced on an empty filter, attached the request log.",
    "createdAt": "2026-04-19T11:00:00.000Z",
    "feedbackStatus": "AWAITING_USER",
    "previousStatus": "NEW"
  }
}

Error response example

403 — comment without the vibe:feedback scope:

{
  "success": false,
  "error": {
    "code": "FEEDBACK_SCOPE_REQUIRED",
    "message": "Requires management key or vibe:feedback scope"
  }
}

Errors

For the full list of common API errors, see Errors.

Known specifics

A comment can change the status. By default a comment moves the ticket to AWAITING_USER. To set a different status, pass status in the body — values as in update. The feedbackStatus and previousStatus fields in the response show the status after and before the comment.

The author comments on their own ticket without the scope. If the request uses the same key that created the ticket, the comment passes without the vibe:feedback scope: the author check runs before the scope check. The scope is only needed for comments on other people's tickets.

Authorship is the person, not the key. A ticket created by another of your keys, or filed from your Vibecode account, is also yours: the comment is recorded as a user message (authorType: USER), the resolution field is not overwritten, and a supplied status is ignored — statuses are changed through update. One condition: such a key needs the vibe:feedback scope — without the scope, only the key that created the ticket counts as yours. Application keys and management keys fall outside this rule entirely: for them, the key owner and the person writing are different people.

An author comment brings a resolved ticket back into the queue. If the ticket is RESOLVED, your comment moves it to NEEDS_REVIEW and clears the closure stamp (resolvedAt, resolvedBy). The resolution text is kept. ARCHIVED and WITHDRAWN stay closed — they still answer 409 FEEDBACK_CLOSED.

An author comment changes the status only where a reply was awaited. Out of AWAITING_USER the ticket moves to NEEDS_REVIEW. On the other open statuses — NEW, REVIEWING, NEEDS_REVIEW — the status is preserved: the triage is the team's anyway. The updatedAt field is refreshed in any case, so a queue sorted by it will show a fresh reply regardless of status.

Only a closing comment fills resolution. A comment with a target status of RESOLVED or ARCHIVED writes its body into resolution; with any other status the field is left alone. The text of such a comment still reaches the author by email and is visible in the thread.

See also

• Get a ticket
• Update a ticket
• Upload an attachment
• Feedback