API changes: September 2026

← Changelog. Days are listed newest first, open an entry by its link.

September 30, 2026

• NEW-0930-1: Chats: messenger settings and v2 service methods
• NEW-0930-2: Chats: the unread mark, read later, mentions, the membership check and chat folders
• NEW-0930-3: Chats: files and CoPilot on the messenger v2 methods
• FIX-0930-4: legacy file metadata for an ordinary key
• NEW-0930-5: Chats: members on messenger v2 — managers, members as entities, active members and membership records
• FIX-0930-6: restore legacy member-list parameters for ordinary keys
• FIX-0930-7: restore chat owner body forwarding
• NEW-0930-8: Chats: messenger v2 — deletion, joining, the parent chat, the access check and v2 modes of the chat card, creation and update
• FIX-0930-9: legacy chat creation for an ordinary key
• NEW-0930-10: Upload and delete catalog product images
• BC-0930-11: Apps return their original redirects to the client
• NEW-0930-12: Notifications: messenger v2 — marking by list, marking all, deleting all, groups and delivery settings
• NEW-0930-13: Bitrix24 account web search settings — advanced mode and a daily spend cap
• FIX-0930-14: /v1/oauth/authorize rejects state prefixed with open-app:
• FIX-0930-15: an immediate bot event re-poll after an error no longer gets 409
• BC-0930-16: POST aggregate rejects legacy-format fields outside the array
• FIX-0930-17: key button on an empty slot in the application list
• FIX-0930-18: a busy server no longer points the machine field at a call that refuses
• FIX-0930-19: post-not-found responses and post id and recipient refusals return an English message
• NEW-0930-20: Chats: messages on the messenger v2 methods — the first page, views, disappearing messages and read marks
• FIX-0930-21: restore partial legacy message batch results
• FIX-0930-22: restore the existing legacy message mutations
• FIX-0930-23: restore legacy feed parameters for ordinary keys
• FIX-0930-24: restore legacy read-mark input handling
• FIX-0930-25: restore legacy message-send fields
• FIX-0930-26: block message viewers for read-only keys
• FIX-0930-27: speech recognition with a disabled model now answers 404 before recognition
• BC-0930-28: cancelling a Cowork order reverses the seat purchase in the revenue export, and three amounts become signed
• BC-0930-29: a repeated galaxy server create no longer spawns applications
• NEW-0930-30: Bot API warns when a registration must be replaced after a Bitrix24 account address change
• BC-0930-31: Key revocation with a server outside its owner and Bitrix24 account scope
• NEW-0930-32: Chats: messenger v2 stickers — packs, adding, deletion and recent stickers
• FIX-0930-33: PATCH /v1/infra/servers/{id}/access-policy spec declares accessPolicy as an enumerated string
• NEW-0930-34: server activity feed
• NEW-0930-35: Chats: personal folders — create, edit, order and contents
• NEW-0930-36: Chats: chat settings — description, color, avatar, member permissions and message auto-delete
• NEW-0930-40: Chats: chat links, joining by code, guest links and guest invitations
• NEW-0930-41: inventory documents and items are available through V1
• FIX-0930-42: outside calls to an app now count toward the key's daily allowance
• NEW-0930-43: Write catalog price types through the Vibecode API
• NEW-0930-44: Chats: reactions, pinned messages, forwarding, in-chat search and typing
• NEW-0930-45: Chats: anchors, channel comments, message blocks and the number of pinned messages
• FIX-0930-46: restore the existing event polling response
• FIX-0930-47: restore the task feed fallback

September 29, 2026

• NEW-0929-1: Catalog measure and VAT rate reference data
• BC-0929-2: employee and requisite sorting now orders by identifier
• BC-0929-3: Cowork ERP management status lists the EMAIL channel only when the account has an email address
• NEW-0929-5: catalog services are available through V1
• FIX-0929-6: heavy revenue export pages no longer fail with 503 after 5 seconds
• FIX-0929-7: /v1/me lists only scopes obtainable on the Bitrix24 account
• NEW-0929-8: connector gateway for Cowork
• FIX-0929-9: the Cowork/Code tier change preview quotes the discounted price
• NEW-0929-10: cause and action in Bitrix24 permission and scope refusals
• FIX-0929-11: a post permission refusal returns an English message
• BC-0929-12: File and folder search validates both supplied parent folder IDs
• NEW-0929-13: balances export: user counters per Bitrix24 account
• BC-0929-14: chat read boundaries, file metadata and publication recovery
• NEW-0929-16: catalog SKUs and offers are available through V1
• NEW-0929-17: Chats: dialog list sections, shared chats, changes since a moment, chat pinning and reading
• FIX-0929-18: The legacy chat list supports deep offsets again
• NEW-0929-19: write catalog list-property values through V1
• NEW-0929-20: cause and a ready transfer step in the BOT_ACCESS_DENIED refusal

