[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-changelog\u002F2026-07-13":3,"docs-tabs-changelog\u002F2026-07-13":6},{"content":4,"lastmod":5},"# API changes: July 13, 2026\n\n[← Changelog](\u002Fdocs\u002Fchangelog) · [July 2026](\u002Fdocs\u002Fchangelog\u002F2026-07)\n\n### FIX-0713-1: OAuth application key platform scopes now sync on create and edit\n\n**Before**\n\nA key issued together with an OAuth application via [POST \u002Fv1\u002Fapps](\u002Fdocs\u002Fapps) did not receive the platform scopes (`vibe:infra`, `vibe:ai`, `vibe:search`, `vibe:storage`) that a key created in the dashboard gets. As a result [POST \u002Fv1\u002Finfra\u002Fservers](\u002Fdocs\u002Finfra\u002Fservers) under such a key returned 403 `INFRA_SCOPE_REQUIRED`. Adding `vibe:infra` to the app's scopes via [PATCH \u002Fv1\u002Fapps\u002F:id](\u002Fdocs\u002Fapps) changed only the app, not the paired key — so it had no effect on access.\n\n**After**\n\nThe paired key created via `POST \u002Fv1\u002Fapps` now receives the same default platform scopes as a key created in the dashboard. A `vibe:*` scope change via `PATCH \u002Fv1\u002Fapps\u002F:id` (both add AND remove) now propagates to the app's active keys. A read-only (READONLY) key is rejected with 403 `WRITE_BLOCKED_READONLY_KEY` on three write operations: server creation (`POST \u002Fv1\u002Finfra\u002Fservers`), app scope change (`PATCH \u002Fv1\u002Fapps\u002F:id`), and READWRITE key issuance (`POST \u002Fv1\u002Fapps` with `mode: \"READWRITE\"`).\n\n**Impact on integrators**\n\nApps created via the API can now manage infrastructure without re-creation. A key whose app already declares `vibe:infra` while the key itself lacks it (the old divergence) is fixed with one edit: remove `vibe:infra` from the app's scopes and add it back via `PATCH \u002Fv1\u002Fapps\u002F:id` — the second edit syncs the key; or re-create the app. A READONLY key can still create a READONLY app (`mode: \"READONLY\"`).\n\n### FIX-0713-2: product-sections: unsupported filters return 400 instead of the whole table\n\n**Before**\n\nOperators (`>`, `\u003C`, `!`, `%`, `$ne`, `$contains`, `$nin`) and non-exact-match fields (`sort`, unknown) in the filter of [GET \u002Fv1\u002Fproduct-sections](\u002Fdocs\u002Fentities\u002Fproduct-sections\u002Flist) and [POST \u002Fv1\u002Fproduct-sections\u002Fsearch](\u002Fdocs\u002Fentities\u002Fproduct-sections\u002Fsearch) were silently ignored — the code 200 and the whole list were returned unfiltered.\n\n**After**\n\nSuch filters are rejected with `400 UNSUPPORTED_FILTER`. Filter by exact match or `$in` on `id`, `name`, `xmlId`, `code`, `catalogId`, `sectionId`. Sorting (`order`\u002F`sort`) is unchanged.\n\n**Impact on integrators**\n\nCalls with operators or `filter[sort]` that previously returned 200 with unfiltered data now return `400` — switch to exact match or `$in`.\n\n### FIX-0713-3: the reason for a failed first server provisioning is now visible\n\n**Before**\n\nIf a server failed to come up on its first creation (a preemptible plan evicted, no free capacity), it silently ended up in `sleeping` status with no explanation. A client polling [GET \u002Fv1\u002Finfra\u002Fservers\u002F:id](\u002Fdocs\u002Finfra\u002Fservers\u002Fget) saw `sleeping` and could not tell why the deploy was blocked.\n\n**After**\n\nSuch a server now moves to `status: \"error\"` with a populated `provisionError` (a human-readable reason) and a new `provisionErrorCode` field — a machine-readable failure category (`PREEMPTIBLE_EVICTION` \u002F `PROVISION_TIMEOUT` \u002F `NO_CAPACITY` \u002F `GENERIC`). The `provisionErrorCode` field is added to [GET \u002Fv1\u002Finfra\u002Fservers\u002F:id](\u002Fdocs\u002Finfra\u002Fservers\u002Fget) and [GET \u002Fv1\u002Finfra\u002Fservers](\u002Fdocs\u002Finfra\u002Fservers\u002Flist) next to `provisionError` (additive, `null` when there were no errors).\n\n**Integrator impact**\n\nNo action needed: `error` is an already-existing status. Recover such a server via `POST \u002Fv1\u002Finfra\u002Fservers\u002F:id\u002Fstart` or `\u002Frepair` (not `\u002Fwake`: on `error` status it returns `422`; the `availableActions` field in the response points to the available action).\n\n### NEW-0713-4: POST and PATCH \u002Fv1\u002Ftasks\u002F:taskId\u002Ftime accept createdDate\n\nAn optional `createdDate` field is now forwarded on [POST \u002Fv1\u002Ftasks\u002F:taskId\u002Ftime](\u002Fdocs\u002Fentities\u002Ftasks\u002Ftime\u002Fcreate) and [PATCH \u002Fv1\u002Ftasks\u002F:taskId\u002Ftime\u002F:itemId](\u002Fdocs\u002Fentities\u002Ftasks\u002Ftime\u002Fupdate) — the time entry lands on the given date instead of the current moment (backfilling last week's tracks). ISO 8601 with offset, bare ISO, and `YYYY-MM-DD` are all accepted and passed to `CREATED_DATE` verbatim. When the field is omitted the behaviour is unchanged — the date equals the creation moment.\n\n### FIX-0713-5: meta.hasMore no longer stays stuck at true with filter + offset\n\n**Before**\n\nWhen paginating a filtered list (for example [GET \u002Fv1\u002Fdeals](\u002Fdocs\u002Fentities\u002Fdeals\u002Flist) with `filter` and `offset`), `meta.hasMore` stayed `true` at every offset — even well past `meta.total`. A `while (meta.hasMore) { offset += limit }` loop ran forever.\n\n**After**\n\nWhen Bitrix24 ignores an offset beyond the filtered set and returns the whole set, `meta.hasMore` is derived from the request window (`offset + limit \u003C meta.total`) instead of being forced to `true`. At `offset=0` the response is unchanged; once the window passes `total`, `hasMore` becomes `false`. Applies to list and `POST \u002Fsearch` across all entities.\n\n### FIX-0713-6: GET \u002Fv1\u002Flists and \u002Fv1\u002Flists\u002F:iblockId\u002Felements honour offset\n\n**Before**\n\n[GET \u002Fv1\u002Flists\u002F:iblockId\u002Felements](\u002Fdocs\u002Flists\u002Felements) and [GET \u002Fv1\u002Flists](\u002Fdocs\u002Flists\u002Flists) silently ignored `offset` — `?limit=50&offset=50` returned the same first page, and a client paginating by `offset` never reached rows 51 and beyond.\n\n**After**\n\n`offset` is mapped to `start`, the native pagination param for these methods, so `offset`-based paging works. An explicit `start` keeps priority when both are supplied.\n\n### NEW-0713-7: New preserveEnv flag keeps .env across cleanDeploy\n\nThe `POST \u002Fv1\u002Finfra\u002Fservers\u002F:id\u002Fdeploy` body gained an optional boolean `preserveEnv` (default `false`). When `cleanDeploy: true` (which wipes the app directory including the `.env` file) and `preserveEnv: true`, the existing `.env` is read before the wipe and restored afterwards unless this request also passes `env` (a supplied `env` wins). Without the flag a re-deploy with `cleanDeploy` could boot the app with no environment variables — on its default port.\n\n### NEW-0713-8: failed galaxy app builds now carry a `buildHint`\n\n**Before**\n\nA galaxy app build failure returned only `GALAXY_APP_BUILD_FAILED`\n(and `GALAXY_APP_START_FAILED`) with a `buildLog` tail — you had to read the log\nby hand to find the cause. `GET \u002Fv1\u002Finfra\u002Fservers\u002F:id` for an ERROR app returned a\nshort `provisionError` but no ready recommendation.\n\n**After**\n\nThe response now carries the parsed cause. The error body of\n`POST \u002Fv1\u002Finfra\u002Fservers\u002F:id\u002Fdeploy` (502) additionally includes `error.category`\n(a machine category such as `MODULE_NOT_FOUND`, `INSTALL_AUTH`, `RESOURCE`) and\n`error.buildHint` — a localized recommendation line naming the concrete next step,\nwhenever the failure is classifiable. `GET \u002Fv1\u002Finfra\u002Fservers\u002F:id` for an ERROR app\nadds the same `data.buildHint` field. The fields are additive: when the cause is\nunrecognized they are absent (`buildHint` is `null`), and `provisionError`\u002F`buildLog`\nkeep arriving as before — existing requests are unaffected.\n\n### FIX-0713-9: concurrent identical source saves no longer mint a duplicate version\n\n**Before**\n\nTwo simultaneous saves of identical bytes to the same server (`POST \u002Fv1\u002Finfra\u002Fservers\u002F:id\u002Fsources`, and the auto-save on deploy) could, under rare timing, create **two** byte-identical versions instead of one — content deduplication was best-effort.\n\n**After**\n\nDeduplication is deterministic: identical bytes submitted concurrently always converge on a single version. On `POST \u002Fv1\u002Finfra\u002Fservers\u002F:id\u002Fsources` both responses return the same `versionId` and the losing request gets `deduplicated: true`; the deploy auto-save converges on that same single version (the deploy response shape is unchanged).\n",null,{},1794739470673]