API changes: October 2026

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

October 31, 2026

• NEW-1031-1: Coupon gifts measured in days
• FIX-1031-2: application list and card honor department access
• FIX-1031-3: moving to your own server keeps department access

October 30, 2026

• NEW-1030-1: a distinct refusal when the key does not manage the server
• FIX-1030-2: Paginated listing of storage root children
• FIX-1030-3: descending id sort for Disk files and folders
• FIX-1030-4: a solution event reaches a Bitrix24 account with the updated module
• NEW-1030-5: Chats: open the discussion of a post in one call
• BC-1030-6: OAuth bot registration and events
• FIX-1030-7: a bot operation no longer promises a retry that changes nothing
• FIX-1030-8: numeric ID arrays in response descriptions
• FIX-1030-9: The daily free API allowance is shared across an owner's keys
• FIX-1030-10: previous webhook cleanup no longer closes Bitrix24 for a Company connection

October 29, 2026

• NEW-1029-1: Analytics sources and channels
• FIX-1029-2: workgroup list remains available without a group image
• FIX-1029-3: The pipeline schema describes isSystem and the missing createdDate
• FIX-1029-4: bot registration no longer promises a retry that changes nothing
• NEW-1029-5: Custom domain of a server through the API
• BC-1029-6: Signed resource URLs and blocked token refresh
• NEW-1029-7: Advertising accounts for analytics
• NEW-1029-8: Manual expenses and source analytics
• FIX-1029-9: signing in to Cowork again keeps the previous key until the new key is confirmed
• FIX-1029-10: Temporary pause after repeated Bitrix24 access denials

October 28, 2026

• FIX-1028-1: Neutral diagnostics for server provisioning failures
• FIX-1028-2: deal counts by stage semantics answer without a pipeline number
• FIX-1028-3: a key is issued on a cloud Bitrix24 account connected without Bitrix24 Network
• FIX-1028-4: deploy continues when the server is ready
• FIX-1028-5: apps.create reflects new-key issuance access
• FIX-1028-6: Comment file IDs are returned in attach again
• NEW-1028-7: Key owner ID source
• NEW-1028-8: Next-page offset for lists
• BC-1028-9: Workspace typeIds no longer accepts a value with no matching type
• NEW-1028-10: End-to-end analytics traces through REST v3

October 27, 2026

• BC-1027-1: List writes reject empty fields and tighten required schema keys
• NEW-1027-2: Retry a server replacement without a second purchase
• FIX-1027-3: Cowork tier recommendations account for seat windows
• BC-1027-4: HEAD no longer runs the GET operation on three routes
• NEW-1027-5: Exhausted AI quota period in the response
• NEW-1027-6: actions on a server being moved to another zone answer 409 SERVER_ZONE_MOVING
• BC-1027-7: creating a standalone machine responds immediately, without SSH credentials
• BC-1027-8: Publishing a post requires explicit recipients

October 26, 2026

• FIX-1026-1: API reference field tables reflect update restrictions
• NEW-1026-2: Drive agent documentation links in GET /v1/guide
• BC-1026-3: Org-structure node and mailbox lists reject filtering and sorting
• BC-1026-4: deploy refuses paths with a .vibe-prev directory, which the platform reserves
• FIX-1026-5: a failed redeploy no longer leaves the application without files
• NEW-1026-6: Five-hour window phase and Cowork turn completion marker
• FIX-1026-7: app address with a name instead of app-… in handlers and appUrl
• NEW-1026-8: MCP package 3.3.0: sign-in flow and CRM form guidance
• FIX-1026-10: Company connection daily caps are now optional
• NEW-1026-11: List unread mention and reaction marks
• BC-1026-12: Access for hour-long cloud tasks
• FIX-1026-13: Incomplete aggregate counts are now marked
• BC-1026-14: Web search uses AI quota
• NEW-1026-15: Rejection before a personal model call starts
• FIX-1026-16: temporary promotion limit-reset failures can be retried safely
• NEW-1026-17: An overly complex request body is refused with 413 BODY_TOO_COMPLEX
• NEW-1026-18: company key for verified self-hosted Bitrix24 accounts

