API changes: August 2026

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

August 31, 2026

• FIX-0831-1: a server whose agent never came up is no longer reported as running
• FIX-0831-2: key issuance on a free plan now names the cause instead of "retry in a minute"
• FIX-0831-3: search and research through the Linkup provider
• FIX-0831-4: seamless dashboard sign-in from a signed Bitrix24 form
• FIX-0831-5: opening an application from the Bitrix24 catalog always acts as an account
• FIX-0831-6: Batch create of telephony lines returns the addressable number in results[].id
• FIX-0831-7: signing back into Cowork on a fee-free seat no longer fails
• FIX-0831-8: TOKEN_MISSING for a personal key now names the webhook mint failure
• FIX-0831-9: vibe top-up is open to self-hosted accounts on the international installation

August 30, 2026

• BC-0830-1: Presigned single-PUT upload is temporarily disabled
• BC-0830-2: an application rename no longer reports success without confirmation from Bitrix24
• FIX-0830-3: for bitrix/* models a stream that never started also ends with a retryable error

August 29, 2026

• FIX-0829-1: importable field flag in guide
• NEW-0829-2: a link to a public app expands into a card
• BC-0829-3: lead filters now support stage semantics
• FIX-0829-4: mailbox and org-structure node list calls work in the batch APIs

August 28, 2026

• FIX-0828-1: stopping a server is no longer billed as a full running hour
• FIX-0828-2: a late upload through a valid URL preserves the object
• FIX-0828-3: GET /v1/guide returns the paging rules as a single paginationCanon block
• FIX-0828-4: task comment filter and sort accept camelCase field names
• BC-0828-5: Deploy outcomes can be confirmed after a dropped connection
• FIX-0828-6: task comment creation returns the correct numeric ID
• BC-0828-7: incomplete public uploads are no longer anonymously accessible
• FIX-0828-8: MCP returns the Drive file content instead of a network error
• FIX-0828-9: concurrent direct uploads of one object are coordinated
• FIX-0828-10: create and update response specifications reflect the identifier
• FIX-0828-11: commands in a galaxy app are no longer refused before dispatch
• FIX-0828-12: Node.js 20 runtime templates install more reliably
• FIX-0828-13: A ZIP deploy no longer asks you to change the archive format when the server is busy with another command
• FIX-0828-14: a payment with an inflated vibe count is held instead of rejected
• FIX-0828-15: a pending-deletion owner's key no longer calls Bitrix24 methods through V1
• BC-0828-16: include now requires the scope of the related entity
• NEW-0828-17: include for requisites, workgroups and product sections
• FIX-0828-18: select combined with include no longer empties the relation on list and search
• NEW-0828-19: the current-user profile is now in the specification and the reference
• FIX-0828-20: topUpAvailable for a self-hosted account reflects the self-hosted checkout
• FIX-0828-21: the auth key now gets the scopes the Bitrix24 account actually grants
• FIX-0828-22: an employee photo can be written through the API again

August 27, 2026

• NEW-0827-1: aggregation marks a partial total next to the number itself
• BC-0827-2: runtime installation order and nginx startup have changed
• NEW-0827-3: unfinished BOX account reason and employee identity transfer between accounts
• FIX-0827-4: unfinished BOX account connection is visible in the list
• FIX-0827-5: user invitations preserve all profile fields
• FIX-0827-6: single comment lookup finds a comment with a string identifier
• FIX-0827-7: contact select accepts typed email addresses again
• FIX-0827-8: tariff headers are returned for infrastructure requests
• NEW-0827-9: array element schemas are available in field contracts
• FIX-0827-10: lists without a total no longer look complete too early
• NEW-0827-11: the self-description now points at the Cowork/Code promo code docs
• FIX-0827-12: the Cowork/Code rate limits no longer quote a number the client never receives
• FIX-0827-13: telephony line creation returns a usable key
• NEW-0827-14: time entry lists explicitly reject unsupported filter envelopes
• FIX-0827-15: PUBLIC app robots.txt is available to crawlers
• FIX-0827-16: entity filters are no longer lost on list calls
• FIX-0827-17: the application access list contains Bitrix24 account employees only
• FIX-0827-18: the connect step of repair status no longer fails for an agent that did connect

August 26, 2026

• FIX-0826-1: socnetGroupId now works on the nested resources of workgroup lists
• BC-0826-2: exec into a Galaxy app answers CONTAINER_NOT_READY instead of a false success
• FIX-0826-3: 404 responses for Bitrix24 method names now point to the V1 route
• FIX-0826-4: Neutral offset in the English createdDate description
• NEW-0826-5: creating an application from the Cowork/Code desktop — two new endpoints
• FIX-0826-6: work schedule answers with a clear error when the required id is missing
• NEW-0826-7: an app is no longer granted the vibe:infra scope on accounts with infrastructure disabled
• NEW-0826-8: the vibe:infra scope can no longer be added to an app by editing its scopes
• NEW-0826-9: managing a galaxy server is blocked while galaxies are disabled for the account
• NEW-0826-10: the vibe:infra scope is no longer granted on accounts with infrastructure disabled
• NEW-0826-11: scope requirements map in the key self-description
• FIX-0826-12: bracket-form sorting of task comments, ?sort[field]=direction
• FIX-0826-13: waking an app on a failed Galaxy host now ends with an explicit error
• FIX-0826-14: Bitrix24 registration failures no longer expose the vendor's internal text

August 25, 2026

• FIX-0825-1: an application card now gets its server on galaxy accounts too
• BC-0825-2: a read-only key no longer writes on platform endpoints
• FIX-0825-3: /v1/me no longer reports app creation as unavailable to a read-only key
• BC-0825-4: a Cowork desktop key can no longer change OAuth application registrations
• BC-0825-5: re-uploading a file now replaces its content instead of failing with 500
• BC-0825-6: the binding and author fields of a timeline comment no longer look editable
• BC-0825-7: deploy base version is required when the top saved source version belongs to somebody else too
• NEW-0825-8: a server's development-team member now sees its application in the catalog
• FIX-0825-9: include is advertised only for entities with relations
• BC-0825-10: Inline archive cap on the deploy body narrowed to 96 MB
• NEW-0825-11: GET /v1/me now names the archive equivalent of the inline cap as its own field
• BC-0825-12: POST /v1/apps now honours the Bitrix24 account policy for who may create apps
• FIX-0825-13: Node.js 20 runtime setup no longer repeats completed steps
• FIX-0825-14: placement bind answers 400 for an over-long iconName instead of a reasonless 502

August 24, 2026

• BC-0824-1: activity type can no longer be changed after creation
• FIX-0824-2: paid accounts no longer receive an error asking them to pay again
• BC-0824-3: the deployment block changes shape for Belarusian accounts along with their access model
• NEW-0824-4: the Bitrix24 plan becomes the access condition for accounts licensed in Belarus
• FIX-0824-5: the server-creation hint in the key response no longer leads nowhere
• FIX-0824-6: the denial text for Kazakhstan and Uzbekistan no longer offers a subscription
• BC-0824-7: bot re-authorization is now explicit and safe
• FIX-0824-8: galaxy application deploy warns when environment variables are reset
• NEW-0824-9: task dependencies are now available through the API
• FIX-0824-10: international bot access keeps the Bitrix24 plan model
• BC-0824-11: opening a workday no longer confirms an expired state
• NEW-0824-12: calendar events can be linked to CRM elements
• FIX-0824-13: an application on a galaxy host that does not boot can be deleted without a live tunnel
• BC-0824-14: an unknown select field name is refused with 400 on almost every entity
• FIX-0824-15: the datePeriod field schema is now visible in GET /v1/bookings/fields
• NEW-0824-16: Scrum kanban stages and sprint listing in the API
• FIX-0824-17: ACCOUNT_FROZEN is now documented on server creation

August 23, 2026

• BC-0823-1: OpenAPI no longer offers create-only fields in PATCH
• NEW-0823-2: several employees can work on one application's code
• FIX-0823-3: platform public URLs no longer point away from the stand

August 22, 2026

• NEW-0822-1: promo code on an occupied seat: the preview returns branches and redemption executes them
• BC-0822-2: the create and rotate responses now match the documented key shape
• BC-0822-3: key rotation now requires the same Bitrix24 plan as creation
• NEW-0822-4: a key now reports the channel it was issued through, and a refusal reports its exact cause
• FIX-0822-5: a rotation refused over scopes now reports the same code on every account
• NEW-0822-6: platform requests to Bitrix24 now carry a signed origin proof
• FIX-0822-7: Reliable source downloads for dedicated VM deploys
• BC-0822-8: rotating and bringing back platform-issued keys is closed
• NEW-0822-9: POST /v1/cowork/deploy-key is closed to external-agent keys
• NEW-0822-10: Reactivating a subscription key checks the issuance gates
• NEW-0822-11: Rotating a subscription key checks the issuance gates
• NEW-0822-12: POST /v1/keys rejects subscription billing
• FIX-0822-13: The inactive-subscription refusal now points at the subscription page

August 21, 2026

• FIX-0821-1: iblockTypeId=structure is accepted on /v1/lists
• FIX-0821-2: currencyId and explicit selection of non-returned fields
• FIX-0821-3: product description filter is no longer rejected
• FIX-0821-4: the refusal on creating an employee without a department now names the field to pass
• NEW-0821-5: Open Channels dialog metadata via the API
• BC-0821-6: a structured value in a scalar field is refused instead of silently lost
• FIX-0821-7: PATCH /v1/infra/servers/:id/access-policy now preserves the access list on policy change
• BC-0821-8: a busy shared galaxy exec channel now answers 409 instead of 502
• BC-0821-9: the per-entity batch now explains what it did with select
• NEW-0821-10: Open Channels session transcript via the API
• NEW-0821-11: galaxy app multipart deploy stores the archive in source storage

August 20, 2026

• NEW-0820-1: the Cowork subscription snapshot is described in the API specification
• FIX-0820-2: include examples use relation names
• FIX-0820-3: MCP now forwards timeline log action parameters correctly
• NEW-0820-4: calendar sections now expose schema and search routes
• FIX-0820-5: personal keys report only executable scopes
• FIX-0820-6: the tasks permission now works on every task operation, no matter how the key was issued
• FIX-0820-7: bot chat creation returns the identifier the other actions accept
• FIX-0820-8: AI provider refusal: a readable message instead of relayed prose, and one error shape for streaming and non-streaming
• FIX-0820-9: an attachment whose extension does not match its content is no longer rejected
• FIX-0820-10: MCP now preserves one chat identifier format
• FIX-0820-11: addresses now apply select — records narrow, and an unknown name is no longer lost
• BC-0820-12: a caller-supplied bot token is validated for length and alphabet
• FIX-0820-13: bot events delivered by webhook without a Bitrix24 address are no longer lost
• FIX-0820-14: the account receives Bitrix24 scopes only, and a platform-only key no longer gains a webhook on rotate
• FIX-0820-15: on the international segment the tariff refusal names a Vibe+ plan
• NEW-0820-16: assigned promo code — the code works only for its recipient
• NEW-0820-17: blocking a leaked key now reports whether its access links were revoked
• FIX-0820-18: revoking a key now closes the access links it issued

August 19, 2026

• FIX-0819-1: bot message sending accepts top-level dialogId
• FIX-0819-2: the X-Tariff-Checked-At header is sent only after a successful plan lookup
• FIX-0819-3: clarified personal-key embedding and handled OAuth without state
• FIX-0819-4: money paths now survive a race for the shared account balance
• BC-0819-5: the freshnessWindowMinutes field is no longer returned
• BC-0819-6: publication refuses when the files of the saved source version are gone
• FIX-0819-7: app publication no longer refuses because the saved sources are old
• FIX-0819-8: Publishing an app no longer marks the source version as successfully deployed
• BC-0819-9: promo code on a closed seat: the COUPON_SEAT_CANCELLED refusal is gone
• FIX-0819-10: a promo code no longer eats the paid term of a downgraded seat
• BC-0819-11: an unbind the platform could not confirm no longer looks like success
• NEW-0819-12: a self-hosted portal can start the Marketplace demo
• BC-0819-13: request body parsing for POST /v1/cowork/deploy-key
• NEW-0819-14: revoking a Cowork/Code device key with the key itself

August 18, 2026

• BC-0818-1: application and source-management contract clarified
• FIX-0818-2: ?refresh=tariff on a self-hosted portal re-checks its access state at the source
• NEW-0818-3: workgroup roster with member roles
• FIX-0818-4: deals: seven fields from GET /v1/deals/fields are now accepted in a filter
• FIX-0818-5: empty workday method results are returned as null
• NEW-0818-6: the field reference for orders and order statuses now returns names and explanations
• NEW-0818-7: machine issuance of promo codes: three V1 methods and two new integration-key scopes
• NEW-0818-8: promo codes for Cowork/Code tiers and the refusal codes of redemption
• NEW-0818-9: promo code in the Cowork/Code app: check a code and redeem it with a desktop key
• NEW-0818-10: applications catalog in the API: list and card

August 17, 2026

• FIX-0817-1: repeated PostgreSQL runtime deploy no longer fails on an existing database
• FIX-0817-2: calls statistics reference shows working filters and sorting
• FIX-0817-3: the Cowork/Code deploy-key mint now recovers a fleet stranded by earlier mints
• NEW-0817-4: quota relief is visible in the Cowork/Code subscription responses
• NEW-0817-5: notification type dictionary
• NEW-0817-6: Bitrix24 account calendar settings are available through the API

August 16, 2026

• NEW-0816-1: the app icon accepts raster files, and a Bitrix24 account can push one itself
• NEW-0816-2: two fields describing a temporary limit increase in the Cowork/Code state
• NEW-0816-3: new 402 company_budget_exhausted rejection on calls that spend credits
• FIX-0816-4: the Cowork deploy-key handout no longer loses servers

August 15, 2026

• BC-0815-1: combo runtimes with a database no longer slip into Galaxy silently
• NEW-0815-2: the bound placements list now states whether the account was checked
• FIX-0815-3: AI quota is resolved by plan in every Western zone
• NEW-0815-4: an app can be added to the Bitrix24 catalog with a dedicated call
• FIX-0815-5: the Cowork monthly limit now follows the tier grid without waiting for a renewal

August 14, 2026

• NEW-0814-1: thirty-one more live operations are now in the machine schema
• BC-0814-2: port pinning refuses instead of confirming falsely
• FIX-0814-3: the dimensions parameter for the bitrix/embeddings model
• FIX-0814-4: leading service markers are no longer included in model content
• FIX-0814-5: the blocking server wake returns WAKE_TIMEOUT far less often on a cold start
• FIX-0814-6: a fractional or malformed path id no longer returns a DIFFERENT record
• NEW-0814-7: reading the notification feed and the unread counter
• NEW-0814-8: Workday history in the V1 API
• FIX-0814-9: the INT_VIBE_PLUS_REQUIRED refusal now points at the plan page inside the account
• BC-0814-10: audio transcription accepts the file only in the file field, never truncates it silently, and returns a recognition refusal as 400
• NEW-0814-11: catalog product image metadata
• NEW-0814-12: audio transcription can now draw on the Cowork/Code subscription quota
• FIX-0814-13: a wake schedule no longer shortens the auto-sleep you set
• NEW-0814-14: a write with a lossy-charset value now reports it

August 13, 2026

• FIX-0813-1: a failed native-module build now states its own cause instead of "Python not found"
• FIX-0813-2: API response shapes are described in the machine-readable schema
• NEW-0813-3: the real state of a sleeping galaxy app in the server GET and in the logs answer
• FIX-0813-4: file download declares its required scope in openapi.json
• FIX-0813-5: A readable build error instead of raw builder output and external addresses
• NEW-0813-6: the agent bundle manifest now reports the runtime verification mode
• NEW-0813-7: the agent bundle manifest gained a targeted runtime repair operation
• FIX-0813-8: The reauth refusal no longer advises OAuth to keys that have none
• FIX-0813-9: deleting a galaxy app on a host that cannot be woken now answers a terminal 409
• NEW-0813-10: the Marketplace trial can be started from a Cowork/Code desktop key
• FIX-0813-11: transient errors no longer close the trial for good
• FIX-0813-12: activating the trial again allows three attempts per hour
• NEW-0813-13: new access refusal code INT_VIBE_PLUS_REQUIRED
• NEW-0813-14: Cowork/Code state now reports the paid term
• FIX-0813-15: a server rename now shows up in the dashboard

August 12, 2026

• NEW-0812-1: nextPollAfterMs — the platform can ask you to poll events less often
• FIX-0812-2: touSavedPct is now a share of the monthly allowance, not of consumption
• NEW-0812-3: The app port is pinned to the server and survives a wake
• BC-0812-4: context in feedback submissions must be a JSON object
• NEW-0812-5: app publication accepts sources from a named server
• NEW-0812-6: deal product rows: the response now signals truncation
• NEW-0812-7: the machine schema now describes the live app, AI and telephony methods
• FIX-0812-8: the free-tier plan list is returned as the public identifier
• FIX-0812-9: Requisite custom-field filtering is corrected
• FIX-0812-10: an unconfirmed Marketplace trial activation now answers pending instead of activated
• FIX-0812-11: a dedicated-machine deploy keeps the build's internal links and checks the application root
• BC-0812-12: task time numeric fields are returned as numbers, not strings
• FIX-0812-13: a filter with a reserved field name is rejected instead of returning the whole collection
• FIX-0812-14: a key allowed to deploy can also patch the application on that server
• FIX-0812-15: room in a shared galaxy is decided by the machine's own measurement, not by a fixed seat count
• NEW-0812-16: deploy operation id and after-the-fact outcome reconciliation
• NEW-0812-17: A failed deploy reports its outcome as data, not prose

August 11, 2026

• NEW-0811-1: server plans now name their price unit
• NEW-0811-2: the application data directory is declared in the deploy body
• NEW-0811-3: issuing a key with exactly the selected platform rights
• NEW-0811-4: off-peak hours are visible in the Cowork/Code subscription and in the exhausted-quota refusal
• FIX-0811-5: the next off-peak hour is counted from the hour boundary, not from the minute of the request
• BC-0811-6: a server whose operating system does not boot answers with a dedicated code
• NEW-0811-7: the "app is not responding" reply now has a separate code for a server with no deploy
• FIX-0811-8: document template creation declares its required scope in openapi.json
• FIX-0811-9: Requisite user fields in responses
• NEW-0811-10: granted_scopes — the issued key's actual scopes in the exchange response
• FIX-0811-11: OpenAPI: required scopes for bespoke operations
• FIX-0811-12: the /v1/guide reference returns a docs link for the telephony-lines entity
• FIX-0811-13: a write with Content-Type: text/plain is now rejected instead of creating an empty record
• BC-0811-14: deploy no longer reports success when the port stayed with the previous process
• NEW-0811-15: Cowork/Code tier change cost preview
• FIX-0811-16: app install failure message now names the Bitrix24 answer
• FIX-0811-17: read-only keys no longer reject read operations as writes
• BC-0811-18: marking messages read now requires a key with write access
• FIX-0811-19: five more read operations stopped being rejected under a read-only key
• NEW-0811-20: Cowork/Code state tells the account how to open up work with Bitrix24
• FIX-0811-21: Cowork/Code state now has a polling ceiling
• FIX-0811-22: the upgrade link in the capabilities response no longer leads nowhere
• FIX-0811-23: the ai_congested retry pause now scales with the configured base and is capped
• NEW-0811-24: an interrupted galaxy deploy now names its cause and flags repeats
• FIX-0811-25: galaxy app creation now reports that the provider, plan and region you sent were not applied
• BC-0811-26: uploading a file to a galaxy app is refused instead of writing to the shared server
• FIX-0811-27: an app from the Bitrix24 catalog now opens for an employee with no Vibecode account
• BC-0811-28: AI requests now carry a service deadline: a 429 refusal instead of a hang
• FIX-0811-29: the server region catalog on the international version no longer returns zones from unavailable regions

August 10, 2026

• NEW-0810-1: issuing a share link is recorded in the account access journal
• BC-0810-2: a filter error in POST /v1/{entity}/batch is now a per-sub-call error, not a whole-request one
• BC-0810-3: batch reads no longer bypass an operation the entity turns off
• BC-0810-4: a filter that is not an object is refused instead of being lost
• BC-0810-5: an unknown filter field name is refused on fifteen more entities
• FIX-0810-6: a host out of free disk space is a distinct retryable deploy failure, not a broken app
• FIX-0810-7: A catalog launch now warns that the app is not authorized
• NEW-0810-8: CRM document list now present in the machine-readable OpenAPI schema
• FIX-0810-9: a direct-link visit now carries the visitor's name and access token
• FIX-0810-10: invoice user fields
• BC-0810-11: The product-row field reference now describes what the responses actually contain
• FIX-0810-12: server member lookup no longer comes back empty because of a recent key without Bitrix24 access
• FIX-0810-13: placement bind names the install-rights refusal instead of a generic gateway error
• BC-0810-14: commands, deploys and file uploads addressed by a galaxy host id are refused
• NEW-0810-15: galaxy host disk usage is exposed in the server list
• NEW-0810-16: agent model bitrix/bitrixgpt-5.6-agent
• NEW-0810-17: bitrix/bitrixgpt-5.5-agent is deprecated
• FIX-0810-18: a transient database transaction failure no longer returns 500 with an internal engine code
• FIX-0810-19: preserveEnv no longer loses .env when a deploy fails after the directory is cleaned

August 9, 2026

• BC-0809-1: meta.total is no longer returned by default in lists

August 7, 2026

• NEW-0807-1: CRM record import: the original author and dates, with no automation run
• FIX-0807-2: a source version deploys by its number on its own server
• FIX-0807-3: reading and updating a nonexistent activity answers 404, not 422
• FIX-0807-4: a body-less request reaches its handler instead of failing at parse time
• BC-0807-5: commenting on your own ticket no longer looks like a platform reply
• BC-0807-6: an AI agent's server no longer accepts an application deploy
• NEW-0807-7: GET /v1/cowork/state reports a scheduled downgrade
• FIX-0807-8: the galaxy host now fetches the source archive itself
• FIX-0807-9: a deploy no longer fails while stopping a slow application
• FIX-0807-10: renaming a requisite preset field is checked before the write
• NEW-0807-11: field schema for task time tracking
• FIX-0807-12: labels and descriptions for the daysBeforeClose, fm and FILES fields in the /fields response
• FIX-0807-13: the feedback list now honours the bracket filter form
• FIX-0807-14: updating an order no longer loses the amount, the mark, and its reason silently
• NEW-0807-15: deploy now reports a displayName or description it did not apply
• FIX-0807-16: reopening a ticket no longer erases the resolution text
• BC-0807-17: an activities aggregate needs a narrowing filter
• FIX-0807-18: a file in a CRM field no longer hits the 1 MB wall, and the refusal code is documented

August 6, 2026

• NEW-0806-1: 402 for an exhausted Cowork/Code quota carries a Retry-After header
• FIX-0806-2: Web search: the response status distinguishes a provider key rejection from a provider failure
• FIX-0806-3: the operation registry in GET /v1/guide now lists what actually works
• FIX-0806-4: the task service fields are accepted on writes — exactly as Bitrix24 itself accepts them
• FIX-0806-5: a catalog application card opens its subpath instead of the server root
• FIX-0806-6: speech recognition now reports a temporary provider pause
• FIX-0806-7: speech recognition now really waits the stated 15 minutes
• FIX-0806-8: galaxy app exec now targets the container by its real name
• BC-0806-9: V1: server status in JSON is always lowercase
• NEW-0806-10: deploying a galaxy app from a link or a saved version
• FIX-0806-11: the smart-process items field reference no longer shows the contacts field
• FIX-0806-12: the pages field reference now says which fields can be empty
• NEW-0806-13: the key-limit refusal now states the numbers
• NEW-0806-14: the site and employee field maps now carry labels, descriptions and value lists
• FIX-0806-15: product sections: the sort field is marked read-only and not-returned
• FIX-0806-16: the active field of a site is read-only now — activation goes through publishing
• FIX-0806-17: base image registry unavailable during a galaxy app build is now transient, not fatal
• FIX-0806-18: issuance refusals now name a service problem instead of an access one
• FIX-0806-19: the platform now passes the application its port in the PORT variable
• BC-0806-20: quota consumption is reported as percentages only
• FIX-0806-21: an exhausted Cowork/Code quota is no longer served by a substitute model
• FIX-0806-22: server repair now reports why it failed and no longer leaves the agent stopped
• FIX-0806-23: key issuance now checks platform access
• NEW-0806-24: a clear refusal when a personal key is left with only placement or entity
• FIX-0806-25: a Galaxy Python build no longer fails on a version that exists

August 5, 2026

• FIX-0805-1: key rotation no longer strands the bot registered with it
• FIX-0805-2: a container on a shared host is no longer lost after key rotation
• FIX-0805-3: key rotation no longer disconnects the server and app bound to it
• BC-0805-4: the task field reference now matches the task response, and numbers are numbers
• FIX-0805-5: the model-unavailable pause now lengthens until the cluster recovers
• NEW-0805-6: deploy warns when the verified app path disagrees with the address Bitrix24 opens
• FIX-0805-7: Placement binding names the reason it was refused
• FIX-0805-8: the tunnel survives an app restart, and port auto-detection no longer loses the target
• FIX-0805-9: the MISSING_FIELDS hint for requisite links names the field names instead of sending you to another endpoint
• FIX-0805-10: the API schema now covers the session exchange and embed slots, and states its own coverage honestly
• FIX-0805-11: a client on a smart process item is written, and a disabled client block answers with a refusal instead of a false success
• FIX-0805-12: a JSON-object filter is applied, and an OR attempt gets its own error code
• FIX-0805-13: a galaxy build failure is no longer reported as npm help text
• FIX-0805-14: employee directory resolves through the server owner's personal key
• FIX-0805-15: on a self-hosted account a module refusal ends the issuance again
• NEW-0805-16: region is now optional when creating a server
• NEW-0805-17: fields of six directories now come with a name and a description
• FIX-0805-18: an empty value of the declared company fields now arrives as null, and a write to them is no longer silently ignored
• FIX-0805-19: the active field of a site page is read-only now — publishing goes through its own call
• NEW-0805-20: creating a server with inline code joined the shared queue for heavy requests
• FIX-0805-21: repair restores the tunnel even when inbound SSH is unavailable
• FIX-0805-22: placement binding: when Bitrix24 names the reason, so do we
• FIX-0805-23: a personal key with no Bitrix24 webhook now says what it is missing
• FIX-0805-24: the app subdomain answers machines with JSON instead of a page, and survives a brief tunnel drop
• FIX-0805-25: the feedback quota is counted per key, not shared across all callers
• FIX-0805-26: Open Channels configuration paging: the window is no longer shifted twice
• BC-0805-27: aggregate over a large pipeline: per-stage counts without reading deals, refusal instead of truncation

August 4, 2026

• BC-0804-1: V1 /wake and /start wake galaxy apps via the host
• BC-0804-2: the declared archive type is now checked against the first bytes
• NEW-0804-3: field names and descriptions for product sections, requisite presets and bank details
• NEW-0804-4: limit=0 is no longer ignored silently
• FIX-0804-5: bank details: entityTypeId marked as a field that is never returned
• FIX-0804-6: discover names the real path identifier
• FIX-0804-7: telephony lines: name declared nullable, serverName marked as never returned
• FIX-0804-8: workgroups: limit > 50 and row-exact offset now work
• FIX-0804-9: deleting an application now completes its removal from the account
• NEW-0804-10: Gateway timeout on exec now carries a recovery hint
• FIX-0804-11: model-unavailable refusal is now 429 with a wait hint, not 502
• FIX-0804-12: a multipart archive deploy now keeps the source version even when the deploy fails
• NEW-0804-13: address fields come with human-readable labels and descriptions
• NEW-0804-14: product fields come with labels, descriptions and a description-format dictionary
• NEW-0804-15: all 45 quote fields come with a label and a description
• NEW-0804-16: catalog product fields come with labels and descriptions
• FIX-0804-17: requisite preset field schema declares inShortList as boolean
• NEW-0804-18: downloading call recordings and timeline attachments
• FIX-0804-19: a bot message without text is refused with a clear error instead of a false success

August 3, 2026

• FIX-0803-1: reopening an archived ticket now clears the resolution stamp too
• FIX-0803-2: missing attachment bytes now answer 404 instead of a truncated response
• FIX-0803-3: server creation now says plainly when it returned the application's existing server
• NEW-0803-4: dictionary of catalog list-property values
• FIX-0803-5: Support tickets work while the account is balance-frozen
• FIX-0803-6: include now returns the full related record, not just link metadata
• FIX-0803-7: rolling-out Open Channels dashboard methods return METHOD_NOT_YET_AVAILABLE
• FIX-0803-8: source-storage writes return precise error codes instead of a generic 500
• FIX-0803-9: a value list in a statuses filter is rejected with a clean 400, not a 500
• FIX-0803-10: /v1/tasks/:taskId/time accepts a key with the task scope
• NEW-0803-11: the one-shot galaxy app create now accepts healthPath
• FIX-0803-12: /start and /wake on a galaxy app now explain why they do not apply
• FIX-0803-13: a galaxy app failure now names its actual cause in provisionError
• FIX-0803-14: /reboot on a sleeping galaxy app now kicks the host repair and says so
• FIX-0803-15: a zip source archive no longer fails at extraction on a galaxy app
• NEW-0803-16: Source versions accept up to 500 MB, and a deploy from our own link now links to the version on any key
• FIX-0803-17: revoking access kills every key of the connection, not just the latest

August 2, 2026

• FIX-0802-1: a batch sub-call with its own start=-1 no longer returns a fabricated total
• BC-0802-2: self-hosted account access is no longer granted unconditionally

August 1, 2026

• FIX-0801-1: AI endpoint response bodies no longer carry platform-internal fields
• FIX-0801-2: galaxy app deploy no longer reports an interruption after an update that actually succeeded
• BC-0801-3: publication checks application authorization before snapshot freshness
• NEW-0801-4: hints in publication responses: hint on NO_USER_TOKEN and presentedAt on SNAPSHOT_REQUIRED
• FIX-0801-5: re-saving the same sources unblocks publication
• BC-0801-6: a broken exec no longer answers with success and exitCode -1
• FIX-0801-7: the JSON response body of /exec and /deploy now starts with an opening brace
• FIX-0801-8: datetimes without a timezone no longer drift when the caller's zone differs from the webhook owner's
• FIX-0801-9: bot deletion is idempotent: "bot already gone" now succeeds instead of returning 502
• FIX-0801-10: Bitrix24 error messages no longer carry HTML markup
• NEW-0801-11: CALL_CARD placement — panel inside the call card
• FIX-0801-12: four silent refusals: activities, warehouses, files, user fields
• NEW-0801-13: task service fields now carry names, descriptions and a dictionary of accepted values