# API changes: November 16, 2026

[← Changelog](/docs/changelog) · [November 2026](/docs/changelog/2026-11)

### NEW-1116-1: MCP load_sources reads snapshots of a standalone server

In `@bitrix24/mcp-vibecode-api`, the `load_sources` tool accepts a `serverId` parameter and reads snapshots saved through `save_sources` with `serverId`, including for a server with no linked app. Exact version selection works through `versionId`, for example `v15`; without `versionId` the newest version of the server is loaded. Requests go to [`GET /v1/infra/servers/:serverId/sources`](/docs/source-storage) and `GET /v1/infra/servers/:serverId/sources/:versionId/download`. Pass exactly one parameter: `serverId` or the app `id`. A server UUID passed as `id` returns `APP_NOT_FOUND` with a hint to pass it as `serverId`, including when `versionId` is omitted; another route is not retried automatically. Both forms preserve version-list errors, including `SOURCE_APP_ID_MISMATCH`, `NOT_AUTHORIZED`, `INTERNAL_ERROR` and `NETWORK_ERROR`. App refusals are no longer masked as missing snapshots; `NO_SAVED_SOURCES` means only a successful request with an empty or missing version list. `sha256` and `savedAt` are returned only when selecting the latest version without `versionId`. Available starting with package version 3.4.5.

### NEW-1116-2: Calls follow-up scope in new keys

New personal keys, Cowork keys and full default scope sets include `syncconnector` for [reading Calls follow-ups](/docs/calls/sync-followup). If the Bitrix24 account refuses issuance with default module scopes, the platform may issue the key without them and reports removed scopes in `removedModuleScopes`. Explicitly selected personal-key scopes are never removed: if the account rejects them, issuance fails. Previously issued keys are not expanded. With the scope present but the module or required update missing, methods return `422 METHOD_NOT_YET_AVAILABLE`.

### NEW-1116-3: App visibility in Bitrix24 independently of external access

[PATCH /v1/infra/servers/:id/access-policy](/docs/infra/access/access-policy) accepts the optional `portalAudience` field: `OWNER_ONLY`, `SPECIFIC_MEMBERS`, or `PORTAL`. With `accessPolicy=PUBLIC` or `AUTHENTICATED`, it controls who sees the app in the Bitrix24 account catalog. Access through the server URL continues to use `accessPolicy`. Selected users and departments come from the existing access list and are preserved. Server responses return both fields. With external access closed, `portalAudience` follows the policy and a conflicting supplied field is ignored; opening `PUBLIC`/`AUTHENTICATED` without the field keeps the previous catalog audience. New servers default to `PORTAL`.

### NEW-1116-4: Image generation is also available on the international platform

Image generation with BitrixGPT 5.6 Image through [POST /v1/images/generations](/docs/ai/images) and [POST /v1/ai/images/generations](/docs/ai/images) is also available on the international Vibecode platform. Find the model in [GET /v1/models](/docs/ai/models/list) by its `capabilities.image_generation` capability. If no such model is listed, image generation is unavailable to your key.

### NEW-1116-5: streamed AI responses send keepalive comments while the model is silent

In a [POST /v1/chat/completions](/docs/ai/chat/streaming) stream with `stream: true`, during a long model pause — for example, while it assembles the arguments of a large tool call — the platform periodically sends a `: keepalive` comment line followed by a blank line. The comment keeps intermediate network hops from closing an idle connection; it carries no data and does not affect the answer, `usage` or the cost. Under the Server-Sent Events specification, lines that start with a colon are skipped: OpenAI-compatible SDKs do this on their own, and a custom stream handler only needs to read `data: ` lines.

The allowed silence is now set per model: models that legitimately stay silent longer get a longer window, and `stream_idle_timeout` arrives only when a model stays silent longer than its own limit.

### NEW-1116-6: a server being deleted together with its host answers 409 SERVER_DELETING

When a galaxy host is deleted, its applications are deleted together with it. Until an application is deleted, [GET /v1/infra/servers/{id}](/docs/infra/servers/get) and [GET /v1/infra/servers](/docs/infra/servers/list) return the field `deleting: true` for it, while `status` keeps its previous value. On the application card the field `deleting: true` appears in `server`. Other servers do not carry the field. `POST /v1/infra/servers/{id}/start`, `/stop`, `/sleep-now`, `/reboot`, `/wake`, `/repair`, `/exec`, `/deploy` and `/upload`, `GET /v1/infra/servers/{id}/logs`, and also `POST /v1/infra/servers/{id}/domain`, `POST /v1/infra/servers/{id}/domain/verify`, `DELETE /v1/infra/servers/{id}/domain` and `POST /v1/infra/servers/{id}/b24-catalog/publish` on such a server answer `409 SERVER_DELETING` and change nothing: the server is not woken, no catalog publication is queued, and `b24CatalogSync.eligible` comes back `false`. `error.userMessage` carries text for a person. Retrying the action does not help.

### NEW-1116-7: Cowork partner limits status

The `GET /v1/cowork/me` and `GET /v1/cowork/state` responses now include `partnerLimits`: whether the partner program is active for the account, whether its free seat matches Pro or exceeds ordinary Free limits, and a confirmed expiry when one exists. The field does not change the tier or quotas.

### FIX-1116-8: access record creation time now comes in UTC

**Before**

[GET /v1/infra/servers/{id}/access](/docs/infra/access/access-list) returned, in `data.users[].createdAt` and `data.departments[].createdAt`, the creation time shifted by the platform's time zone offset: for records added through the access list, the time differed from the actual moment of addition.

**After**

Both fields return the actual creation time in UTC.

**Impact on integrators**

Requests do not change. If you compensated for the shift yourself, remove that correction: records added before the fix keep the previous value, so one list contains both variants, and the "newest first" order between them may not match the actual order of addition.