October 25, 2026

• NEW-1025-1: preview and connect models to a key of any provider

October 24, 2026

• FIX-1024-1: actions on a server being created answer 409 SERVER_CREATING
• NEW-1024-2: Bitrix24 entity operations with company credentials
• NEW-1024-3: Notifications and workday reads with Company credentials
• BC-1024-4: storage validates the file content type more strictly
• NEW-1024-5: solution event to the Bitrix24 account: POST /v1/solution-events
• FIX-1024-6: A completed command response no longer precedes server release
• FIX-1024-7: bot event polling no longer loses events after Bitrix24 restarts numbering

October 23, 2026

• FIX-1023-1: the 502 hint for a galaxy in ERROR that never connected no longer advises a retry
• NEW-1023-2: Submit a CRM form result and send a form to an Open Channel customer
• FIX-1023-3: GET /v1/me guidance respects Cowork key restrictions
• FIX-1023-4: Deployment to a new or woken server survives system updates
• BC-1023-5: CRM forms: configuration reads and builder dictionaries
• FIX-1023-6: a request to a bitrix model without images no longer hits the limit for images
• FIX-1023-7: unsupported GET collection filters now return a warning
• FIX-1023-8: Bitrix model availability reflects configured access
• FIX-1023-9: web search citations match the returned sources
• BC-1023-10: V1 operation limits use the authenticated access key
• BC-1023-11: Calendar event batch lists reject from, to and section in params
• FIX-1023-12: Calendar event and section batch lists forward required parameters
• NEW-1023-13: Create, update and manage CRM forms
• NEW-1023-14: CRM form embedding and connected places
• NEW-1023-15: Company method permissions and readiness
• FIX-1023-16: Deploy after interrupted package installation
• FIX-1023-17: models fetched with a standard provider key are bound to that key
• FIX-1023-18: consistent model selection for personal and company keys
• FIX-1023-19: Model replacement metadata uses the platform catalog

October 22, 2026

• FIX-1022-1: Deployment after server wake waits for readiness
• NEW-1022-2: waking a server during a configuration change answers 409 RESIZE_IN_PROGRESS
• BC-1022-3: Black Hole tells a dropped connection to the app from app startup, new code BH_APP_CONNECTION_LOST
• BC-1022-4: deleting the final OAuth key deactivates the app
• NEW-1022-5: Who is connected to a company key

October 21, 2026

• NEW-1021-1: python312 runtime on Python 3.12 from the Ubuntu 24.04 archive
• BC-1021-2: Neutral image identifiers and names
• NEW-1021-3: APP_DB_BUSY reports that the galaxy host is starting
• FIX-1021-4: an oversized request to a model: images for bitrix are downscaled, a size refusal is 413 instead of 502
• NEW-1021-5: Connector catalog groups, session modes and metadata
• FIX-1021-6: The Deploy API operation limit is counted per API key and server
• FIX-1021-7: Request and response examples in the API reference
• FIX-1021-8: OpenAPI describes the fields for creating a time entry
• FIX-1021-9: bot registration promises a retry only where it helps

October 20, 2026