September 28, 2026

• NEW-0928-1: task results through legacy REST
• NEW-0928-2: task results through REST 3.0
• NEW-0928-3: Four task template methods
• NEW-0928-4: 12 Scrum operations are available through named routes
• FIX-0928-5: creating a custom field now checks the value that is sent to Bitrix24
• FIX-0928-6: a repeated POST /v1/bots for an existing bot no longer breaks its token
• BC-0928-7: the agent_turn_loop_detected refusal for a looping agent turn is switched on
• NEW-0928-8: Definition of Done settings and sprint metric source data are available
• NEW-0928-9: Flows and task status lists are available through the API
• FIX-0928-10: the seat assignment link in the Cowork members list opens the Employees section
• FIX-0928-11: Public apps report unavailability when waking is blocked
• BC-0928-12: server source access follows the owner key
• FIX-0928-13: business process templates, activities and automation rules on an account without the module answer 409 BIZPROC_MODULE_NOT_ENABLED
• NEW-0928-14: Cowork plans return a promo block: a seat-limited promotion and the price of the rest of the order
• FIX-0928-15: empty POST requests receive the intended validation response
• FIX-0928-16: warning about application access to the Bitrix24 account after deploy
• FIX-0928-17: the Cowork desktop key can read its application's server sources again
• NEW-0928-19: Cowork/Code limit reset with a promotion right
• FIX-0928-20: reading sites on an account without the Sites module answers with its own code
• NEW-0928-21: the spec now names the rollout refusal on the call follow-up methods
• NEW-0928-22: Cowork cloud tasks
• FIX-0928-23: Read application sources from Cowork
• BC-0928-24: Sequential bot polling uses the persisted position
• NEW-0928-25: seat demo status in Cowork/Code subscription responses
• FIX-0928-26: a chat response without tool calls is no longer marked as a tool call
• FIX-0928-27: a connection failure in workflow operations is no longer reported as a disabled module

September 27, 2026

• BC-0927-1: Cowork plans return the new-seat price with the Bitrix24 account's discounts
• NEW-0927-2: Cowork seat price quote for the checkout
• FIX-0927-3: business process operations on an account without the module answer 409 instead of 404
• NEW-0927-4: A Cowork order with a quote is credited at the quote's prices
• NEW-0927-5: Checklist actions and attaching a file to a task

September 26, 2026

• BC-0926-1: the Cowork subscription key of an owner without a Bitrix24 account cannot be rotated, re-enabled or extended
• NEW-0926-2: Direct task actions through the API
• FIX-0926-3: looping model reasoning is cut off with the reasoning_repetition code
• FIX-0926-4: the streamed chat response always ends with a finish reason
• FIX-0926-5: a large ERP user mapping replacement no longer answers 503

September 25, 2026

• BC-0925-1: an unreadable field id is refused before a smart-process field is changed or deleted
• FIX-0925-3: sign-in from Cowork now opens Galaxy apps too
• FIX-0925-4: a server whose creation failed on the cloud side no longer hangs in PROVISIONING
• FIX-0925-5: the sleeping-app log read no longer names a wake address that is banned on the host
• FIX-0925-6: a cursor with a corrupted date in revenue exports is rejected with INVALID_CURSOR instead of a 500 error
• FIX-0925-7: the charges export includes AI usage over the quota
• FIX-0925-8: bot file upload checks the required fields before calling Bitrix24
• FIX-0925-9: Editing the scopes of a key whose webhook stayed on the previous Bitrix24 account address answers PORTAL_ADDRESS_CHANGED
• FIX-0925-10: the workflow list answers with a clear code on an account without the module
• FIX-0925-11: BitrixGPT 5.5 accepts json_schema when the model supports structured outputs
• FIX-0925-12: storage: reads and deletes by key pick a non-deleted copy of the file
• BC-0925-13: mailbox listing without the Mail module answers with a clear 409
• BC-0925-14: the task chat feed for a read-only key — a page holds at most 50 messages
• NEW-0925-15: Chats: the format=v2 mode, chat loading, counters and messages around a message
• FIX-0925-16: a dropped connection to Bitrix24 answers 502 BITRIX_UNAVAILABLE
• NEW-0925-17: Vibe credits spend per Bitrix24 account: GET /v1/platform/revenue/spend
• FIX-0925-18: a wake window on a server in the scheduled run mode can be created and edited through the API
• FIX-0925-19: employee directory uses available keys
• BC-0925-20: Bitrix24 events and automation rule callbacks arrive without Bitrix24 tokens under a Read-only key
• BC-0925-21: deploying with a Read-only key does not post the new version announcement
• NEW-0925-22: note field in the eventDelivery block of the GET /v1/me response
• NEW-0925-23: Vibe credits by Bitrix24 account: GET /v1/platform/revenue/credits

