[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-entities\u002Fpay-systems\u002Fhandlers":3,"docs-tabs-entities\u002Fpay-systems\u002Fhandlers":6},{"content":4,"lastmod":5},"## List pay system handlers\n\n`GET \u002Fv1\u002Fpay-systems\u002Fhandlers`\n\nChoose a registered REST handler when creating a pay system in your Bitrix24 account.\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fpay-systems\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\u002Fpay-systems\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 response = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fpay-systems\u002Fhandlers', {\n  headers: {\n    'X-Api-Key': 'YOUR_API_KEY',\n  },\n})\n\nconst { success, data, meta } = await response.json()\nconsole.log(data)\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst response = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fpay-systems\u002Fhandlers', {\n  headers: {\n    'X-Api-Key': 'YOUR_APP_KEY',\n    'Authorization': 'Bearer USER_SESSION_TOKEN',\n  },\n})\n\nconst { success, data, meta } = await response.json()\nconsole.log(data)\n```\n\n## Response fields\n\n| Field | Type | Required | Description |\n|---|---|---|---|\n| `success` | boolean | yes | `true` for a successful request |\n| `data` | array | yes | List of registered REST handlers for pay systems |\n| `data[].id` | integer | no | Handler ID |\n| `data[].name` | string | no | Handler name |\n| `data[].code` | string | no | Handler code |\n| `data[].sort` | integer | no | Handler sort value |\n| `data[].description` | string | no | Handler description |\n| `data[].settings` | object \u002F array | no | Handler settings definition. The structure and nested keys depend on the handler |\n| `data[].profiles` | array | no | Handler profile definitions |\n| `meta` | object | yes | List metadata |\n| `meta.total` | integer | yes | Number of handlers in `data` |\n\nHandler fields are included in the response if they are present in the handler definition. An empty `data` array means there are no registered REST handlers.\n\n## Response example\n\nThe example shows the main handler fields. See the [response fields table](#response-fields) for the full structure.\n\n```json\n{\n  \"success\": true,\n  \"data\": [\n    {\n      \"id\": 1,\n      \"code\": \"my_payment_handler\",\n      \"sort\": 100\n    },\n    {\n      \"id\": 3,\n      \"code\": \"my_qr_handler\",\n      \"sort\": 100\n    }\n  ],\n  \"meta\": {\n    \"total\": 2\n  }\n}\n```\n\n## Error response example\n\n400 — the request includes the query parameter `limit=1`:\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` | The request includes query parameters. This method accepts none |\n| 403 | `BITRIX_ACCESS_DENIED` | Bitrix24 denied access to the handlers |\n| 422 | `BITRIX_ERROR` | The operation failed in Bitrix24. See `error.message` for details |\n| 502 | `BITRIX_RESPONSE_INVALID` | The response has an invalid structure |\n| 401 | `TOKEN_MISSING` | The key has no configured Bitrix24 access tokens |\n| 403 | `SCOPE_DENIED` | The key lacks the `pay_system` scope |\n\nFor the full list of common API errors, see [Errors](\u002Fdocs\u002Ferrors).\n\n## See also\n\n- [Pay systems](\u002Fdocs\u002Fentities\u002Fpay-systems)\n- [Errors](\u002Fdocs\u002Ferrors)\n","2026-10-14",{},1795000361392]