Feedback

A programmatic feedback channel for Vibecode. AI models, integrations, and external tools submit bug reports, suggestions, and questions straight from code — with error context, environment, and reproduction steps. Tickets submitted through the API land in the same tracker as those from the form in your Vibecode account.

Base URL: https://vibecode.bitrix24.com/v1 | Authorization: X-Api-Key

Access levels | Quick start | Full example | Endpoint reference | Error codes

Access levels

Permissions depend on whether the key has the vibe:feedback scope.

The vibe:feedback scope is not granted to a key automatically — enable it explicitly when creating or updating a key. The scope grants extended read and update access to every ticket in the account, not just the ones the key created. Grant it selectively — for example, to a key that processes the support ticket queue.

Quick start

Submitting a bug ticket with request context:

curl -X POST https://vibecode.bitrix24.com/v1/feedback \
  -H "X-Api-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "category": "BUG",
    "title": "POST /v1/deals/search returns 500 on empty filter",
    "body": "Calling POST /v1/deals/search with body {\"filter\":{}} gives a 500. Expected an empty array or 400.",
    "context": {
      "endpoint": "/v1/deals/search",
      "request": {"filter": {}},
      "httpStatus": 500,
      "requestId": "req_abc123"
    }
  }'

Response:

{
  "success": true,
  "data": {
    "id": "a1b2c3d4-1111-2222-3333-444455556666",
    "category": "BUG",
    "title": "POST /v1/deals/search returns 500 on empty filter",
    "status": "NEW",
    "createdAt": "2026-04-19T10:30:00.000Z"
  }
}

The ticket number the user and support see is VB- plus the first 8 characters of the id. In the example above that is VB-a1b2c3d4. Save it so you can reference the ticket in correspondence.

Full example

Submit a ticket, verify it in the list, and withdraw it if it was created by mistake.

const BASE = 'https://vibecode.bitrix24.com/v1'
const headers = { 'X-Api-Key': 'YOUR_API_KEY', 'Content-Type': 'application/json' }

// 1. Submit a ticket
const created = await fetch(`${BASE}/feedback`, {
  method: 'POST',
  headers,
  body: JSON.stringify({
    category: 'DOCS',
    title: 'Typo in the filtering section',
    body: 'The example on /docs/filtering is missing a closing bracket.',
  }),
}).then(r => r.json())

const ticketId = created.data.id
console.log('Ticket created:', 'VB-' + ticketId.slice(0, 8))

// 2. Find it in your list
const list = await fetch(`${BASE}/feedback?category=DOCS&limit=5`, { headers })
  .then(r => r.json())
console.log('Total DOCS tickets:', list.total)

// 3. Withdraw it if created by mistake
await fetch(`${BASE}/feedback/${ticketId}`, {
  method: 'PATCH',
  headers,
  body: JSON.stringify({ status: 'WITHDRAWN' }),
})

Endpoint reference

Windows / PowerShell and UTF-8

Non-ASCII characters (accented letters such as ö, ü, é, or any non-Latin script) in title, body, or resolution may turn into question marks (?) if the request is sent from Windows PowerShell without explicit UTF-8 serialization. This is not a server-side display problem — the non-ASCII bytes are lost before the HTTP request is sent, on the client side.

Cause. By default, PowerShell re-encodes the string from the -Body parameter (Invoke-WebRequest / Invoke-RestMethod) into the system's legacy (non-UTF-8) code page — for example windows-1252 on Western installs — and any character outside that page is lost before the request is assembled. The Content-Type: charset=utf-8 header does not help here — by the time it applies, the original bytes are already lost.

Solution. Pass the request body as a UTF-8 byte array.

# 1. Console output encoding — does not affect how the body is encoded
[Console]::OutputEncoding = [System.Text.Encoding]::UTF8

# 2. Build the JSON and convert it to a UTF-8 byte array
$body = @{
  category = 'DOCS'
  title    = 'Typo in the documentation'
  body     = 'The filtering section example is missing a closing bracket.'
} | ConvertTo-Json -Compress

$bytes = [System.Text.Encoding]::UTF8.GetBytes($body)

# 3. Pass a byte array to -Body (not a string) and set the encoding in Content-Type
Invoke-WebRequest `
  -Uri 'https://vibecode.bitrix24.com/v1/feedback' `
  -Method POST `
  -Headers @{
    'X-Api-Key'    = 'YOUR_API_KEY'
    'Content-Type' = 'application/json; charset=utf-8'
  } `
  -Body $bytes

Common mistakes:

• Saving the .ps1 with a UTF-8 BOM — older PowerShell versions may fail to parse the script itself.
• Passing a string to -Body (-Body $body) instead of a byte array (-Body $bytes) — the string is re-encoded through the system code page.
• Relying only on Content-Type: application/json; charset=utf-8 without UTF8.GetBytes — this header does not restore the lost bytes; it only declares the body encoding to the server.

Node.js (fetch) and Python (requests) encode the body in UTF-8 themselves, so no extra steps are required. The problem is specific to PowerShell.

Error codes

Feedback conversations keep working even when the balance is frozen. A frozen billing account returns 402 ACCOUNT_FROZEN, but four feedback operations are exempt: create a ticket, list tickets, open a ticket, and reply to the team. You can report a problem exactly when it matters most, and continue the conversation if support asks for details.

Attachment uploads, downloads, and deletions, along with ticket updates, remain blocked under a freeze — they still return 402 ACCOUNT_FROZEN. The freeze does not lift the daily ticket-creation quotas.

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

See also

• Submit a ticket
• Keys and authorization
• Errors