• FIX-1020-1: the reference and OpenAPI show the actual response of five operations
• FIX-1020-2: Neutral server repair error messages
• FIX-1020-3: Public refusal reasons for bot updates and event polling
• FIX-1020-4: marking notifications read accepts an empty body with a JSON header
• FIX-1020-5: a Compose deploy names the container that failed behind HTTP 200
• FIX-1020-6: key deletion no longer gets stuck after a bot change
• NEW-1020-7: Company connections: readiness checks at every phase
• NEW-1020-8: AI for company connections with separate administrator consent
• FIX-1020-9: account cleanup fixed for deletion of apps without placement permission
• FIX-1020-10: updating a bot after an acknowledged write
• FIX-1020-11: a storage key with an empty or "." segment is rejected at the entry
• FIX-1020-12: Batch product creation returns product identifiers
• FIX-1020-13: reading and copying a sleeping application's database
• BC-1020-14: A new version of an existing app requires the same access as a new app
• FIX-1020-15: Explicit bitrix-search selection in the research schema
• BC-1020-16: Quick replies accept only sections of their own channel
• NEW-1020-17: Connector list pages, search and filters
• BC-1020-18: activity update refuses the deadline instead of answering without a change
• NEW-1020-19: Connectors report their type and session modes
• NEW-1020-20: node24 runtime on a supported Node.js release
• NEW-1020-21: replace an application's server through the API
• NEW-1020-22: Connector selection for Cowork
• BC-1020-23: PHP 8.3 on a dedicated server is installed from the Ubuntu repository
• NEW-1020-29: Official connector marker in catalog pages
• NEW-1020-30: Service company and connector modes in the workshop
• NEW-1020-31: Service companies in the connector catalog
• FIX-1020-32: Connector group counts in Cowork
• FIX-1020-33: Retry-After of a bot reconcile refusal is the time until the next scheduled check

October 19, 2026

• BC-1019-1: Adding storage access requires a personal key
• FIX-1019-2: Connect revokes the presented Cowork device key
• FIX-1019-3: deployments recognise links to platform storage
• NEW-1019-4: Explicit early refusal on repeated JSON
• FIX-1019-5: a server start from error that never becomes ready returns the server to error
• NEW-1019-6: graduating a galaxy application to a dedicated server keeps its custom domain
• NEW-1019-7: Recover a bot registration after a response without an ID
• NEW-1019-8: links to new Open Channel pages in GET /v1/guide
• FIX-1019-9: Server reuse hint explains how to create a second application
• NEW-1019-10: navigation URLs in the Cowork connector list
• FIX-1019-11: first Node.js 20 deploy on a new server no longer waits for system updates

October 18, 2026

• FIX-1018-1: a late wake cancellation does not stop a ready server
• FIX-1018-2: Creating departments in a batch

October 17, 2026

• BC-1017-1: Message and caption length checks before writing
• FIX-1017-2: Empty turns with tools receive an explanation
• NEW-1017-3: Prepare a server for the application database
• FIX-1017-4: Catalog sections in the write schema are an array of IDs
• FIX-1017-5: a closed application database connection is no longer reported as busy
• NEW-1017-6: sign-in source label for device flow
• NEW-1017-7: Key self-description provides the design rule for new UI
• FIX-1017-8: File search accepts the requested result count

October 16, 2026

• BC-1016-1: File access after an application transfer
• FIX-1016-2: a catalog launch offers authorization for a personal-key server too
• FIX-1016-3: server prices reflect the current platform price list
• FIX-1016-4: User and site creation field metadata corrected
• FIX-1016-5: Replacement authorization keys follow the application owner
• BC-1016-6: Public storage rejects executable MIME types with parameters
• FIX-1016-7: CRM document download no longer returns the Bitrix24 response text instead of the file
• NEW-1016-8: Applying application secrets without a deploy
• FIX-1016-9: bot re-subscription no longer returns 500 after a Bitrix24 timeout
• FIX-1016-10: Deployments to a new server wait for initial setup
• FIX-1016-11: a missing to-do activity answers 404 instead of 422
• NEW-1016-12: agent model bitrix/bitrixgpt-6.0-agent
• NEW-1016-13: Manually stopped Black Hole apps

October 15, 2026

• FIX-1015-1: Exact counts for searches across time windows
• NEW-1015-2: Application database restore
• BC-1015-3: entity writes reject a nested fields object
• BC-1015-4: contact names longer than 50 characters are rejected before writing
• FIX-1015-5: Updating an all-day event preserves its all-day flag
• FIX-1015-6: call follow-up methods are available on every account
• BC-1015-7: The extranet group flag is read-only
• NEW-1015-8: Application database writes via API and MCP
• NEW-1015-9: Message view count on request
• BC-1015-10: Cowork Demo requires employee consent
• FIX-1015-11: coupon redemption no longer refuses accounts backed by platform staff
• FIX-1015-12: deploying a Docker Compose app no longer fails on its own container
• FIX-1015-13: Build reports a faulty host