September 24, 2026

• NEW-0924-2: Multiplicity flag for Bitrix24 account fields in the entity fields description
• BC-0924-3: CRM document sorting takes one bracket level only
• FIX-0924-4: Cowork ERP management status no longer asks for a confirmation code by default
• FIX-0924-5: the daily call allowance is counted by completed hours
• FIX-0924-6: the aggregation reference in GET /v1/guide describes POST aggregation and numeric-function fields by type
• NEW-0924-7: a default schedule for new machines
• FIX-0924-8: the run mode named at create now reaches a galaxy application
• FIX-0924-9: aggregation reports a Bitrix24 account error the same way the list does
• NEW-0924-10: new refusal code agent_turn_loop_detected for a looping agent turn
• FIX-0924-11: an empty fields in a bot request body no longer swallows the flat fields
• FIX-0924-14: A bot events request with an explicit offset below the stored one no longer moves the cursor
• NEW-0924-15: resubscribe now reports the event mode Bitrix24 holds
• NEW-0924-16: sign-in to a deployed app with a Cowork desktop key
• BC-0924-17: list methods check the key before reading the body and answer 401 without one
• FIX-0924-18: a file in a list element property is no longer capped at 1 MB

September 23, 2026

• NEW-0923-1: ERP connection management through the Cowork API
• NEW-0923-2: turning chat notifications off and on
• BC-0923-3: creating a deal or a lead with a stage outside the dictionary no longer answers with success
• BC-0923-4: CRM_CREATE in open-line configurations now accepts only supported values
• FIX-0923-5: Field-name validation when reading requisites
• FIX-0923-6: Reuse the application server after rebinding its key
• FIX-0923-7: Bracket form of order and scope no longer causes an internal error
• FIX-0923-8: galaxy app diagnostics now check the public address
• FIX-0923-9: revoking server access now ends sessions that are already open
• FIX-0923-10: Legacy GET aggregates report incomplete data
• BC-0923-11: fieldName is checked before Bitrix24 is called when creating a custom field
• NEW-0923-12: server detail returns the last deploy's start command, install command and port
• NEW-0923-13: app active-servers refusal now names the server owner
• BC-0923-14: retrying Cowork application creation after a network failure returns the first attempt's outcome — while it is still fresh

September 22, 2026

• BC-0922-1: single-entity batch paginates: a sub-call offset is finally read
• NEW-0922-2: two new refusal codes for agent runtime keys
• NEW-0922-3: result delivery for a long-running solution method
• FIX-0922-4: a Bitrix24 «parameter not supplied» refusal answers 400, not 422
• FIX-0922-5: Bitrix24 account address change: the call answers 409 PORTAL_ADDRESS_CHANGED instead of 500
• FIX-0922-6: deleting an app releases the authorization key held by its card
• FIX-0922-7: the OpenAPI aggregation schema now describes fields the way the API accepts them
• FIX-0922-8: default per-user limits raised — keys, servers, bots
• BC-0922-9: Retrying an unfinished key rotation requires recovery
• FIX-0922-10: JavaScript service names no longer replace a parameter value
• NEW-0922-11: Cowork/Code desktop ticket for phone access
• FIX-0922-12: the owner-only policy now behaves the same on every entry point
• FIX-0922-13: a wake schedule can be set for an app inside a galaxy again
• NEW-0922-14: three more presets in the work-schedule library

September 21, 2026

