[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-changelog\u002F2026-09-13":3,"docs-tabs-changelog\u002F2026-09-13":6},{"content":4,"lastmod":5},"# API changes: September 13, 2026\n\n[← Changelog](\u002Fdocs\u002Fchangelog) · [September 2026](\u002Fdocs\u002Fchangelog\u002F2026-09)\n\n### FIX-0913-1: the API description now names the refusals shared by every operation\n\n**Before**\n\nThe machine-readable description (`\u002Fv1\u002Fopenapi.json`) did not name the refusals produced not by the endpoints themselves but by shared platform layers — and a client generated from the description met them as an unknown answer.\n\nThe balance refusal `402 ACCOUNT_FROZEN` (the account is frozen for debt) is possible on any key-authenticated operation except a few informational and service ones — and was described on 22 operations out of 842. The answers `429 RATE_LIMITED` (Bitrix24 limited the call rate), `429 ERROR_LOOP_DETECTED`, `429 QUEUE_OVERFLOW`, `429 QUEUE_TIMEOUT`, `429 OPERATION_TIME_LIMIT`, `429 TIMEOUT_QUARANTINE`, `502 BITRIX_UNAVAILABLE` (Bitrix24 is unavailable) and `503 BITRIX_TIMEOUT` (Bitrix24 did not answer in time) are possible on every operation that calls Bitrix24 — `502 BITRIX_UNAVAILABLE` was described on 11 operations, `503 BITRIX_TIMEOUT` on 4, the rest almost nowhere. The operations of workflow templates, robots and activities (`\u002Fv1\u002Fbizproc-templates`, `\u002Fv1\u002Fbizproc-robots`, `\u002Fv1\u002Fbizproc-activities`) answer a personal key with `403 OAUTH_REQUIRED` — the description was silent; [GET \u002Fv1\u002Ftriggers](\u002Fdocs\u002Fautomation\u002Ftriggers\u002Flist) described only success while Bitrix24 answers a personal key with `403 BITRIX_ACCESS_DENIED`. The `400 INVALID_PARAMS` answer to a non-numeric record id in the path was described on the record read of no entity with a numeric id (`GET \u002Fv1\u002Ftasks\u002F{id}`, `GET \u002Fv1\u002Fworkgroups\u002F{id}` and the rest) nor on most of the task, scrum, timeline and timeline-log sub-resource endpoints.\n\n**After**\n\nEndpoint behaviour is unchanged — the description is corrected. The successful responses remain the same `200`, `201` and `204` they were: the description of the refusals changes, the response does not.\n\n`402 ACCOUNT_FROZEN` is described on exactly the operations the shared freeze gate can refuse: every key-authenticated operation except `GET \u002Fv1\u002Fme`, `GET \u002Fv1\u002Fme\u002Fsources`, `GET \u002Fv1\u002Fguide`, the four feedback-conversation calls (`GET \u002Fv1\u002Ffeedback`, `POST \u002Fv1\u002Ffeedback`, `GET \u002Fv1\u002Ffeedback\u002F{id}`, `POST \u002Fv1\u002Ffeedback\u002F{id}\u002Fcomments`) and `DELETE \u002Fv1\u002Fcowork\u002Fkey`. The description states that the refusal arrives before any check of the operation itself and always in the common response envelope (on the OpenAI-compatible AI operations too), and that as the narrowing rolls out the refusal will remain only on wallet-paid operations — a successful answer on a frozen account does not mean the account is clear (the state is `infraState` in the [GET \u002Fv1\u002Fme](\u002Fdocs\u002Fkeys-auth\u002Fme) response).\n\n`429`, `502` and `503` with the codes listed above are described on the operations that call Bitrix24: the generated entity operations (list, read, create, update, delete, search, batch, import, aggregate, relations, product rows, actions — except `GET \u002Fv1\u002F{entity}\u002Ffields`, which answers a Bitrix24 failure with `200`, the static field set and a `fields_partial` warning), the batch call `POST \u002Fv1\u002Fbatch` (with a set of its own: a Bitrix24 rate limit on the envelope itself arrives not as `429` but as `502 BITRIX_UNAVAILABLE` in its usual form or `422 BITRIX_ERROR`, with the Bitrix24 code in `error.bitrixError.error`; `429` there is the batch budget and the queue), and the hand-written families: the task sub-resources, scrum, timeline, timeline log, workday, calls, workflows (`\u002Fv1\u002Fworkflows`), CRM custom fields (`\u002Fv1\u002Fuserfields`), stage history, file upload, duplicate search, `GET \u002Fv1\u002Faddresses\u002Ffields`, `POST \u002Fv1\u002Fdoc-templates`. Where an operation already had a `429` of its own (the read or batch budget, the endpoint's own limit), its own `502` or `503`, the previous text is kept and extended. Each such operation also describes `422 BITRIX_ERROR` — the common answer to a Bitrix24 error that falls under no narrower code.\n\nAll operations of the three workflow entities describe `403 OAUTH_REQUIRED`; on writes, next to `WRITE_BLOCKED_READONLY_KEY`. [GET \u002Fv1\u002Ftriggers](\u002Fdocs\u002Fautomation\u002Ftriggers\u002Flist) and [POST \u002Fv1\u002Ftriggers\u002Ffire](\u002Fdocs\u002Fautomation\u002Ftriggers\u002Ffire) describe `401`, `403` (`SCOPE_DENIED`, `BITRIX_ACCESS_DENIED`, and `WRITE_BLOCKED_READONLY_KEY` on firing), `422` and, on firing, `400` (`MISSING_PARAMS`, `INVALID_ENTITY_TYPE`, `INVALID_ENTITY_TYPE_ID`).\n\n`400 INVALID_PARAMS` to a non-numeric record id is described on the record read, update and delete of every entity with a numeric id and on the task, scrum, timeline, timeline-log, call transcript (`GET \u002Fv1\u002Factivities\u002F{activityId}\u002Ftranscript`), workgroup member and lead conversion endpoints. The endpoint-specific codes of the same refusal are named where an endpoint answers with them: `INVALID_DYNAMIC_PARAM` (all smart-process operations by `{entityTypeId}`), `INVALID_ENTITY_TYPE_ID` (a smart-process record, smart-process custom fields, CRM card configuration), `INVALID_ROW_ID` (a product row), `INVALID_ANCHOR` (requisite links), `VALIDATION_ERROR` (configurable activities), `INVALID_ID` (an employee photo), `INVALID_BOT_ID` (bot ownership transfer), `UNKNOWN_ENTITY` (CRM custom fields by `{entity}`).\n\nWhat the description STILL does not name — deliberately: the daily call-quota refusal (`429 QUOTA_EXCEEDED`) is shared by the whole API and is outside this change; on the batch reads that report a Bitrix24 refusal inside the successful answer, per sub-call (`POST \u002Fv1\u002Fmail\u002Fmailboxes\u002Fbatch`, `POST \u002Fv1\u002Ftasks\u002F{taskId}\u002Fcomments\u002Fbatch`), no response-level Bitrix24 refusal is described — there is none.\n\nThe shared answers live in the reusable description components `AccountFrozen`, `PortalRateLimited`, `PortalUnavailable`, `PortalTimeout` and `OauthAppKeyRequired`. The interactive reference (`\u002Fdocs` → API reference) has been regenerated from the corrected description. Code details — on the [Errors](\u002Fdocs\u002Ferrors) page.\n\n### NEW-0913-2: a Partner Connect application requests the vibe:ai scope itself\n\n`vibe:ai` is now listed among the scopes of a Connect application at registration and on edit — like any Bitrix24 scope, with no request form and no review. From there the scope travels the usual path: the application passes it in the `scope` parameter of `\u002Fv1\u002Fconnect\u002Fauthorize`, the user sees an \"AI models\" line on the consent page and confirms the set as a whole, and the issued key carries the scope. AI Router calls made with such a key work, and consumption is covered by the account's monthly AI allowance.\n\nThe scope is never added automatically: an application that did not ask for it behaves exactly as before, and previously issued keys keep their scope sets. The other platform scopes — `vibe:search`, `vibe:infra`, `vibe:storage`, `vibe:feedback` — are granted by a platform administrator, and a self-registration request carrying them is rejected with `SCOPE_NOT_ALLOWED`. The `\u002F.well-known\u002Foauth-authorization-server` document lists `vibe:ai` in its `scopes_supported` field.\n\n### FIX-0913-3: product rows of a missing record now answer \"not found\", like the sibling methods\n\n**Before**\n\n[GET \u002Fv1\u002Fdeals\u002F{id}\u002Fproducts](\u002Fdocs\u002Fentities\u002Fdeals\u002Fproducts-get) on a nonexistent `id` answered `403 BITRIX_ACCESS_DENIED` — that is how Bitrix24 answers a product-row request for an owner that does not exist, and VibeCode passed the answer through as is. The sibling methods on the same `id` — the record itself, its contacts, writing product rows — answered `404 ENTITY_NOT_FOUND`. A client that received \"access denied\" went to check permissions instead of checking the `id`. The same for leads, quotes, invoices and smart-process items.\n\n**After**\n\nWhen Bitrix24 refuses a product-row read, VibeCode checks the record itself once — with the same call `GET \u002Fv1\u002F{entity}\u002F{id}` makes. The record does not exist — the answer is `404 ENTITY_NOT_FOUND`, like the sibling methods. The record exists but the employee's permissions restrict it — still `403 BITRIX_ACCESS_DENIED`. Successful requests make no extra call. OpenAPI declares the `404` response for the method; the invoices page no longer describes `403` as the answer for a missing record.\n\n**Affected endpoints:** [GET \u002Fv1\u002Fdeals\u002F{id}\u002Fproducts](\u002Fdocs\u002Fentities\u002Fdeals\u002Fproducts-get), [GET \u002Fv1\u002Fleads\u002F{id}\u002Fproducts](\u002Fdocs\u002Fentities\u002Fleads\u002Fproducts-get), [GET \u002Fv1\u002Fquotes\u002F{id}\u002Fproducts](\u002Fdocs\u002Fentities\u002Fquotes\u002Fproducts-get), [GET \u002Fv1\u002Finvoices\u002F{id}\u002Fproducts](\u002Fdocs\u002Fentities\u002Finvoices\u002Fproducts-get), [GET \u002Fv1\u002Fitems\u002F{entityTypeId}\u002F{id}\u002Fproducts](\u002Fdocs\u002Fentities\u002Fitems\u002Fproducts-get).\n\n### FIX-0913-4: the account freeze is checked for an application key even without a user session\n\n**Before**\n\nAn application key (`vibe_app_*`) sent without an `Authorization: Bearer` header carrying a user session was not checked against the account freeze: the call went on to the operation's own checks. On a frozen account such a key passed through the doors paid for from the Vibe credits balance — [creating an application](\u002Fdocs\u002Fapps\u002Fcreate) with its paired key, uploading and downloading ticket attachments, [updating a ticket](\u002Fdocs\u002Ffeedback\u002Fupdate), [search](\u002Fdocs\u002Fsearch\u002Frun) and [deep research](\u002Fdocs\u002Fsearch\u002Fresearch), the server list — whereas a personal key and the same application key with a session received `402 ACCOUNT_FROZEN`.\n\n**After**\n\nThe freeze is a state of the account, not of the session: on a frozen account an application key without a session answers `402 ACCOUNT_FROZEN` exactly where a personal key does — the set of closed and open calls is described in the [\"What the account freeze closes\"](\u002Fdocs\u002Ferrors) section. The calls open under the freeze — the self-description, the reference, the spec, the support conversation — stay open for such a key too. On an account that is not frozen the responses do not change: the successful response is preserved.\n\n**Impact on integrators**\n\nNothing changes for the client. If an integration used an application key without a session and suddenly receives `402 ACCOUNT_FROZEN` on a frozen account, the key is not broken — the account is in debt: top up the balance; the account state is visible in the `infraState` block of [`GET \u002Fv1\u002Fme`](\u002Fdocs\u002Fkeys-auth\u002Fme).\n\n### FIX-0913-5: the batch call answers 429 ERROR_LOOP_DETECTED instead of 500 when the platform paused it after a series of refusals\n\n**Before**\n\nWhen the batch calls of one key kept being refused by Bitrix24 and the Vibecode platform temporarily paused them (see [ERROR_LOOP_DETECTED](\u002Fdocs\u002Ferrors\u002Flimits)), [POST \u002Fv1\u002Fbatch](\u002Fdocs\u002Fbatch) itself answered `500 INTERNAL_ERROR` with no `Retry-After` header and no hint — while every other operation in the same state answers `429 ERROR_LOOP_DETECTED`. The client read an internal platform error where the platform's own protective mechanism was at work, and did not know how long to wait.\n\n**After**\n\n[POST \u002Fv1\u002Fbatch](\u002Fdocs\u002Fbatch) answers `429 ERROR_LOOP_DETECTED` with a `Retry-After` header, and `error.message` and `error.hint` carry the number of refusals in the last hour and how often a probe request is let through to check that the series is over. The individual calls inside a batch already received this code in `data.errors.\u003Cid>` — only the answer to the whole batch changed.\n\n**Impact on integrators**\n\nNothing to change. A handler that honours the `Retry-After` pause on `429 ERROR_LOOP_DETECTED` now covers the batch call too. If an alert was set on a `500` from the batch call, it stops firing on this state.\n",null,{},1794739479357]