October 14, 2026

• FIX-1014-1: Epic and sprint lists honour a limit of up to 50
• FIX-1014-2: repeated error protection holds the block until a successful call
• FIX-1014-3: issuing a key into an empty slot waits for another operation on the application
• FIX-1014-4: Group calendar event owner and organizer
• FIX-1014-5: Catalog document and item lists honor withTotal=false
• FIX-1014-6: Connect sign-in accepts a localhost redirect address for both client types
• FIX-1014-7: Reference pagination advice respects unsupported filtering
• FIX-1014-9: A missing method no longer means a missing record
• FIX-1014-11: Repetition in truncated JSON no longer suggests a higher limit
• FIX-1014-12: product-row field dictionary no longer marks productId as required
• BC-1014-13: CRM dictionary record description comes in the description field instead of DESCRIPTION
• BC-1014-14: PKCE is also enforced for confidential clients
• BC-1014-15: Catalog product, SKU, and service date filters are rejected
• FIX-1014-16: an AI key shared by the Bitrix24 account administrator works for account users

October 13, 2026

• BC-1013-1: App address outside the platform: https only, not with an app or server key
• FIX-1013-2: rotating a revoked API key is refused before a new key is created
• NEW-1013-4: appUserSignIn.setup slot in the /v1/me response
• NEW-1013-5: Server repair reports that the platform has no channel to the machine
• NEW-1013-6: Application database copies
• NEW-1013-7: Long-running commands with durable results
• NEW-1013-8: Starting a sleeping server reports that no free capacity is available yet
• BC-1013-9: Offer filters by date are rejected
• FIX-1013-10: an unreadable plan on server creation answers only 403
• FIX-1013-11: service fields respect the catalog
• FIX-1013-12: Checklist reports a missing task
• NEW-1013-13: Atlas token exchange after a Bitrix24 account registers anew in Atlas
• BC-1013-14: Missing work schedules return an error
• FIX-1013-15: Batch file and folder lists honor the parent folder
• FIX-1013-16: catalog batch lists respect field selection
• FIX-1013-17: Validation of bot message, command and file IDs
• FIX-1013-18: mail date filters accept timezone offsets

October 12, 2026

• FIX-1012-1: Clear guidance when the server management service is unreachable
• NEW-1012-2: Batch reads of catalogs and storages are discoverable in OpenAPI
• NEW-1012-3: Company connectors for an application key
• BC-1012-4: The vibe:storage scope is not granted to Partner Connect applications
• FIX-1012-5: A vibe:storage scope refusal on a Partner Connect key no longer suggests an administrator grant
• NEW-1012-6: refusal outcomes for COMPANY clients
• NEW-1012-7: Refusal codes for company connections
• FIX-1012-8: Consistent refusal for closed company connection issuance
• FIX-1012-9: a busy app upload path allows retrying the deploy
• NEW-1012-10: Company connection status polling
• NEW-1012-11: App hosting marker in app responses
• BC-1012-12: datetime filters preserve the explicit time zone
• BC-1012-13: Application deletion requires confirmed container removal
• NEW-1012-14: Retryable refusal while a server binding is busy
• NEW-1012-15: Management keys are available in OpenAPI
• NEW-1012-16: Scheduled HTTP calls
• NEW-1012-17: Clear chat history for the caller or everyone
• FIX-1012-18: Confirmation of chat deletion
• FIX-1012-19: application files stay available after a key reissue and an application transfer

October 11, 2026

• BC-1011-1: Interrupted key issuance retains its quota slot
• BC-1011-2: Protecting servers during an active move to a Galaxy
• BC-1011-3: Galaxy app builds are limited to half of the host memory
• NEW-1011-4: Application secret delivery during deployment
• NEW-1011-5: CRM record activities are available in the API reference

October 10, 2026

• BC-1010-1: Cloud task service routes moved to V1
• NEW-1010-2: Application secret names
• FIX-1010-3: AI quota is checked before wallet balance
• FIX-1010-4: consistent denial status when the plan or subscription could not be read
• NEW-1010-5: Connector price in the connector list
• NEW-1010-6: Cowork money-pause reason in AI responses

