[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-changelog\u002F2026-07-24":3,"docs-tabs-changelog\u002F2026-07-24":6},{"content":4,"lastmod":5},"# API changes: July 24, 2026\n\n[← Changelog](\u002Fdocs\u002Fchangelog) · [July 2026](\u002Fdocs\u002Fchangelog\u002F2026-07)\n\n### FIX-0724-1: activities: an unrecognized filter field name is now rejected with 400 UNKNOWN_FILTER_FIELD\n\n**Before**\n\n`GET \u002Fv1\u002Factivities` and `POST \u002Fv1\u002Factivities\u002Fsearch` silently dropped an unknown filter key: the request returned `200 success` with the filter trimmed to empty — that is, it returned the whole (owner-scoped or entire) activity set. For example `{\"filter\":{\"ownerTypeId\":2,\"ownerId\":3,\"bogusField\":123}}` ignored `bogusField` and returned every activity of the parent deal. This diverged from the documentation and from other CRM entities (companies, invoices), where such a filter was already rejected.\n\n**After**\n\nA filter field name that is not in the activity schema — and is not a `UF_*` custom field, the `id` key, or a special token — is now rejected before the Bitrix24 call with `400 UNKNOWN_FILTER_FIELD` and a list of available fields, the same as companies\u002Fquotes\u002Fcontacts already do. The full list of filterable fields is returned by `GET \u002Fv1\u002Factivities\u002Ffields`.\n\n**Impact on integrators**\n\nFiltering by real activity fields (in camelCase or the native Bitrix24 UPPER case), by `UF_*` fields, operators (`>=`, `\u003C`, `!`, etc.), ranges, and AND\u002FNOT all work as before. If you relied on the silent drop of an unrecognized key, remove it from the filter.\n\n### NEW-0724-2: bizproc activities and robots \u002Ffields now return field labels and descriptions\n\n**Before**\n\n`GET \u002Fv1\u002Fbizproc-activities\u002Ffields` and `GET \u002Fv1\u002Fbizproc-robots\u002Ffields` described each field only by its type and the readonly flag, with no human-readable labels.\n\n**After**\n\nEach of the 12 fields now carries a `label` and a `description` in English, which makes building forms and hints easier. Field types are unchanged.\n\n### FIX-0724-3: Downloading your own storage objects no longer returns 403\n\n**Before**\n\n`GET \u002Fv1\u002Fstorage\u002Fobjects\u002F:key` could return `403` for an object the key owner legitimately owns but that physically lives under a different storage \"family\" prefix (for example, server files visible in a developer's listing). The object appeared in the listing, yet downloading it, minting a presigned URL or issuing a `HEAD` failed.\n\n**After**\n\nThe scoped credentials account for the object's actual family (the Bitrix24 account stays bound to the caller's context), so download (`?download`), streaming (`?inline`) and `HEAD` work for your own objects regardless of family. Ownership checks are unchanged — someone else's object still returns `404`.\n\n### FIX-0724-4: GET \u002Fv1\u002Fworkflows honours the limit parameter\n\n**Before**\n\n`GET \u002Fv1\u002Fworkflows` accepted `limit` but silently ignored it — the whole page of running workflows (up to 50) was always returned regardless of the requested size.\n\n**After**\n\n`limit` is respected: the response holds at most the requested number of records. Values above 50 are gathered page by page (capped at 500); `meta.total` still reports the total number of running workflows.\n\n### FIX-0724-5: deploy: an app wrapped in a single archive folder no longer fails with ENOENT package.json\n\n**Before**\n\nDeploying (`POST \u002Fv1\u002Finfra\u002Fservers\u002F:id\u002Fdeploy`) to a standalone server an archive that wraps the project in a single top-level folder (e.g. `myapp\u002Fpackage.json` instead of `package.json` at the root) failed at the install step:\n\n```\nnpm error enoent Could not read package.json ... open '\u002Fopt\u002Fapp\u002Fpackage.json'\n```\n\nThe uploaded archive was left beside the extracted content, so the auto-flatten of a single wrapping directory did not fire (the root held two entries — the archive and the folder) and `package.json` stayed nested.\n\n**After**\n\nThe uploaded archive is removed before the flatten step, so a single wrapping directory collapses, `package.json` lands at the deploy root, and the install proceeds normally.\n\n**Impact**\n\nNo client action required. Flat archives (files at the archive root) work as before; to be safe you can package flat: `tar -czf build.tar.gz -C \u003Cproject_dir> .`.\n\n### FIX-0724-6: \u002Fv1\u002Fusers* endpoints no longer return 403 and 500 on keys with user access\n\n**Before**\n\nOn a read-only (READONLY) key with `user` access, `GET \u002Fv1\u002Fusers\u002Fme` returned `403 WRITE_BLOCKED_READONLY_KEY` even though it is a read endpoint. Separately, `GET \u002Fv1\u002Fusers`, `GET \u002Fv1\u002Fusers\u002F:id`, `POST \u002Fv1\u002Fusers\u002Fsearch` and `GET \u002Fv1\u002Fusers\u002Ffields` returned `500 INTERNAL_ERROR` on accounts where one of the user fields (`UF_*`) had an empty definition.\n\n**After**\n\n`GET \u002Fv1\u002Fusers\u002Fme` works on a read-only key. The other `\u002Fv1\u002Fusers*` endpoints return data and skip the field with an empty definition instead of failing.\n\n**Impact on integrators**\n\nNo action required — existing calls keep working, and the previously failing scenarios now respond correctly.\n\n### NEW-0724-7: bizproc activity and robot callback delivery to a Black Hole app\n\nRegistering a bizproc activity or robot whose `handler` points at your Black Hole deploy server now reliably delivers the execution callback (event token, auth block, code and properties) to the app. Previously that callback could be lost: Bitrix24 online events are not retried, and a sleeping or waking server dropped the call. The platform intercepts the `handler` at registration, queues the call durably, and retries delivery with a server wake-up and backoff.\n\nAffects [POST \u002Fv1\u002Fbizproc-activities](\u002Fdocs\u002Fentities\u002Fbizproc-activities) and [POST \u002Fv1\u002Fbizproc-robots](\u002Fdocs\u002Fentities\u002Fbizproc-robots) (and their update). New error code `SERVER_APP_MISMATCH` (400): the Black Hole server behind the given `handler` must belong to the same app that registers the activity. Registering such a `handler` through `\u002Fv1\u002Fbatch` is not supported — use a single request (`BIZPROC_CALLBACK_BATCH_UNSUPPORTED`). Additionally, `POST \u002Fv1\u002Fbizproc-robots` now requires `code`, `name` and `handler` upfront — omitting any returns `400 MISSING_REQUIRED_FIELDS` instead of a raw Bitrix24 error (as activities already did).\n\nThe capability is rolling out gradually and is enabled per account: until it is on for your account, registration behaves as before, without managed delivery. **Once it is on, batch registration behaviour changes:** an attempt to register a BH `handler` via `\u002Fv1\u002Fbatch` starts being rejected (`BIZPROC_CALLBACK_BATCH_UNSUPPORTED`) — move such registrations to a single `POST \u002Fv1\u002Fbizproc-activities` or `\u002Fv1\u002Fbizproc-robots`.\n",null,{},1794739472097]