[{"data":1,"prerenderedAt":8},["ShallowReactive",2],{"docs-entities\u002Fbooking-client-types":3,"docs-tabs-entities\u002Fbooking-client-types":6},{"content":4,"lastmod":5},"# Booking client types\n\nA booking client type is a module and code pair that defines which CRM record can be a client of a booking or of a wait list record: a contact or a company. Use this reference to pass only allowed pairs in booking clients.\n\nBitrix24 API: `booking.v1.clientType.list`\nScope: `booking`\n\n## Operations\n\n- [List booking client types](.\u002Fbooking-client-types\u002Flist.md) — `GET \u002Fv1\u002Fbooking-client-types`\n\n## Key fields\n\n| Field | Description |\n|------|----------|\n| `module` | Module the client type belongs to, for example `crm` |\n| `code` | Client type code, for example `CONTACT` — contact, `COMPANY` — company |\n\n## Before you start\n\n1. **The reference is read-only.** Client types are defined by the Bitrix24 account. They cannot be created, changed or deleted through the API, so the only operation is the list.\n2. **Pass the pair as a whole.** For the clients of a booking or a wait list record, the client type is set with the `type.module` and `type.code` fields. A pair that is not in the reference is rejected with `400 INVALID_PARAMS` before anything is written.\n3. **Reading works with a read-only key.** The reference changes nothing in the Bitrix24 account.\n\n## Typical scenario\n\n1. Get the allowed pairs: [`GET \u002Fv1\u002Fbooking-client-types`](.\u002Fbooking-client-types\u002Flist.md).\n2. Find a contact or a company for the booking: [`GET \u002Fv1\u002Fcontacts`](\u002Fdocs\u002Fentities\u002Fcontacts\u002Flist) or [`GET \u002Fv1\u002Fcompanies`](\u002Fdocs\u002Fentities\u002Fcompanies\u002Flist).\n3. Set the booking clients with a type from the reference: [`PUT \u002Fv1\u002Fbookings\u002F:id\u002Fclients`](\u002Fdocs\u002Fentities\u002Fbookings\u002Fclients-set).\n\n## Limits\n\n| Limit | Value |\n|-------|----------|\n| Pagination | none, the whole list arrives in one response |\n| General API limit | see [Limits and optimization](\u002Fdocs\u002Foptimization) |\n\n## See also\n\n- [Booking clients](\u002Fdocs\u002Fentities\u002Fbookings\u002Fclients)\n- [Booking wait list](\u002Fdocs\u002Fentities\u002Fbooking-wait-list)\n- [Bookings](\u002Fdocs\u002Fentities\u002Fbookings)\n","2026-10-28",{"booking-client-types\u002Flist.md":7},"# List booking client types\n\n`GET \u002Fv1\u002Fbooking-client-types`\n\nReturns the module and code pairs that the Bitrix24 account accepts as a client type in bookings and in the wait list.\n\nNo parameters. The whole list arrives in one response.\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X GET \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fbooking-client-types\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\"\n```\n\n### curl — OAuth application\n\n```bash\ncurl -X GET \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fbooking-client-types\" \\\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\u002Fbooking-client-types', {\n  headers: { 'X-Api-Key': 'YOUR_API_KEY' },\n})\n\nconst { data } = await res.json()\nconsole.log(data.map((type) => `${type.module}\u002F${type.code}`))\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fbooking-client-types', {\n  headers: {\n    'X-Api-Key': 'YOUR_APP_KEY',\n    'Authorization': 'Bearer USER_SESSION_TOKEN',\n  },\n})\n\nconst { data } = await res.json()\nconsole.log(data.map((type) => `${type.module}\u002F${type.code}`))\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|----------|\n| `success` | boolean | `true` on success |\n| `data` | array | Client types allowed in the Bitrix24 account. An empty array is a valid response |\n| `data[].module` | string | Module the client type belongs to, for example `crm` |\n| `data[].code` | string | Client type code, for example `CONTACT` or `COMPANY` |\n\n## Response example\n\n```json\n{\n  \"success\": true,\n  \"data\": [\n    {\n      \"code\": \"COMPANY\",\n      \"module\": \"crm\"\n    },\n    {\n      \"code\": \"CONTACT\",\n      \"module\": \"crm\"\n    }\n  ]\n}\n```\n\n## Error response example\n\n401 — no key passed:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"MISSING_API_KEY\",\n    \"message\": \"API key required. Pass via X-Api-Key header.\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 401 | `MISSING_API_KEY` | `X-Api-Key` was not passed |\n| 401 | `TOKEN_MISSING` | The key has no connection to Bitrix24 |\n| 403 | `SCOPE_DENIED` | The key lacks the `booking` scope |\n| 422 | `BITRIX_ERROR` | Bitrix24 rejected the request. The reason is in `message` |\n| 429 | `RATE_LIMITED` | Request rate exceeded |\n| 502 | `BITRIX_RESPONSE_INVALID` | Bitrix24 returned a list of an unexpected shape |\n| 502 | `BITRIX_UNAVAILABLE` | Bitrix24 is unavailable |\n| 503 | `BITRIX_TIMEOUT` | Bitrix24 did not respond in time |\n\nFull list of common API errors — [Errors](\u002Fdocs\u002Ferrors).\n\n## Known specifics\n\n**Query parameters do not change the response.** `filter`, `limit` and other query string parameters are ignored without a warning: the response always contains every client type of the Bitrix24 account.\n\n## See also\n\n- [Booking client types](\u002Fdocs\u002Fentities\u002Fbooking-client-types)\n- [Booking clients](\u002Fdocs\u002Fentities\u002Fbookings\u002Fclients)\n- [Booking wait list](\u002Fdocs\u002Fentities\u002Fbooking-wait-list)\n- [Errors](\u002Fdocs\u002Ferrors)\n",1795000270776]