• FIX-0921-1: the mailbox batch example now shows a sub-call
• FIX-0921-2: image generation honours output_format and negative_prompt
• FIX-0921-3: /exec no longer corrupts multi-byte characters in output
• FIX-0921-4: application external API survives a short tunnel reconnect
• FIX-0921-5: write-operation 403 schemas now allow every published code
• BC-0921-7: A field the entity description does not declare is checked on write by its Bitrix24 type
• BC-0921-8: the contact and deal schemas are completed: twelve response fields declared read-only, thirteen service and empty keys removed
• FIX-0921-9: Cowork plans return terms to an unknown account too, once terms are open to everyone
• NEW-0921-10: the Cowork employee list now breaks parked seats down by plan and term
• NEW-0921-11: server deletion reports how the request to delete the machine in the cloud ended
• NEW-0921-12: DISK_FULL code in a server's provisionErrorCode after a failed repair
• NEW-0921-13: activities now support include: responsible, author, editor
• FIX-0921-14: structured output is checked for parseability, not only for truncation

September 20, 2026

• FIX-0920-1: the OpenAPI specification and the API reference name the required filter keys and count over "*"
• BC-0920-2: updating or deleting a missing employee field answers 404
• FIX-0920-3: two simultaneous server creations for one application now yield one machine
• BC-0920-4: the clientId field is removed from the Cowork employee list response
• FIX-0920-5: server status stops reporting "connected" while the tunnel is dead
• FIX-0920-6: the OpenAPI schema declares the scope refusal on entity read operations
• BC-0920-7: batch writes and import no longer answer with success when Bitrix24 did not apply the stage or the manual amount
• FIX-0920-8: the previous turn's reasoning reaches the model again

September 19, 2026

• FIX-0919-2: a lost link to the cloud machine is no longer reported as its absence, and no longer advises creating a second one
• FIX-0919-3: wasEverCommercial in GET /v1/me is payment history, not access
• NEW-0919-4: server run mode and the work-schedule library are now available over the API
• FIX-0919-5: the OpenAPI specification and the API reference describe task history, kanban stages and CRM reference aggregation
• BC-0919-6: a project deploy key is issued only to an admitted Bitrix24 account

September 18, 2026

• FIX-0918-1: quote filter and sort by the not-returned contacts field answer with the platform's refusal, not a Bitrix24 error
• BC-0918-2: A server development-team member gets their own key, and the key block gains the collaborator slot
• NEW-0918-3: An application created from Cowork no longer has to name its scopes
• BC-0918-4: The envSync field on a galaxy application key replacement returns the real delivery outcome
• FIX-0918-5: the icon upload tells a permission refusal apart from a missing server
• FIX-0918-6: an application's external API now reaches the application instead of answering "not reachable"
• FIX-0918-7: a function-call turn no longer duplicates the reasoning into content
• NEW-0918-8: company-parked seats in the Cowork members method
• FIX-0918-9: employees who left no longer appear in the Cowork members list
• FIX-0918-10: an account whose plan was never asked about no longer gets a "paid plan required" refusal
• FIX-0918-11: an access refusal now tells an unread subscription from a missing one
• NEW-0918-12: a server can be created already in the run mode you need
• NEW-0918-13: storage and key-count ceilings for an account without a commercial plan
• NEW-0918-14: a payment carrying a Cowork seat composition now creates seat rights

September 17, 2026

• NEW-0917-1: Cowork plans read: quotas, prices and terms
• NEW-0917-2: servers now report a run mode: runMode and workSchedule in reads
• NEW-0917-3: account balance in the members read
• FIX-0917-4: removed apps show a clear placement state
• FIX-0917-5: application external API returns 503 under overload
• FIX-0917-6: warnings from a successful runtime install are now visible in the deploy response
• NEW-0917-7: paid seat rights in the members read
• FIX-0917-8: creating a folder through the global POST /v1/batch is no longer rejected by Bitrix24
• FIX-0917-9: the time-entry list answers 404 for a missing task
• FIX-0917-10: the "Time Management is not available on this portal" refusal has its own code
• BC-0917-11: a galaxy command with no exit status is no longer reported as successful
• BC-0917-12: an empty query-parameter value in the operations list is no longer replaced by the default
• NEW-0917-13: the outcome of a server command is readable after an interrupted wait
• FIX-0917-14: on a busy server the machine-actionable recovery field names the guarded endpoint
• FIX-0917-15: apps with an interface are no longer created in API-only mode
• BC-0917-16: creating a Cowork/Code application: live paid seat and a scope check
• FIX-0917-17: the idle threshold on a scheduled server is no longer a silent no-op
• BC-0917-18: the invoice schema is completed: eleven response fields declared, seven of them read-only, contacts marked as not returned
• FIX-0917-19: Idempotency-Key protects galaxy app creation and reuse
• BC-0917-20: key mode errors point to an available switch
• BC-0917-21: contact and deal responses drop the Bitrix24 search-index service string
• FIX-0917-22: smart-processes batch updates use the documented identifier
• FIX-0917-23: search filter schemas now respect entity capabilities
• FIX-0917-24: hint for an unavailable Galaxy package registry
• BC-0917-25: the seven client-requisite fields of a quote are returned again and declared read-only
• NEW-0917-26: a new PARKED value of the Cowork seat state
• BC-0917-27: Unambiguous record and page selection when listing CRM documents
• BC-0917-28: document template card declares both scopes for the fileId example
• FIX-0917-29: a bracket-form parameter gets 400 instead of 500

