[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-entities\u002Fbizproc-activities\u002Flist":3,"docs-tabs-entities\u002Fbizproc-activities\u002Flist":6},{"content":4,"lastmod":5},"\n## Activity list\n\n`GET \u002Fv1\u002Fbizproc-activities`\n\nReturns the list of business process activity codes registered on the Bitrix24 account. Each response element is a string activity code used in the update and delete paths.\n\nThe method works only with an authorization key.\n\n## Parameters\n\n| Parameter | Type | Default | Description |\n|----------|-----|-----------|---------|\n| `limit` | number | `50` | Maximum number of codes in the response |\n| `offset` | number | `0` | Number of codes to skip from the beginning of the full list |\n| `select` | string | — | Accepted, but does not change the response: the `data` items are code strings |\n| `withTotal` | boolean | — | Accepted, but does not change the response: `meta.total` is returned for any value of the parameter |\n\nSorting is not supported: `sort` and `order` return `400 INVALID_SORT_FIELD`. Filtering is not supported either: `filter` returns `400 UNSUPPORTED_FILTER`.\n\n## Examples\n\nThe session token is issued by OAuth authorization, is valid for 24 hours, and cannot be renewed — [Passing the key](\u002Fdocs\u002Fkeys-auth#passing-the-key).\n\n### curl — OAuth application\n\n```bash\ncurl \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fbizproc-activities\" \\\n  -H \"X-Api-Key: YOUR_APP_KEY\" \\\n  -H \"Authorization: Bearer USER_SESSION_TOKEN\"\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fbizproc-activities', {\n  headers: {\n    'X-Api-Key': 'YOUR_APP_KEY',\n    'Authorization': 'Bearer USER_SESSION_TOKEN',\n  },\n})\n\nconst { success, data, meta } = await res.json()\nconsole.log(`Registered activities: ${meta.total}`)\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|---------|\n| `success` | boolean | Always `true` on success |\n| `data` | array | Array of strings — the codes of registered activities |\n| `meta.total` | number | Number of codes in the full list, not the current page |\n| `meta.hasMore` | boolean | Whether more codes remain after the current page |\n\n## Response example\n\n```json\n{\n  \"success\": true,\n  \"data\": [\n    \"notify_manager\",\n    \"sync_status\"\n  ],\n  \"meta\": {\n    \"total\": 2,\n    \"hasMore\": false\n  }\n}\n```\n\n## Error response example\n\n403 — the request was sent with an API key on a method that requires an authorization key:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"OAUTH_REQUIRED\",\n    \"message\": \"bizproc-activities require an OAuth app key (vibe_app_*) with an Authorization: Bearer session — a personal vibe_api_* key lacks the per-user OAuth context Bitrix24 needs for these methods. Create an OAuth app (POST \u002Fv1\u002Fapps) and retry with its key. On this 403 switch keys — do NOT delete or recreate the app (that discards anything already registered under it, e.g. a bizproc robot you just registered).\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|---------|\n| 400 | `INVALID_SORT_FIELD` | `sort` or `order` was supplied; the list method does not support sorting |\n| 400 | `UNSUPPORTED_FILTER` | `filter` was supplied. The list method does not filter — filter the codes on the client side |\n| 403 | `OAUTH_REQUIRED` | Called with an API key. The method is available only to an authorization key |\n| 401 | `TOKEN_MISSING` | The authorization key was sent without the `Authorization: Bearer \u003Csession>` header |\n| 401 | `WRONG_AUTH_SCHEME` | The authorization key was sent in the `Authorization: Bearer` header. The key goes in `X-Api-Key`, while `Authorization: Bearer` carries the session token |\n| 401 | `INVALID_SESSION` | The session token has expired or is invalid — authorize again |\n| 403 | `SCOPE_DENIED` | The key lacks the `bizproc` scope |\n| 409 | `BIZPROC_MODULE_NOT_ENABLED` | Business Processes are not available on the account: the module is not included in the plan, or it is switched off in account settings. Ask an account administrator to enable Business Processes — until then, the method returns the same response regardless of how many times you retry |\n| 429 | `RATE_LIMITED` | Rate limit exceeded: 300 requests per minute per portal. All API keys of the portal share one limit. The current limit is returned in the `x-ratelimit-limit` header. Retry after the delay in the `Retry-After` header |\n\nFor the full list of common API errors, see [Errors](\u002Fdocs\u002Ferrors).\n\n## Known specifics\n\n**An empty list is a successful response.** Until at least one activity is registered on the Bitrix24 account, `data` comes back as an empty array with code `200`. The absence of activities is not an error.\n\n## See also\n\n- [Register an activity](\u002Fdocs\u002Fentities\u002Fbizproc-activities\u002Fcreate)\n- [Keys and authorization](\u002Fdocs\u002Fkeys-auth)\n- [Errors](\u002Fdocs\u002Ferrors)\n","2026-10-23",{},1794739312785]