Vibecode API Changelog

Vibecode API change history: new features, fixes, and breaking changes.

The latest entries are in the current month's archive. To find changes to a specific part of the API, open changes by API section.

Entry prefixes

NEW — a new capability: a new endpoint, a new optional field or parameter, a new error code in a new scenario. Existing client requests keep working.
FIX — corrected behavior. The response changes to the correct one, no client action required.
BC — a breaking change. Requires client action. The old format is supported for the stated period, then discontinued.

Entry code format: {TYPE}-{MMDD}-{N}, where MMDD is the publication date and N is the entry number within that date. The code stays a permanent identifier of the entry, and the numbers within a date may have gaps.

Some NEW entries are marked rolling out: the method shipped in a specific Bitrix24 update and is not yet available on every Bitrix24 account. Until the update reaches an account, the call returns 422 METHOD_NOT_YET_AVAILABLE with the target version — this is a sign of the rollout, not an integration error.

Scheduled removals of old formats

These changes are already live, but the old format keeps working for now. It stops working on the date shown — update your integration before then.

Within the next month:

until 21.10.2026 — BC-1007-7: a key of an employee marked as dismissed returns 403 OWNER_BLOCKED

Later removals

After the next month: 28.

until 26.12.2026 — BC-0629-3: vibe-search provider slug removed
until 01.01.2027 — BC-0701-5: categoryId in the posts response is now an array of numbers
until 06.01.2027 — BC-0707-2: Order-card nested fields normalized
until 06.01.2027 — BC-0706-7: dedicated error code for an oversized exec command
until 09.01.2027 — BC-0709-4: CRM, task and landing fields aligned with the real Bitrix24 contract
until 10.01.2027 — BC-0710-21: Open Channels config fields normalized to camelCase and described in /fields
until 14.01.2027 — BC-0714-30: renaming a catalog app reaches Bitrix24, publish loses menuTitle
until 15.01.2027 — BC-0716-1: json_object on a reasoning model recovers JSON; the 422 body is refined
until 15.01.2027 — BC-0716-4: POST /v1/infra/servers rejects unknown body fields
until 21.01.2027 — BC-0721-10: a broken image_url candidate no longer fails the whole request
until 22.01.2027 — BC-0723-14: the /v1/me deployment.standalone.requiredFields.create shape is now an object + documents the name slug
until 27.01.2027 — BC-0729-14: defaultOperatorData on Open Channels is an object now, and empty means null
until 30.01.2027 — BC-0802-2: self-hosted account access is no longer granted unconditionally
until 30.01.2027 — BC-0801-3: publication checks application authorization before snapshot freshness
until 30.01.2027 — BC-0731-1: source uploads require Content-Length
until 01.02.2027 — BC-0811-26: uploading a file to a galaxy app is refused instead of writing to the shared server
until 01.02.2027 — BC-0801-6: a broken exec no longer answers with success and exitCode -1
until 04.02.2027 — BC-0810-2: a filter error in POST /v1/{entity}/batch is now a per-sub-call error, not a whole-request one
until 04.02.2027 — BC-0810-3: batch reads no longer bypass an operation the entity turns off
until 04.02.2027 — BC-0810-4: a filter that is not an object is refused instead of being lost
until 04.02.2027 — BC-0810-5: an unknown filter field name is refused on fifteen more entities
until 04.02.2027 — BC-0805-4: the task field reference now matches the task response, and numbers are numbers
until 05.02.2027 — BC-0805-27: aggregate over a large pipeline: per-stage counts without reading deals, refusal instead of truncation
until 06.02.2027 — BC-0806-20: quota consumption is reported as percentages only
until 07.02.2027 — BC-0807-17: an activities aggregate needs a narrowing filter
until 09.02.2027 — BC-0809-1: meta.total is no longer returned by default in lists
until 18.02.2027 — BC-0824-14: an unknown select field name is refused with 400 on almost every entity
until 17.03.2027 — BC-0918-4: The envSync field on a galaxy application key replacement returns the real delivery outcome

Monthly archive

October 2026 · September 2026 · August 2026 · July 2026 · June 2026

Changes by API section

Pick the section your integration uses: its page lists every change to that section.

Vibecode API Changelog

Entry prefixes

Scheduled removals of old formats

Later removals

Monthly archive

Changes by API section

Getting started

API basics

Keys & access

Applications

Servers and deployment

AI

CRM

Tasks & calendar

Communication

People

Content & files

Sales & inventory

Business processes