September 16, 2026

• FIX-0916-1: partner accounts get raised free Cowork limits
• NEW-0916-2: Bitrix24 account members and their Cowork seats
• FIX-0916-3: a concurrent application key replacement issues exactly one key
• NEW-0916-4: server details show the port detected by the tunnel agent
• FIX-0916-5: the COWORK_HARNESS_DISABLED code no longer arrives on Cowork subscription keys
• FIX-0916-6: Object reads are limited independently for each Bitrix24 account
• FIX-0916-7: API reports the effective tunnel state
• NEW-0916-8: Cowork off-peak and quota-relief keys now always arrive
• FIX-0916-9: storage: a file uploaded again under the same key no longer counts as several objects
• FIX-0916-10: a wake window on a server with a run mode is no longer refused as an always-on conflict
• BC-0916-11: Unambiguous record type when listing CRM documents
• NEW-0916-12: calendar events now support include: owner, host, attendee
• NEW-0916-13: employee custom fields via /v1/userfields/users
• FIX-0916-14: aggregation refusals explain the limit on reads without pagination
• BC-0916-15: previousKey in the application key replacement response
• FIX-0916-16: an application with a blocked key can be repaired by replacing it
• FIX-0916-17: POST /v1/keys/{id}/rotate accepts a blocked key
• NEW-0916-18: department names in the members read
• NEW-0916-19: model catalog: capability filter for Cowork/Code keys
• BC-0916-20: a whitespace-only application name is rejected on every write path
• FIX-0916-21: a call to the account's previous address is now refused by name

September 15, 2026

• BC-0915-1: Black Hole classifies the app's response by its author, not its status; new code BH_APP_TIMEOUT
• FIX-0915-2: Bitrix24 event subscriptions accept event codes with dots
• FIX-0915-3: the bitrixgpt-* family no longer names its base model in an answer
• FIX-0915-5: Black Hole apps on a self-hosted portal get the employee ID on direct-link sign-in
• FIX-0915-6: the frozen-account refusal no longer promises the backup model is paid from the wallet
• FIX-0915-7: a platform integration key survives its creator moving to the administrator tier
• FIX-0915-8: a refused Black Hole app now explains which account the platform recognized
• FIX-0915-10: external collaborator keys are bound to their server
• BC-0915-11: application publication no longer hides a rejected placement bind
• NEW-0915-12: the application external API is open to every Bitrix24 account
• NEW-0915-13: task comment attachments and comment file download
• NEW-0915-14: catalog price types are available through the API
• BC-0915-15: a read-only key can deploy an application to its own server again
• NEW-0915-16: Bitrix24 account balance change notifications
• FIX-0915-17: the mode-switch address for an application auth key now follows where the application card lives
• NEW-0915-18: open channels: chats by CRM card and putting an operator into a dialog

September 14, 2026