October 9, 2026

• BC-1009-1: Order in document-template and calendar-event batch subcalls
• FIX-1009-2: Deleting an absent product image returns 404
• FIX-1009-3: Manual AI model registration reports invalid field types
• BC-1009-4: fields in catalog batch requests returns a field map without a wrapper
• NEW-1009-5: Cowork quota wall offers a limit reset with a promotion right
• BC-1009-6: Activity and automation rule lists reject sorting
• FIX-1009-7: The SSH password of an open server now works for the user returned by the access method
• FIX-1009-8: OpenAPI describes smart-invoice user fields
• FIX-1009-9: OpenAPI describes CRM activity bindings
• FIX-1009-10: Strict validation of requisite preset field ids
• FIX-1009-11: a Vibe+ trial started in Bitrix24 now grants access on .com
• FIX-1009-12: wake windows: margin no lower than the platform's, outcomes by the moment the server came up
• NEW-1009-14: Singleton methods are discoverable in OpenAPI and the API reference
• FIX-1009-15: adding a product to a payment returns 404 in German and Kazakh Bitrix24
• NEW-1009-16: work time settings for a specified employee
• NEW-1009-17: Cowork extensions
• NEW-1009-18: Learn-more link in the AI quota 402 refusal
• BC-1009-19: Bitrix24 account approval for AI access in Connect applications

October 8, 2026

• FIX-1008-1: Python 3.11 installation continues when the package repository is unavailable
• FIX-1008-2: User SSH keys are installed on pre-provisioned virtual machines
• FIX-1008-4: OpenAPI describes reading mail messages, acting on them and finding recipients
• FIX-1008-5: OpenAPI describes organizational structure counts, searches and operations
• FIX-1008-6: OpenAPI describes your AI provider keys and their models
• BC-1008-7: a partner application key does not pass vibe:ai on to a derived key — 403 SCOPE_GRANT_REQUIRES_CONSENT
• NEW-1008-8: Partner Connect: a "Connect AI" button example for an application inside Bitrix24
• FIX-1008-10: OpenAPI describes requisite preset fields
• FIX-1008-11: Disk method availability
• BC-1008-12: forced bot deletion requires Bitrix24 confirmation
• FIX-1008-13: key deletion waits for bot cleanup
• BC-1008-14: single-entity batch list applies the sort order

October 7, 2026

• FIX-1007-1: a server delete that loses the race no longer reports success
• NEW-1007-2: Edit content and publish an individual page block
• NEW-1007-3: Knowledge-base bindings to menus and workgroups
• NEW-1007-4: Block cards and saved templates
• BC-1007-5: generic lifecycle methods are unavailable for managed agent and bot servers
• FIX-1007-6: bots recover after a Bitrix24 account address change
• BC-1007-7: a key of an employee marked as dismissed returns 403 OWNER_BLOCKED
• FIX-1007-9: key issuance on an unpaid plan returns 402 with a purchase link
• NEW-1007-10: Restore and permanently delete Disk objects
• NEW-1007-11: Disk full-text search and storage operations
• NEW-1007-12: File version history and content on Drive
• NEW-1007-13: Disk public links and folder sharing with a user
• BC-1007-14: Task stages are checked against the target group kanban
• NEW-1007-15: Task stage management and day plan reading
• NEW-1007-16: Manage task custom fields
• BC-1007-17: Warehouse stock records and read-only currency base flag

October 6, 2026

