Dành cho AI agent: markdown của trang này — /docs-content-en/changelog.md chỉ mục tài liệu — /llms.txt

Hiện tại, các bài viết trong tài liệu chỉ có bằng tiếng Anh.

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:

Later removals

After the next month: 29.

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.

General changes — limits, access, platform-wide behavior.

Getting started

API basics

Keys & access

Applications

Servers and deployment

AI

CRM

Tasks & calendar

Communication

People

Content & files

Sales & inventory

Business processes