• BC-0914-1: channel recovery may refuse to protect a running operation
• BC-0914-2: storage object delete and list received a per-account request limit
• FIX-0914-3: updating and deleting a smart process answer the Bitrix24 refusal code, not an internal error
• NEW-0914-4: creating a lead now warns when Bitrix24 converted it by itself
• BC-0914-5: access-policy refusal identifies the required key
• BC-0914-6: company search rejects the service index and contacts support category filtering
• BC-0914-7: storage object listing no longer counts the full set by default
• BC-0914-8: creating a document template from a Disk file requires the disk scope
• NEW-0914-9: Vibe+ trials grant agent access on the international platform
• FIX-0914-10: open line queue fields refuse clearly instead of surfacing a Bitrix24 error
• FIX-0914-11: partner NFR licenses are recognized as commercial
• NEW-0914-13: the external application API response carries X-Vibe-Request-Id
• BC-0914-14: Idempotency-Key on server creation now has a 15-minute replay window
• FIX-0914-15: OpenAPI now separates a personal key from an OAuth application key
• FIX-0914-16: native user-field names remain in narrow selections
• FIX-0914-17: Connect app authorization on self-hosted portals
• FIX-0914-18: the dedicated server card returns the installed runtime after a successful deploy
• BC-0914-19: the chat model field no longer matches models by substring
• FIX-0914-20: smart-process custom fields answer the Bitrix24 refusal code, not "not found"
• BC-0914-21: the quote response drops Bitrix24 service fields, the contacts field is marked as not returned
• NEW-0914-22: reasoning from earlier responses in the chat completion history
• FIX-0914-23: rate limit descriptions state the platform-wide cap and point at the header with the effective value
• FIX-0914-24: the default reasoning step is sent to the model explicitly
• BC-0914-25: the application external API answers a timeout with 503 instead of 504

September 13, 2026

• FIX-0913-1: the API description now names the refusals shared by every operation
• NEW-0913-2: a Partner Connect application requests the vibe:ai scope itself
• FIX-0913-3: product rows of a missing record now answer "not found", like the sibling methods
• FIX-0913-4: the account freeze is checked for an application key even without a user session
• FIX-0913-5: the batch call answers 429 ERROR_LOOP_DETECTED instead of 500 when the platform paused it after a series of refusals

September 12, 2026

• NEW-0912-2: device_id parameter in the device-flow confirmation link
• BC-0912-3: a meaningless body on message edit, chat members and post update is refused, not executed
• BC-0912-4: numeric path ids of the chat and notification endpoints are checked before the Bitrix24 call
• FIX-0912-5: a pre-existing NodeSource configuration now survives an interrupted runtime install
• FIX-0912-6: the eighth unavailability reason now reaches self-hosted accounts as well

September 11, 2026

• FIX-0911-1: the OpenAPI spec's scope slice no longer pulls in unrelated hand-written sections
• FIX-0911-2: POST /v1/doc-templates refusals point to the file field, not to Drive
• NEW-0911-3: the Marketplace trial unavailability reason gained an eighth value
• FIX-0911-4: Batch calls preserve selected fields
• FIX-0911-5: audio transcription tells an input error apart from a service failure
• FIX-0911-6: a write response now hints which fields were not recognised
• NEW-0911-7: The flow_ref field in the device-code response
• NEW-0911-8: balances export: client identifier, single-account lookup and a delta
• BC-0911-9: the tax amount on deals and quotes is now read-only
• FIX-0911-10: the messenger API description now matches what the endpoints answer

September 10, 2026

• BC-0910-1: a network failure on the way to the provider arrives under its own code ai_provider_network
• FIX-0910-2: AI provider errors now carry the pause from the provider's own header, in one shape for every stream
• FIX-0910-3: MCP tools mark API refusals as errors
• FIX-0910-4: the QUEUE_TIMEOUT refusal message names the actual wait
• NEW-0910-5: external membership is visible in V1: an external value for access.via and an externalServers block in /v1/me
• FIX-0910-6: X-Vibe-User-Name on a catalog open now carries the employee card name
• FIX-0910-7: responses of a model hosted by a third-party provider name the public model id
• BC-0910-8: GET /v1/me answers 401 for a deleted key instead of 200
• BC-0910-9: a Bitrix24 credential refusal now arrives as 401, not 422
• FIX-0910-10: disk move and copy operations are now available in OpenAPI
• BC-0910-11: a custom AI provider no longer follows redirects
• BC-0910-12: task, telephony and universal-list endpoints no longer ignore filter in silence
• FIX-0910-13: two spellings of one filter field no longer drop a condition in silence
• NEW-0910-14: vibe balances for every Bitrix24 account in one export
• NEW-0910-15: companies expose their linked contacts through include=contact
• FIX-0910-16: a boolean userfield flag is no longer dropped silently
• FIX-0910-17: V1 responses return X-Request-Id

September 9, 2026

