[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-entities\u002Fdelivery-services\u002Fhandlers":3,"docs-tabs-entities\u002Fdelivery-services\u002Fhandlers":6},{"content":4,"lastmod":5},"## List delivery handlers\n\n`GET \u002Fv1\u002Fdelivery-services\u002Fhandlers`\n\nLists registered REST delivery handlers so you can choose a handler before creating a delivery service.\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fdelivery-services\u002Fhandlers\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\"\n```\n\n### curl — OAuth application\n\n```bash\ncurl \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fdelivery-services\u002Fhandlers\" \\\n  -H \"X-Api-Key: YOUR_APP_KEY\" \\\n  -H \"Authorization: Bearer USER_SESSION_TOKEN\"\n```\n\n### JavaScript — personal key\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fdelivery-services\u002Fhandlers', {\n  headers: {\n    'X-Api-Key': 'YOUR_API_KEY',\n  },\n})\n\nconst { success, data, meta } = await res.json()\nconsole.log(data, meta.total)\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fdelivery-services\u002Fhandlers', {\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(data, meta.total)\n```\n\n## Response fields\n\n| Field | Type | Required | Description |\n|-------|------|:--------:|-------------|\n| `success` | boolean | yes | `true` on a successful request |\n| `data` | array | yes | Array of registered handlers. Empty if no handlers are registered |\n| `data[].id` | integer | no | Handler ID |\n| `data[].name` | string | no | Handler name |\n| `data[].code` | string | no | Handler code. Pass it as `restCode` when [creating a delivery service](\u002Fdocs\u002Fentities\u002Fdelivery-services\u002Fcreate) |\n| `data[].sort` | integer | no | Handler sort order |\n| `data[].description` | string | no | Handler description |\n| `data[].settings` | object \\| array | no | Handler settings. Nested keys retain their Bitrix24 names |\n| `data[].profiles` | array | no | Handler profile definitions. Nested keys retain their Bitrix24 names |\n| `meta` | object | yes | Handler count metadata |\n| `meta.total` | integer | yes | Number of items in `data` |\n\n## Response example\n\nThe example shows the main handler fields. The full structure is listed in the Response fields table above.\n\n```json\n{\n  \"success\": true,\n  \"data\": [\n    {\n      \"id\": 1,\n      \"name\": \"Delivery handler\",\n      \"code\": \"my_delivery_handler\",\n      \"sort\": 250\n    }\n  ],\n  \"meta\": {\n    \"total\": 1\n  }\n}\n```\n\n## Error response example\n\n400 — query parameters are present in the URL:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"INVALID_PARAMS\",\n    \"message\": \"Handlers have no query parameters\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|------|-------------|\n| 400 | `INVALID_PARAMS` | Any query parameter is present in the URL. Call this method without query parameters |\n| 502 | `BITRIX_RESPONSE_INVALID` | The response structure or a numeric field value is invalid |\n| 401 | `MISSING_API_KEY` | The `X-Api-Key` header is missing |\n| 401 | `TOKEN_MISSING` | The key has no available Bitrix24 tokens |\n| 403 | `SCOPE_DENIED` | The key lacks the `delivery` scope |\n| 403 | `BITRIX_ACCESS_DENIED` | Bitrix24 denied access |\n| 422 | `BITRIX_ERROR` | Bitrix24 rejected the request. The reason is in `error.message` |\n\nFor all common API errors, see [Errors](\u002Fdocs\u002Ferrors).\n\n## See also\n\n- [Create a delivery service](\u002Fdocs\u002Fentities\u002Fdelivery-services\u002Fcreate)\n- [Delivery services](\u002Fdocs\u002Fentities\u002Fdelivery-services)\n","2026-10-14",{},1795000330412]