• BC-1006-1: Comment files return only current metadata
• NEW-1006-2: site actions and data
• NEW-1006-3: Page actions and template discovery
• NEW-1006-4: Site folders
• BC-1006-5: galaxy host without an agent gets the AGENT_NEVER_CONNECTED code
• BC-1006-6: whitespace-only names of a key and of an AI credential are rejected
• FIX-1006-7: GET /v1/chats/:dialogId/messages: the limit ceiling applies to any spelling of the name
• NEW-1006-8: System pages and template areas
• BC-1006-9: the refusal for a server with no cloud VM names only the endpoints the caller may call
• BC-1006-10: a smart process can no longer be re-attached to a workspace through customSectionId
• NEW-1006-11: digital workspaces are now an entity — /v1/automated-solutions
• NEW-1006-12: landing blocks over the API: a page can now be filled with content
• FIX-1006-13: the reaction add and remove response is documented as data.result
• NEW-1006-14: Drive file search, synchronization and saving
• FIX-1006-15: typing indicator response example now matches the actual response
• BC-1006-16: feedback attachments now accept documents, not just images
• BC-1006-17: reading, updating and deleting a smart process field check that the field belongs to the smart process in the path
• FIX-1006-18: the business-process editor spec names when the section is unavailable
• NEW-1006-19: Continue note search and list documents
• FIX-1006-20: A missing payment product returns 404 regardless of the Bitrix24 account language
• BC-1006-21: Galaxy app deploy validates env line size
• BC-1006-22: reading post comments returns only valid identifiers and file fields
• NEW-1006-23: Copy, move, reorder and delete page blocks
• FIX-1006-24: server rename updates the application placement label
• NEW-1006-25: Read page blocks and catalog samples

October 5, 2026

• FIX-1005-1: the list of plans allowed on a trial can hold several plans
• FIX-1005-2: repeating an event subscription no longer returns an error
• FIX-1005-3: sleeping-server deploy operation is visible during wake
• FIX-1005-4: Reading pages without explicit field selection
• BC-1005-5: the task comment list reads the legacy store and paginates it
• FIX-1005-6: OpenAPI describes object filter serialization
• BC-1005-7: overall per-minute request limit per key and per key owner
• NEW-1005-8: Read-only mode for Cowork chats: chat keys and the mode choice
• NEW-1005-9: chats of one project as a separate list
• BC-1005-10: device limit on Cowork desktop key issuance and the COWORK_DEVICE_LIMIT_REACHED code
• BC-1005-11: auto-sleep no longer stops an application with a fetch Bot
• FIX-1005-12: request examples in the reference and the specification no longer show a body the route does not accept
• FIX-1005-13: OpenAPI describes every address route
• BC-1005-14: deleting a call log entry searches the 5000 newest entries
• NEW-1005-15: Calendar resources, availability and meeting RSVP
• FIX-1005-16: OpenAPI describes employee deactivation

October 4, 2026

• FIX-1004-1: Cloud tasks distinguish elapsed run times from credential expiry
• BC-1004-2: Finishing active Cowork work after the five-hour limit
• FIX-1004-3: switching to OPEN while the mode is disabled returns the platform refusal

October 3, 2026

• BC-1003-1: addresses and bookings no longer lose a filter condition in silence
• FIX-1003-2: CRM forms no longer hide ordinary form text
• FIX-1003-3: deleting a blocked key confirms revocation of its tokens
• FIX-1003-4: a deleted authorization app no longer describes the application card
• BC-1003-5: static deploy uses the platform web server

October 2, 2026

• NEW-1002-1: Work and daily reports
• NEW-1002-2: Pay systems and delivery services
• NEW-1002-3: Open Line operator actions
• NEW-1002-4: Booking resource CRUD, resource types and work hours
• NEW-1002-5: Bot commands and notification actions
• NEW-1002-6: Booking clients and wait list
• BC-1002-7: Cowork tries to finish ongoing work before the five-hour limit
• NEW-1002-8: Open Line CRM chats and quick replies
• NEW-1002-9: Operator actions accept chat
• NEW-1002-10: Open Line bot session actions
• FIX-1002-11: Operator actions refuse imprecise identifiers
• FIX-1002-13: a multipart upload reservation now counts against the Bitrix24 account storage cap immediately
• BC-1002-14: unsupported CRM product sort fields now report an error
• BC-1002-15: an unreadable smart-process userfield id is refused before the Bitrix24 account is called
• FIX-1002-16: entity list and search answer a clear error when entityTypeId did not arrive
• NEW-1002-17: Workgroup member actions and my workgroups
• FIX-1002-18: employee sorting no longer blocks list reads
• BC-1002-19: Bot registration checks account address changes and registration origin
• FIX-1002-20: empty V1 POST, PUT and PATCH requests receive validation errors
• NEW-1002-21: SIP, default outgoing line and call recording
• NEW-1002-22: Business-process tasks
• NEW-1002-23: App document downloads and public sharing
• BC-1002-24: only the custom-openai-compat provider accepts a per-credential endpoint
• NEW-1002-25: Call journal and feed comments
• NEW-1002-26: Prepared-service connectors and public OAuth client documents
• FIX-1002-27: a personal coupon of a deleted recipient can no longer be redeemed by anyone
• NEW-1002-28: Knowledge-base moves and module field types