• BC-0909-1: Audio transcription retains subscription billing when Cowork/Code is disabled
• BC-0909-3: Universal lists: an absent list answers "not found", and a bad offset answers with an error
• BC-0909-4: phantom contacts field removed from companies, leads, and deals
• FIX-0909-5: a self-hosted portal now issues a key that needs no webhook
• FIX-0909-6: replacing an application key no longer hands out an already-expired secret
• FIX-0909-7: a public numeric address in baseUrl and proxyUrl is no longer refused as private
• FIX-0909-8: the spec declares the 429 refusal of endpoints that carry their own rate limit
• FIX-0909-9: an expired OAuth user token returns an authentication error
• FIX-0909-10: the token endpoint's rate-limit refusal is now machine-readable
• FIX-0909-11: model reasoning for Cowork no longer appears in final text
• BC-0909-12: box top-ups now check out at the licence's own till

September 8, 2026

• FIX-0908-1: warehouses no longer substitute a different id, and refuse an unsupported filter out loud
• BC-0908-2: A value of the wrong type in a write field is refused instead of silently corrupting data
• FIX-0908-3: Paging through recent dialogs no longer loses or repeats records
• BC-0908-4: Fields that Bitrix24 assigns itself are now declared read-only
• FIX-0908-5: search and aggregate answer with an error on a wrongly typed parameter instead of silent emptiness
• FIX-0908-6: task favorites, comments and time entries answer honestly
• BC-0908-7: Lead conversion stamps backlinks and answers in the standard read format
• BC-0908-8: a payment currency that disagrees with the order is no longer swapped silently
• NEW-0908-9: the standalone server auto-sleep policy is now visible through the API
• BC-0908-10: writing an amount to a smart-process type without product rows no longer answers with a false success
• FIX-0908-11: the host from galaxyId is now available for reading
• NEW-0908-12: key issuance now says whether the key got access to Bitrix24 data
• FIX-0908-13: workday history is returned while a day is still open
• NEW-0908-14: agents are available for Open Channel binding
• NEW-0908-15: department include in user records
• NEW-0908-16: labels and descriptions for every basic field
• NEW-0908-17: protection against writing over newer sources
• NEW-0908-18: replace an application key in one call, and see its mask on the card
• NEW-0908-19: read the sprint list, active sprint, and a sprint by ID
• BC-0908-20: a paused Cowork/Code seat no longer opens Bitrix24 past the account plan
• FIX-0908-22: the sources registry no longer advertises a door that answers 403 to the calling key

September 7, 2026

• FIX-0907-1: redeeming a coupon on your own Bitrix24 account is now refused with a dedicated code
• NEW-0907-2: self-description now says whether infrastructure is stopped for non-payment
• FIX-0907-3: fixed pagination for business process activity and automation rule lists
• FIX-0907-4: infrastructure debt no longer disables what is paid for separately
• FIX-0907-5: an oversized numeric CRM ID is rejected before Bitrix24 is called
• FIX-0907-6: lead conversion respects the selected deal pipeline
• NEW-0907-7: Bitrix24 employee id of the app author in /v1/apps responses
• BC-0907-8: companies field removed from the contacts API
• FIX-0907-9: multipart upload replaces a large object under its existing key
• FIX-0907-10: moving a deal/lead to a nonexistent stage now returns an error instead of a silent success
• FIX-0907-11: The placement-bind note says trial, not demo
• FIX-0907-12: the spec declares every server mode-switch response
• NEW-0907-13: /v1/cowork/me and /v1/cowork/state now name the Bitrix24 account the key is bound to
• BC-0907-14: a partial lead conversion failure now answers 422, not 200
• FIX-0907-15: root-type validation on entity create, update, batch and search
• FIX-0907-16: an absent record answers 404 for warehouses, catalogs, order statuses, basket items and smart processes

September 6, 2026

• FIX-0906-1: a free Bitrix24 plan now answers key issuance terminally, not with a "retry later"
• BC-0906-2: PATCH /v1/infra/servers/:id/mode rejects opening a server with a sealed role
• NEW-0906-3: PATCH /v1/infra/servers/:id/mode may return a network-policy switch failure
• FIX-0906-4: PATCH /v1/infra/servers/:id/mode closes the server firewall when the connection drops mid-switch
• BC-0906-5: a platform integration key now dies together with its issuer's authority

September 5, 2026

• FIX-0905-1: chat with a Cowork/Code key works while the product is disabled
• FIX-0905-2: the key-issuance refusal now separates an unread plan from a free one

September 4, 2026

• NEW-0904-2: the Supports BitrixMobile flag at application registration
• BC-0904-3: the self-hosted refusal code is renamed to SELFHOSTED_NOT_AVAILABLE
• FIX-0904-4: trial deployment hints account for galaxy host eligibility
• FIX-0904-5: a catalog card is no longer published without its Bitrix24 account binding
• FIX-0904-6: expiresAt of presigned URLs now equals their signature lifetime
• FIX-0904-7: the latin locales call Bitrix24 trial access a trial
• FIX-0904-8: batch currencies sub-call no longer returns meta.total 0 next to a non-empty data
• NEW-0904-9: a partner application can revoke its own key
• BC-0904-10: offset in the statuses and deal-categories references works at any depth
• BC-0904-11: Workday history now returns the time-zone offset
• BC-0904-13: Entity read calls now have a per-account rate limit
• NEW-0904-14: invoices support include=deal

September 3, 2026

• NEW-0903-1: GET /v1/models exposes the reasoning control declaration
• NEW-0903-2: reasoning control in chat completions
• FIX-0903-3: invalid reasoning parameter values are rejected
• FIX-0903-4: GET /v1/me no longer declares region as required
• FIX-0903-5: direct BOX calls honor certificate trust
• BC-0903-6: an app key without an employee session reads only app-shared files by name
• FIX-0903-7: employees of one app can save files under the same name
• FIX-0903-8: a multipart upload distinguishes who holds the logical name
• BC-0903-9: smart process stage history by numeric entityTypeId, query parameters are now strict
• FIX-0903-10: one request no longer pauses a Bitrix24 method with its own sub-calls
• BC-0903-11: an employee photo that cannot become a file is refused on update
• NEW-0903-12: a command that removes an employee photo
• BC-0903-13: business process activity and robot creation returns a string code
• BC-0903-14: re-uploading with a personal key now refuses where the object state requires it
• FIX-0903-15: re-uploading with a personal key replaces the file instead of creating a second object
• FIX-0903-16: Node.js 20 deploy no longer depends on the package repository on a prepared image
• BC-0903-17: currency sorting rejects a field Bitrix24 cannot sort by
• BC-0903-18: include accepts only resolvable relations
• BC-0903-19: input array in POST /v1/embeddings capped at 64 strings
• NEW-0903-20: speech-to-text error texts no longer name the recognition engine
• FIX-0903-21: a Vibe+ demo now opens access on .com
• NEW-0903-22: two new promo code refusal codes: Bitrix24 plan restriction

September 2, 2026

• BC-0902-1: Documents expose the PDF transformation status
• BC-0902-2: The mode-switch address in the access-mode refusal is no longer fixed
• FIX-0902-3: a stream that never started ends with a retryable error for models from every provider
• NEW-0902-4: booking resources lookup in V1
• NEW-0902-5: money-in export marks revoked orders and returns the recognizable amount
• NEW-0902-6: device-flow accepts a device identifier
• NEW-0902-7: new INT_BOX_PARTNER_REQUIRED refusal code for self-hosted accounts on the international installation
• NEW-0902-8: stable account identifier in the key self-description
• NEW-0902-9: server creation answers 409 REISSUE_IN_PROGRESS while the application authorization key is being re-issued
• FIX-0902-10: Open Channels dashboard methods are now available in OpenAPI
• NEW-0902-11: support code in an unrecognized key issuance refusal
• NEW-0902-12: the Performance Review section is available through /v1/performan/review
• FIX-0902-13: the Bitrix24 plan refusal on key issuance and app installation now states its cause
• FIX-0902-14: a refusal on the consent page returns the user to the partner application

September 1, 2026

• FIX-0901-1: a permission refusal on the sprint board arrives as 403, not as a platform error
• BC-0901-2: an empty employee photo is refused on update
• FIX-0901-3: rate limit descriptions now name the replica share, not just the total cap
• BC-0901-4: task comment updates reject read-only fields
• FIX-0901-5: the 401 TOKEN_MISSING error now names the reason on every V1 route
• FIX-0901-6: direct upload can be repeated after object deletion
• FIX-0901-7: a transient image-registry outage no longer marks a galaxy app broken
• BC-0901-8: Regular chat-bot blocks key deletion
• FIX-0901-9: file uploads and AI requests now answer 429 under memory pressure
• FIX-0901-10: creating a Hermes agent no longer fails because of the startup payload size
• NEW-0901-11: the business-process editor is available through the API
• BC-0901-12: deleting a server now deletes the agent bound to it