October 1, 2026

• NEW-1001-1: Manage CRM to-dos and activity deadlines
• NEW-1001-2: read CRM forms
• NEW-1001-3: Cross-entity CRM and requisite lookup
• BC-1001-4: machine file links require a Vibecode API key
• NEW-1001-5: download CRM files and documents through the Vibecode API
• NEW-1001-6: CRM payments with product positions and delivery reads
• NEW-1001-7: create and manage CRM documents through the Vibecode API
• NEW-1001-8: file size refusal on upload carries a hint
• FIX-1001-9: Cowork key no longer refused to a box service account
• NEW-1001-10: CRM document templates are available through the Vibecode API
• NEW-1001-11: cause, action and a text for a person in refusals for a key's scope
• FIX-1001-12: a Bitrix24 scope refusal no longer calls a cabinet key a platform key
• BC-1001-13: Human approval for wider application access
• BC-1001-14: a multifield row with an id is refused on every write door
• NEW-1001-15: CRM dictionaries, mode and currency localizations
• NEW-1001-18: recentCallsDataSince field in GET /v1/ai/usage
• BC-1001-19: changing the mode of Cowork seat keys through V1 and re-issuing a key wider than the caller are refused with 403
• BC-1001-20: keys issued by a Cowork seat are no wider than the seat mode
• NEW-1001-21: POST /v1/cowork/deploy-key names the mode of the minted key
• FIX-1001-22: an application and an empty-slot key are issued in the caller's mode instead of 403
• FIX-1001-23: a third-party agent key is no longer told to obtain a deploy key
• FIX-1001-24: rotatable and rotateBlockedReason account for the calling key mode
• FIX-1001-25: updating a to-do no longer overwrites concurrent edits
• BC-1001-27: string parameters no longer accept arrays and objects
• BC-1001-28: Disk file download links require a Vibecode API key
• NEW-1001-29: the application external API works with a server in the schedule run mode
• BC-1001-30: Explicit refusal for duplicate and missing CRM bindings
• NEW-1001-31: Contact company bindings, lead contact bindings and clear-all
• NEW-1001-32: status change reason in the server activity feed
• NEW-1001-33: The pull_channel scope is available on enabled accounts
• NEW-1001-34: Contact and company call lists
• NEW-1001-35: Recurring deals and immediate template exposure
• FIX-1001-36: postponing a legacy task activity no longer returns a false 422
• NEW-1001-37: Upload chat files without immediate publication
• FIX-1001-38: Your own DeepSeek or OpenAI-compatible provider key receives the model name without the catalog prefix
• NEW-1001-39: CRM sales-intelligence traces
• NEW-1001-40: GET /v1/me states the Bitrix24 data-write restriction on its own
• FIX-1001-41: an immediate bot event re-poll after a refusal about the bot itself no longer gets 409
• NEW-1001-42: Time control and work schedule members
• NEW-1001-43: cause, action and a text for a person in SCOPE_DENIED of chat, CRM, calendar and other routes
• NEW-1001-44: Order dictionaries and basket item properties
• NEW-1001-45: exchange an Atlas access token for a Cowork key and renew that key
• NEW-1001-46: Shipments and shipment items
• NEW-1001-47: cause, action and a text for a person in key scope refusals of the tasks, web search, users and other routes
• NEW-1001-48: connector endpoints for the Cowork desktop