[{"data":1,"prerenderedAt":12},["ShallowReactive",2],{"docs-entities\u002Fbooking-resource-types":3,"docs-tabs-entities\u002Fbooking-resource-types":6},{"content":4,"lastmod":5},"# Booking resource types\n\nA booking resource type is a category of online booking resources, such as specialists, equipment or rooms. The type stores the settings for client messages about bookings: which messages to send, when, and with which template.\n\nBitrix24 API: `booking.v1.resourceType.*`\nScope: `booking`\n\n## Operations\n\n- [Create a resource type](.\u002Fbooking-resource-types\u002Fcreate.md) — `POST \u002Fv1\u002Fbooking-resource-types`\n- [List resource types](.\u002Fbooking-resource-types\u002Flist.md) — `GET \u002Fv1\u002Fbooking-resource-types`\n- [Get a resource type](.\u002Fbooking-resource-types\u002Fget.md) — `GET \u002Fv1\u002Fbooking-resource-types\u002F:id`\n- [Update a resource type](.\u002Fbooking-resource-types\u002Fupdate.md) — `PATCH \u002Fv1\u002Fbooking-resource-types\u002F:id`\n- [Delete a resource type](.\u002Fbooking-resource-types\u002Fdelete.md) — `DELETE \u002Fv1\u002Fbooking-resource-types\u002F:id`\n\n## Key fields\n\n| Field | Description |\n|------|----------|\n| `id` | Type identifier. List: [`GET \u002Fv1\u002Fbooking-resource-types`](.\u002Fbooking-resource-types\u002Flist.md). Pass it in `typeId` when [creating a booking resource](\u002Fdocs\u002Fentities\u002Fbooking-resources\u002Fcreate) |\n| `code` | Symbolic code, unique among the types of the Bitrix24 account. Required on create and in every update |\n| `name` | Type name. Required on create |\n| `is*NotificationOn` | Six switches for client messages: booking info, confirmation request, reminder, feedback request, late-arrival message, cancellation message |\n| `senderCode` | Service that sends messages to the client, for example `bitrix24` |\n\nFor the full field list, see [Get a resource type](.\u002Fbooking-resource-types\u002Fget.md).\n\n## What to know before you start\n\n1. **Client messages are on by default.** A type created without the `is*NotificationOn` switches gets all six set to `true`. To turn client messages off, pass all six set to `false` on create.\n2. **The request body is flat.** Fields go at the root of the JSON, without a `fields` wrapper. The switches accept `true` \u002F `false` or the strings `\"Y\"` \u002F `\"N\"`; the response always returns `true` or `false`.\n3. **An update requires a new `code`.** A `PATCH` without `code` or with the current code is rejected with `422 BITRIX_ERROR`. To keep the code, change fields in two requests: first with a temporary `code`, then with the original one.\n4. **A type that has ever had a resource cannot be deleted.** The API still returns `422 BITRIX_ERROR` even after all resources of this type are deleted.\n5. **The full list is returned.** The list has no pagination: all resource types in the Bitrix24 account, up to 500, are returned in a single response. A filter by `id` does not narrow the list — for a single type, use [get by `id`](.\u002Fbooking-resource-types\u002Fget.md).\n\n## Typical scenario\n\n1. Find a suitable type: [`GET \u002Fv1\u002Fbooking-resource-types`](.\u002Fbooking-resource-types\u002Flist.md). The Bitrix24 account already has built-in types, for example `equipment` and `room`.\n2. If none fits, create your own: [`POST \u002Fv1\u002Fbooking-resource-types`](.\u002Fbooking-resource-types\u002Fcreate.md).\n3. Create a resource of this type, passing the type `id` in `typeId`: [`POST \u002Fv1\u002Fbooking-resources`](\u002Fdocs\u002Fentities\u002Fbooking-resources\u002Fcreate).\n4. Set the resource's working hours: [`PUT \u002Fv1\u002Fbooking-resources\u002F:id\u002Fslots`](\u002Fdocs\u002Fentities\u002Fbooking-resources\u002Fslots).\n5. Book clients: [`POST \u002Fv1\u002Fbookings`](\u002Fdocs\u002Fentities\u002Fbookings\u002Fcreate).\n\n## Limits\n\n| Limit | Value |\n|-------|----------|\n| Types in a list response | up to 500. If the Bitrix24 account has more, the list responds with `502 BITRIX_RESPONSE_INVALID` |\n| Pagination | none, `limit` and `offset` are not accepted |\n| Request rate | list — up to 20 requests per minute per Bitrix24 account, other operations — up to 60. The current limit for the key is returned in the `x-ratelimit-limit` header |\n| General API limit | see [Limits and optimization](\u002Fdocs\u002Foptimization) |\n\n## See also\n\n- [Booking resources](\u002Fdocs\u002Fentities\u002Fbooking-resources)\n- [Bookings](\u002Fdocs\u002Fentities\u002Fbookings)\n- [Errors](\u002Fdocs\u002Ferrors)\n","2026-10-23",{"booking-resource-types\u002Fcreate.md":7,"booking-resource-types\u002Flist.md":8,"booking-resource-types\u002Fget.md":9,"booking-resource-types\u002Fupdate.md":10,"booking-resource-types\u002Fdelete.md":11},"# Create: Booking resource types\n\n`POST \u002Fv1\u002Fbooking-resource-types`\n\nCreates a booking resource type — a category of online booking resources with the settings for client messages about bookings.\n\nFields go at the root of the JSON, without a `fields` wrapper.\n\n## Request fields (body)\n\n| Field | Type | Required | Description |\n|------|-----|:-----:|----------|\n| `code` | string | yes | Symbolic code of the type. Unique among the types of the Bitrix24 account: a duplicate code is rejected with `422 BITRIX_ERROR` |\n| `name` | string | yes | Type name |\n| `isInfoNotificationOn` | boolean \\| string | no | Booking info message to the client. `true` \u002F `false` or `\"Y\"` \u002F `\"N\"`. Default `true` |\n| `isConfirmationNotificationOn` | boolean \\| string | no | Booking confirmation request. Default `true` |\n| `isReminderNotificationOn` | boolean \\| string | no | Booking reminder. Default `true` |\n| `isFeedbackNotificationOn` | boolean \\| string | no | Feedback request. Default `true` |\n| `isDelayedNotificationOn` | boolean \\| string | no | Message to a client who is running late. Default `true` |\n| `isCancellationNotificationOn` | boolean \\| string | no | Booking cancellation message to the client. Default `true` |\n| `senderCode` | string \\| null | no | Service that sends messages to the client, for example `bitrix24`. Default `null` |\n| `infoNotificationDelay` | number \\| null | no | How many seconds after the booking is made to send the booking info message. Default `null` |\n| `confirmationNotificationDelay` | number \\| null | no | How many seconds before the booking to send the first confirmation request. Default `86400` |\n| `confirmationNotificationRepetitions` | number \\| null | no | How many times to repeat the confirmation request, not counting the first one. Default `null` |\n| `confirmationNotificationRepetitionsInterval` | number \\| null | no | Interval between repeats of the confirmation request, in seconds. Default `10800` |\n| `confirmationCounterDelay` | number \\| null | no | How many seconds before the booking an unconfirmed booking enters the counter. Default `10800` |\n| `reminderNotificationDelay` | number \\| null | no | How many seconds before the booking to send the reminder. `-1` — on the morning of the booking day. Default `-1` |\n| `delayedNotificationDelay` | number \\| null | no | After how many seconds of lateness to send the message to the client. Default `300` |\n| `delayedCounterDelay` | number \\| null | no | After how many seconds of lateness the booking enters the calendar counter. Default `300` |\n| `cancellationNotificationDelay` | number \\| null | no | Delay of the booking cancellation message, in seconds. Default `600` |\n| `templateTypeInfo` | string | no | Booking message template: `inanimate`, `animate`, `inanimate_long`. Default `inanimate`. Saved, but not returned in the type card |\n| `templateTypeConfirmation` | string | no | Confirmation request template: `inanimate`, `animate`, `inanimate_long`. Default `inanimate` |\n| `templateTypeReminder` | string | no | Reminder template. The only value is `base` |\n| `templateTypeFeedback` | string | no | Feedback request template: `inanimate`, `animate`. Default `inanimate` |\n| `templateTypeDelayed` | string | no | Late-arrival message template: `inanimate`, `animate`. Default `inanimate` |\n\nThe built-in \"Expert\" type uses the `animate` templates; the \"Equipment\", \"Car\" and \"Property\" types use `inanimate`.\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X POST \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fbooking-resource-types\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"name\": \"Technicians\",\n    \"code\": \"master\",\n    \"isInfoNotificationOn\": false,\n    \"isConfirmationNotificationOn\": false,\n    \"isReminderNotificationOn\": false,\n    \"isFeedbackNotificationOn\": false,\n    \"isDelayedNotificationOn\": false,\n    \"isCancellationNotificationOn\": false\n  }'\n```\n\n### curl — OAuth application\n\n```bash\ncurl -X POST \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fbooking-resource-types\" \\\n  -H \"X-Api-Key: YOUR_APP_KEY\" \\\n  -H \"Authorization: Bearer USER_SESSION_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"name\": \"Technicians\",\n    \"code\": \"master\",\n    \"isInfoNotificationOn\": false,\n    \"isConfirmationNotificationOn\": false,\n    \"isReminderNotificationOn\": false,\n    \"isFeedbackNotificationOn\": false,\n    \"isDelayedNotificationOn\": false,\n    \"isCancellationNotificationOn\": false\n  }'\n```\n\n### JavaScript — personal key\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fbooking-resource-types', {\n  method: 'POST',\n  headers: {\n    'X-Api-Key': 'YOUR_API_KEY',\n    'Content-Type': 'application\u002Fjson',\n  },\n  body: JSON.stringify({\n    name: 'Technicians',\n    code: 'master',\n    isInfoNotificationOn: false,\n    isConfirmationNotificationOn: false,\n    isReminderNotificationOn: false,\n    isFeedbackNotificationOn: false,\n    isDelayedNotificationOn: false,\n    isCancellationNotificationOn: false,\n  }),\n})\n\nconst { data } = await res.json()\nconsole.log('Type ID:', data.id)\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fbooking-resource-types', {\n  method: 'POST',\n  headers: {\n    'X-Api-Key': 'YOUR_APP_KEY',\n    'Authorization': 'Bearer USER_SESSION_TOKEN',\n    'Content-Type': 'application\u002Fjson',\n  },\n  body: JSON.stringify({\n    name: 'Technicians',\n    code: 'master',\n    isInfoNotificationOn: false,\n    isConfirmationNotificationOn: false,\n    isReminderNotificationOn: false,\n    isFeedbackNotificationOn: false,\n    isDelayedNotificationOn: false,\n    isCancellationNotificationOn: false,\n  }),\n})\n\nconst { data } = await res.json()\nconsole.log('Type ID:', data.id)\n```\n\n## Response fields\n\nOn success, the HTTP status is `201 Created`.\n\n| Field | Type | Description |\n|------|-----|----------|\n| `success` | boolean | `true` on success |\n| `data` | object | Card of the created type. The card fields are listed in the \"Response fields\" section of the [Get a booking resource type](\u002Fdocs\u002Fentities\u002Fbooking-resource-types\u002Fget) page |\n| `data.id` | number | Type identifier. Pass it in `typeId` when [creating a booking resource](\u002Fdocs\u002Fentities\u002Fbooking-resources\u002Fcreate) |\n\n## Response example\n\n```json\n{\n  \"success\": true,\n  \"data\": {\n    \"id\": 31,\n    \"code\": \"master\",\n    \"name\": \"Technicians\",\n    \"senderCode\": null,\n    \"isInfoNotificationOn\": false,\n    \"isConfirmationNotificationOn\": false,\n    \"isReminderNotificationOn\": false,\n    \"isFeedbackNotificationOn\": false,\n    \"isDelayedNotificationOn\": false,\n    \"isCancellationNotificationOn\": false,\n    \"infoNotificationDelay\": null,\n    \"confirmationNotificationDelay\": 86400,\n    \"confirmationNotificationRepetitions\": null,\n    \"confirmationNotificationRepetitionsInterval\": 10800,\n    \"confirmationCounterDelay\": 10800,\n    \"reminderNotificationDelay\": -1,\n    \"delayedNotificationDelay\": 300,\n    \"delayedCounterDelay\": 300,\n    \"cancellationNotificationDelay\": 600,\n    \"templateTypeConfirmation\": \"inanimate\",\n    \"templateTypeReminder\": \"base\",\n    \"templateTypeFeedback\": \"inanimate\",\n    \"templateTypeDelayed\": \"inanimate\"\n  }\n}\n```\n\n## Error response example\n\n422 — a type with this code already exists:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"BITRIX_ERROR\",\n    \"message\": \"Resource type with code \\\"master\\\" already exists\",\n    \"b24Code\": \"1010\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 400 | `MISSING_REQUIRED_FIELDS` | `code` is not passed. Message `code is required` |\n| 400 | `READONLY_FIELD` | `id` is passed in the body. Message `id is read-only` |\n| 400 | `INVALID_PARAMS` | Empty body. Message `Provide a non-empty object of fields` |\n| 400 | `INVALID_PARAMS` | A field not listed in the \"Request fields (body)\" table. Message `Unknown booking field` |\n| 400 | `INVALID_PARAMS` | A field value is an object or an array. Message `Fields must contain scalar values` |\n| 422 | `BITRIX_ERROR` | A type with this `code` already exists, `b24Code` `1010` |\n| 422 | `BITRIX_ERROR` | `name` is not passed. Message `Required fields: name` |\n| 401 | `MISSING_API_KEY` | The `X-Api-Key` header is not passed |\n| 401 | `TOKEN_MISSING` | The key has no Bitrix24 tokens |\n| 403 | `SCOPE_DENIED` | The key does not have the `booking` scope |\n| 403 | `WRITE_BLOCKED_READONLY_KEY` | The key is in read-only mode |\n| 429 | `RATE_LIMITED` | Request rate exceeded. The effective cap is in the `x-ratelimit-limit` header |\n| 502 | `BITRIX_RESPONSE_INVALID` | Bitrix24 returned a response of an unexpected shape. If this happened while re-reading the card after the write, the type has already been created — find it in the [list](\u002Fdocs\u002Fentities\u002Fbooking-resource-types\u002Flist) before retrying |\n\nFull list of common API errors — [Errors](\u002Fdocs\u002Ferrors).\n\n## See also\n\n- [List booking resource types](\u002Fdocs\u002Fentities\u002Fbooking-resource-types\u002Flist)\n- [Update a booking resource type](\u002Fdocs\u002Fentities\u002Fbooking-resource-types\u002Fupdate)\n- [Delete a booking resource type](\u002Fdocs\u002Fentities\u002Fbooking-resource-types\u002Fdelete)\n- [Create a booking resource](\u002Fdocs\u002Fentities\u002Fbooking-resources\u002Fcreate)\n- [Errors](\u002Fdocs\u002Ferrors)\n","# List: Booking resource types\n\n`GET \u002Fv1\u002Fbooking-resource-types`\n\nReturns all booking resource types of the Bitrix24 account in one response, with filtering by code or name, and sorting.\n\n## Parameters\n\n| Parameter | Type | Required | Default | Description |\n|----------|-----|:-----:|-----------|----------|\n| `filter` (query) | string | no | — | JSON filter object. Fields: `code` — a string or an array of strings, `name` — exact name, `searchQuery` — part of the name. Example: `?filter={\"code\":[\"equipment\",\"expert\"]}` |\n| `order` (query) | string | no | `{\"id\":\"ASC\"}` | JSON object for sorting by `id`, `name` or `code`, with values `ASC` or `DESC`. Example: `?order={\"name\":\"DESC\"}` |\n\n**Pagination.** There is no pagination: the list returns all matching types in one response, up to 500. The `limit` and `offset` parameters are not accepted — a request with them is rejected with `400 INVALID_PARAMS`. Pass `filter` and `order` URL-encoded, as in the examples.\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -G \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fbooking-resource-types\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\" \\\n  --data-urlencode 'filter={\"code\":[\"equipment\",\"expert\"]}'\n```\n\n### curl — OAuth application\n\n```bash\ncurl -G \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fbooking-resource-types\" \\\n  -H \"X-Api-Key: YOUR_APP_KEY\" \\\n  -H \"Authorization: Bearer USER_SESSION_TOKEN\" \\\n  --data-urlencode 'filter={\"code\":[\"equipment\",\"expert\"]}'\n```\n\n### JavaScript — personal key\n\n```javascript\nconst params = new URLSearchParams({\n  filter: JSON.stringify({ code: ['equipment', 'expert'] }),\n})\n\nconst res = await fetch(`https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fbooking-resource-types?${params}`, {\n  headers: { 'X-Api-Key': 'YOUR_API_KEY' },\n})\n\nconst { data, meta } = await res.json()\nconsole.log(meta.total, data.map((type) => type.code))\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst params = new URLSearchParams({\n  filter: JSON.stringify({ code: ['equipment', 'expert'] }),\n})\n\nconst res = await fetch(`https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fbooking-resource-types?${params}`, {\n  headers: {\n    'X-Api-Key': 'YOUR_APP_KEY',\n    'Authorization': 'Bearer USER_SESSION_TOKEN',\n  },\n})\n\nconst { data, meta } = await res.json()\nconsole.log(meta.total, data.map((type) => type.code))\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|----------|\n| `success` | boolean | `true` on success |\n| `data` | array | Array of type cards. The card fields are listed in the \"Response fields\" section of the [Get a booking resource type](\u002Fdocs\u002Fentities\u002Fbooking-resource-types\u002Fget) page |\n| `meta.total` | number | Number of types in the response |\n| `meta.hasMore` | boolean | Always `false`: the list arrives whole |\n\n## Response example\n\nThe main card fields are shown. The full set is on the [Get a booking resource type](\u002Fdocs\u002Fentities\u002Fbooking-resource-types\u002Fget) page.\n\n```json\n{\n  \"success\": true,\n  \"data\": [\n    {\n      \"id\": 3,\n      \"code\": \"equipment\",\n      \"name\": \"Equipment\",\n      \"senderCode\": null,\n      \"isInfoNotificationOn\": true,\n      \"isConfirmationNotificationOn\": true,\n      \"isReminderNotificationOn\": true,\n      \"isFeedbackNotificationOn\": false,\n      \"isDelayedNotificationOn\": true,\n      \"isCancellationNotificationOn\": true,\n      \"templateTypeConfirmation\": \"inanimate\"\n    },\n    {\n      \"id\": 5,\n      \"code\": \"expert\",\n      \"name\": \"Expert\",\n      \"senderCode\": null,\n      \"isInfoNotificationOn\": true,\n      \"isConfirmationNotificationOn\": true,\n      \"isReminderNotificationOn\": true,\n      \"isFeedbackNotificationOn\": false,\n      \"isDelayedNotificationOn\": true,\n      \"isCancellationNotificationOn\": true,\n      \"templateTypeConfirmation\": \"animate\"\n    }\n  ],\n  \"meta\": {\n    \"total\": 2,\n    \"hasMore\": false\n  }\n}\n```\n\n## Error response example\n\n400 — the filter field is not supported:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"INVALID_PARAMS\",\n    \"message\": \"Unknown resource type filter\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 400 | `INVALID_PARAMS` | A filter field is not one of the allowed fields. Message `Unknown resource type filter` |\n| 400 | `INVALID_PARAMS` | A filter field value is an object. Message `Filter values must be scalars or scalar arrays` |\n| 400 | `INVALID_PARAMS` | Sorting by a field other than `id`, `name` or `code`, or in a direction other than `ASC` \u002F `DESC`. Message `Invalid resource type order` |\n| 400 | `INVALID_PARAMS` | `filter` or `order` is not JSON. Message `filter and order must be JSON objects` |\n| 400 | `INVALID_PARAMS` | `filter` or `order` is JSON but not an object, for example an array. Message `filter and order must be objects` |\n| 400 | `INVALID_PARAMS` | A parameter other than `filter` and `order` is passed. Message `Only filter and order are supported` |\n| 400 | `INVALID_PARAMS` | A parameter is passed twice. Message `Repeated query parameters are not supported` |\n| 401 | `MISSING_API_KEY` | The `X-Api-Key` header is not passed |\n| 401 | `TOKEN_MISSING` | The key has no Bitrix24 tokens |\n| 403 | `SCOPE_DENIED` | The key does not have the `booking` scope |\n| 429 | `RATE_LIMITED` | Request rate exceeded. The effective cap is in the `x-ratelimit-limit` header |\n| 502 | `BITRIX_RESPONSE_INVALID` | The Bitrix24 account has more than 500 types, or Bitrix24 returned a list of an unexpected shape |\n\nFull list of common API errors — [Errors](\u002Fdocs\u002Ferrors).\n\n## Known specifics\n\n**A filter by `id` does not work.** The `id` field and uppercase field names, for example `CODE`, pass validation but do not filter records: the response contains all types of the Bitrix24 account. To get a single type by its identifier, call [`GET \u002Fv1\u002Fbooking-resource-types\u002F:id`](\u002Fdocs\u002Fentities\u002Fbooking-resource-types\u002Fget).\n\n**Built-in types.** Besides the types created through the API, the list contains types that Bitrix24 creates on its own, for example `equipment` — \"Equipment\" and `room` — \"Property\".\n\n## See also\n\n- [Get a booking resource type](\u002Fdocs\u002Fentities\u002Fbooking-resource-types\u002Fget)\n- [Create a booking resource type](\u002Fdocs\u002Fentities\u002Fbooking-resource-types\u002Fcreate)\n- [Booking resources](\u002Fdocs\u002Fentities\u002Fbooking-resources)\n- [Errors](\u002Fdocs\u002Ferrors)\n","# Get: Booking resource types\n\n`GET \u002Fv1\u002Fbooking-resource-types\u002F:id`\n\nReturns a booking resource type by its identifier: name, code and the settings for client messages about bookings.\n\n## Parameters\n\n| Parameter | Type | Required | Description |\n|----------|-----|:-----:|----------|\n| `id` (path) | number | yes | Type identifier. List: [`GET \u002Fv1\u002Fbooking-resource-types`](\u002Fdocs\u002Fentities\u002Fbooking-resource-types\u002Flist) |\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fbooking-resource-types\u002F31\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\"\n```\n\n### curl — OAuth application\n\n```bash\ncurl \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fbooking-resource-types\u002F31\" \\\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-resource-types\u002F31', {\n  headers: { 'X-Api-Key': 'YOUR_API_KEY' },\n})\n\nconst { data } = await res.json()\nconsole.log(data.name, data.code)\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fbooking-resource-types\u002F31', {\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.name, data.code)\n```\n\n## Response fields\n\nThe `is*NotificationOn` switches are always `true` or `false` in the response, even if the strings `\"Y\"` \u002F `\"N\"` were passed on write. Delays are in seconds.\n\n| Field | Type | Description |\n|------|-----|----------|\n| `success` | boolean | `true` on success |\n| `data.id` | number | Type identifier. Pass it in `typeId` when [creating a booking resource](\u002Fdocs\u002Fentities\u002Fbooking-resources\u002Fcreate) |\n| `data.code` | string | Symbolic code of the type, unique among the types of the Bitrix24 account |\n| `data.name` | string | Type name |\n| `data.senderCode` | string \\| null | Service that sends messages to the client, for example `bitrix24`. `null` — not set |\n| `data.isInfoNotificationOn` | boolean | Booking info message to the client |\n| `data.isConfirmationNotificationOn` | boolean | Booking confirmation request |\n| `data.isReminderNotificationOn` | boolean | Booking reminder |\n| `data.isFeedbackNotificationOn` | boolean | Feedback request |\n| `data.isDelayedNotificationOn` | boolean | Message to a client who is running late |\n| `data.isCancellationNotificationOn` | boolean | Booking cancellation message to the client |\n| `data.infoNotificationDelay` | number \\| null | How many seconds after the booking is made to send the booking info message |\n| `data.confirmationNotificationDelay` | number \\| null | How many seconds before the booking to send the first confirmation request |\n| `data.confirmationNotificationRepetitions` | number \\| null | How many times to repeat the confirmation request, not counting the first one |\n| `data.confirmationNotificationRepetitionsInterval` | number \\| null | Interval between repeats of the confirmation request |\n| `data.confirmationCounterDelay` | number \\| null | How many seconds before the booking an unconfirmed booking enters the counter |\n| `data.reminderNotificationDelay` | number \\| null | How many seconds before the booking to send the reminder. `-1` — on the morning of the booking day |\n| `data.delayedNotificationDelay` | number \\| null | After how many seconds of lateness to send the message to the client |\n| `data.delayedCounterDelay` | number \\| null | After how many seconds of lateness the booking enters the calendar counter |\n| `data.cancellationNotificationDelay` | number \\| null | Delay of the booking cancellation message |\n| `data.templateTypeConfirmation` | string | Confirmation request template: `inanimate`, `animate`, `inanimate_long` |\n| `data.templateTypeReminder` | string | Reminder template: `base` |\n| `data.templateTypeFeedback` | string | Feedback request template: `inanimate`, `animate` |\n| `data.templateTypeDelayed` | string | Late-arrival message template: `inanimate`, `animate` |\n\n## Response example\n\n```json\n{\n  \"success\": true,\n  \"data\": {\n    \"id\": 31,\n    \"code\": \"master\",\n    \"name\": \"Technicians\",\n    \"senderCode\": null,\n    \"isInfoNotificationOn\": false,\n    \"isConfirmationNotificationOn\": false,\n    \"isReminderNotificationOn\": false,\n    \"isFeedbackNotificationOn\": false,\n    \"isDelayedNotificationOn\": false,\n    \"isCancellationNotificationOn\": false,\n    \"infoNotificationDelay\": null,\n    \"confirmationNotificationDelay\": 86400,\n    \"confirmationNotificationRepetitions\": null,\n    \"confirmationNotificationRepetitionsInterval\": 10800,\n    \"confirmationCounterDelay\": 10800,\n    \"reminderNotificationDelay\": -1,\n    \"delayedNotificationDelay\": 300,\n    \"delayedCounterDelay\": 300,\n    \"cancellationNotificationDelay\": 600,\n    \"templateTypeConfirmation\": \"inanimate\",\n    \"templateTypeReminder\": \"base\",\n    \"templateTypeFeedback\": \"inanimate\",\n    \"templateTypeDelayed\": \"inanimate\"\n  }\n}\n```\n\n## Error response example\n\n404 — no type with this `id`:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"ENTITY_NOT_FOUND\",\n    \"message\": \"Booking record not found\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 404 | `ENTITY_NOT_FOUND` | No type with this `id` |\n| 400 | `INVALID_PARAMS` | `id` is not a positive integer. Message `id must be a positive safe integer` |\n| 401 | `MISSING_API_KEY` | The `X-Api-Key` header is not passed |\n| 401 | `TOKEN_MISSING` | The key has no Bitrix24 tokens |\n| 403 | `SCOPE_DENIED` | The key does not have the `booking` scope |\n| 429 | `RATE_LIMITED` | Request rate exceeded. The effective cap is in the `x-ratelimit-limit` header |\n| 502 | `BITRIX_RESPONSE_INVALID` | Bitrix24 returned a card of an unexpected shape |\n\nFull list of common API errors — [Errors](\u002Fdocs\u002Ferrors).\n\n## Known specifics\n\n**The type's resources come from a separate request.** The type card does not list its resources. To get them, call [`GET \u002Fv1\u002Fbooking-resources?typeId=31`](\u002Fdocs\u002Fentities\u002Fbooking-resources\u002Flist).\n\n**The booking message template is not returned in the card.** [Create](\u002Fdocs\u002Fentities\u002Fbooking-resource-types\u002Fcreate) and [update](\u002Fdocs\u002Fentities\u002Fbooking-resource-types\u002Fupdate) accept the `templateTypeInfo` field, but the card does not include it. The current template cannot be read through the API.\n\n## See also\n\n- [List booking resource types](\u002Fdocs\u002Fentities\u002Fbooking-resource-types\u002Flist)\n- [Update a booking resource type](\u002Fdocs\u002Fentities\u002Fbooking-resource-types\u002Fupdate)\n- [Booking resources](\u002Fdocs\u002Fentities\u002Fbooking-resources)\n- [Errors](\u002Fdocs\u002Ferrors)\n","# Update: Booking resource types\n\n`PATCH \u002Fv1\u002Fbooking-resource-types\u002F:id`\n\nChanges the fields of a booking resource type that are passed in the request. Fields missing from the request body keep their previous values.\n\nFields go at the root of the JSON, without a `fields` wrapper. Every request needs a new `code` — see \"Known specifics\".\n\n## Parameters\n\n| Parameter | Type | Required | Description |\n|----------|-----|:-----:|----------|\n| `id` (path) | number | yes | Type identifier. List: [`GET \u002Fv1\u002Fbooking-resource-types`](\u002Fdocs\u002Fentities\u002Fbooking-resource-types\u002Flist) |\n\n## Request fields (body)\n\n| Field | Type | Required | Description |\n|------|-----|:-----:|----------|\n| `code` | string | yes | New symbolic code of the type. Must differ from the current code and from the codes of other types |\n| `name` | string | no | Type name |\n| `isInfoNotificationOn` | boolean \\| string | no | Booking info message to the client. `true` \u002F `false` or `\"Y\"` \u002F `\"N\"` |\n| `isConfirmationNotificationOn` | boolean \\| string | no | Booking confirmation request |\n| `isReminderNotificationOn` | boolean \\| string | no | Booking reminder |\n| `isFeedbackNotificationOn` | boolean \\| string | no | Feedback request |\n| `isDelayedNotificationOn` | boolean \\| string | no | Message to a client who is running late |\n| `isCancellationNotificationOn` | boolean \\| string | no | Booking cancellation message to the client |\n| `senderCode` | string \\| null | no | Service that sends messages to the client, for example `bitrix24` |\n| `infoNotificationDelay` | number \\| null | no | How many seconds after the booking is made to send the booking info message |\n| `confirmationNotificationDelay` | number \\| null | no | How many seconds before the booking to send the first confirmation request |\n| `confirmationNotificationRepetitions` | number \\| null | no | How many times to repeat the confirmation request, not counting the first one |\n| `confirmationNotificationRepetitionsInterval` | number \\| null | no | Interval between repeats of the confirmation request, in seconds |\n| `confirmationCounterDelay` | number \\| null | no | How many seconds before the booking an unconfirmed booking enters the counter |\n| `reminderNotificationDelay` | number \\| null | no | How many seconds before the booking to send the reminder. `-1` — on the morning of the booking day |\n| `delayedNotificationDelay` | number \\| null | no | After how many seconds of lateness to send the message to the client |\n| `delayedCounterDelay` | number \\| null | no | After how many seconds of lateness the booking enters the calendar counter |\n| `cancellationNotificationDelay` | number \\| null | no | Delay of the booking cancellation message, in seconds |\n| `templateTypeInfo` | string | no | Booking message template: `inanimate`, `animate`, `inanimate_long`. Saved, but not returned in the type card |\n| `templateTypeConfirmation` | string | no | Confirmation request template: `inanimate`, `animate`, `inanimate_long` |\n| `templateTypeReminder` | string | no | Reminder template. The only value is `base` |\n| `templateTypeFeedback` | string | no | Feedback request template: `inanimate`, `animate` |\n| `templateTypeDelayed` | string | no | Late-arrival message template: `inanimate`, `animate` |\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X PATCH \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fbooking-resource-types\u002F31\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"name\": \"Nail technicians\",\n    \"code\": \"master-2\"\n  }'\n```\n\n### curl — OAuth application\n\n```bash\ncurl -X PATCH \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fbooking-resource-types\u002F31\" \\\n  -H \"X-Api-Key: YOUR_APP_KEY\" \\\n  -H \"Authorization: Bearer USER_SESSION_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"name\": \"Nail technicians\",\n    \"code\": \"master-2\"\n  }'\n```\n\n### JavaScript — personal key\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fbooking-resource-types\u002F31', {\n  method: 'PATCH',\n  headers: {\n    'X-Api-Key': 'YOUR_API_KEY',\n    'Content-Type': 'application\u002Fjson',\n  },\n  body: JSON.stringify({\n    name: 'Nail technicians',\n    code: 'master-2',\n  }),\n})\n\nconst { data } = await res.json()\nconsole.log(data.name, data.code)\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fbooking-resource-types\u002F31', {\n  method: 'PATCH',\n  headers: {\n    'X-Api-Key': 'YOUR_APP_KEY',\n    'Authorization': 'Bearer USER_SESSION_TOKEN',\n    'Content-Type': 'application\u002Fjson',\n  },\n  body: JSON.stringify({\n    name: 'Nail technicians',\n    code: 'master-2',\n  }),\n})\n\nconst { data } = await res.json()\nconsole.log(data.name, data.code)\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|----------|\n| `success` | boolean | `true` on success |\n| `data` | object | Card of the type after the change. The card fields are listed in the \"Response fields\" section of the [Get a booking resource type](\u002Fdocs\u002Fentities\u002Fbooking-resource-types\u002Fget) page |\n\n## Response example\n\n```json\n{\n  \"success\": true,\n  \"data\": {\n    \"id\": 31,\n    \"code\": \"master-2\",\n    \"name\": \"Nail technicians\",\n    \"senderCode\": null,\n    \"isInfoNotificationOn\": false,\n    \"isConfirmationNotificationOn\": false,\n    \"isReminderNotificationOn\": false,\n    \"isFeedbackNotificationOn\": false,\n    \"isDelayedNotificationOn\": false,\n    \"isCancellationNotificationOn\": false,\n    \"infoNotificationDelay\": null,\n    \"confirmationNotificationDelay\": 86400,\n    \"confirmationNotificationRepetitions\": null,\n    \"confirmationNotificationRepetitionsInterval\": 10800,\n    \"confirmationCounterDelay\": 10800,\n    \"reminderNotificationDelay\": -1,\n    \"delayedNotificationDelay\": 300,\n    \"delayedCounterDelay\": 300,\n    \"cancellationNotificationDelay\": 600,\n    \"templateTypeConfirmation\": \"inanimate\",\n    \"templateTypeReminder\": \"base\",\n    \"templateTypeFeedback\": \"inanimate\",\n    \"templateTypeDelayed\": \"inanimate\"\n  }\n}\n```\n\n## Error response example\n\n422 — the current `code` is passed in the body:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"BITRIX_ERROR\",\n    \"message\": \"Resource type with code \\\"master\\\" already exists\",\n    \"b24Code\": \"1011\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 404 | `ENTITY_NOT_FOUND` | No type with this `id`. Message `Booking record not found` |\n| 422 | `BITRIX_ERROR` | `code` matches the current code or the code of another type, `b24Code` `1011` |\n| 422 | `BITRIX_ERROR` | The body has no `code`. Message `Internal server error.` |\n| 400 | `INVALID_PARAMS` | `id` is not a positive integer. Message `id must be a positive safe integer` |\n| 400 | `INVALID_PARAMS` | Empty body. Message `Provide a non-empty object of fields` |\n| 400 | `INVALID_PARAMS` | A field not listed in the \"Request fields (body)\" table. Message `Unknown booking field` |\n| 400 | `INVALID_PARAMS` | A field value is an object or an array. Message `Fields must contain scalar values` |\n| 400 | `READONLY_FIELD` | `id` is passed in the body. Message `id is read-only` |\n| 401 | `MISSING_API_KEY` | The `X-Api-Key` header is not passed |\n| 401 | `TOKEN_MISSING` | The key has no Bitrix24 tokens |\n| 403 | `SCOPE_DENIED` | The key does not have the `booking` scope |\n| 403 | `WRITE_BLOCKED_READONLY_KEY` | The key is in read-only mode |\n| 429 | `RATE_LIMITED` | Request rate limit exceeded. The effective cap is in the `x-ratelimit-limit` header |\n| 502 | `BITRIX_RESPONSE_INVALID` | Bitrix24 returned a response of an unexpected shape. If this happened while re-reading the card after the write, the changes are already saved — check the type with a [get request](\u002Fdocs\u002Fentities\u002Fbooking-resource-types\u002Fget) before retrying |\n\nFull list of common API errors — [Errors](\u002Fdocs\u002Ferrors).\n\n## Known specifics\n\n**An update requires a new `code`.** A request without `code` is rejected with `422 BITRIX_ERROR` and the message `Internal server error.`; a request with the current code is rejected with `422 BITRIX_ERROR` saying that this code already exists. To change other fields and keep the original code, make two requests: the first with a temporary `code`, the second with the original one.\n\n## See also\n\n- [Get a booking resource type](\u002Fdocs\u002Fentities\u002Fbooking-resource-types\u002Fget)\n- [List booking resource types](\u002Fdocs\u002Fentities\u002Fbooking-resource-types\u002Flist)\n- [Create a booking resource type](\u002Fdocs\u002Fentities\u002Fbooking-resource-types\u002Fcreate)\n- [Errors](\u002Fdocs\u002Ferrors)\n","# Delete: Booking resource types\n\n`DELETE \u002Fv1\u002Fbooking-resource-types\u002F:id`\n\nDeletes a booking resource type that has never had resources. A deleted type cannot be restored through the API — create a new one if needed.\n\n## Parameters\n\n| Parameter | Type | Required | Description |\n|----------|-----|:-----:|----------|\n| `id` (path) | number | yes | Type identifier. List: [`GET \u002Fv1\u002Fbooking-resource-types`](\u002Fdocs\u002Fentities\u002Fbooking-resource-types\u002Flist) |\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X DELETE \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fbooking-resource-types\u002F33\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\" \\\n  -w \"%{http_code}\\n\"\n```\n\n### curl — OAuth application\n\n```bash\ncurl -X DELETE \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fbooking-resource-types\u002F33\" \\\n  -H \"X-Api-Key: YOUR_APP_KEY\" \\\n  -H \"Authorization: Bearer USER_SESSION_TOKEN\" \\\n  -w \"%{http_code}\\n\"\n```\n\n### JavaScript — personal key\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fbooking-resource-types\u002F33', {\n  method: 'DELETE',\n  headers: { 'X-Api-Key': 'YOUR_API_KEY' },\n})\n\nif (res.status === 204) {\n  console.log('Deleted')\n} else {\n  const { error } = await res.json()\n  console.log(error.code, error.message)\n}\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fbooking-resource-types\u002F33', {\n  method: 'DELETE',\n  headers: {\n    'X-Api-Key': 'YOUR_APP_KEY',\n    'Authorization': 'Bearer USER_SESSION_TOKEN',\n  },\n})\n\nif (res.status === 204) {\n  console.log('Deleted')\n} else {\n  const { error } = await res.json()\n  console.log(error.code, error.message)\n}\n```\n\n## Response\n\nOn successful deletion, the HTTP status is `204 No Content` with an empty body. The status code signals success, not the body.\n\n## Response example\n\n```\nHTTP\u002F1.1 204 No Content\n```\n\n## Error response example\n\n422 — resources are bound to the type:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"BITRIX_ERROR\",\n    \"message\": \"The type can not be deleted. There are resources of type\",\n    \"b24Code\": \"1012\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 404 | `ENTITY_NOT_FOUND` | The type with this `id` does not exist or was already deleted. Message `Booking record not found` |\n| 422 | `BITRIX_ERROR` | Resources are bound to the type. Message `The type can not be deleted. There are resources of type`, `b24Code` `1012` |\n| 422 | `BITRIX_ERROR` | The type's resources have been deleted, but the type has had resources before. Message `The field TYPE_ID is required.`, `b24Code` `1012` |\n| 400 | `INVALID_PARAMS` | `id` is not a positive integer. Message `id must be a positive safe integer` |\n| 401 | `MISSING_API_KEY` | The `X-Api-Key` header is not passed |\n| 401 | `TOKEN_MISSING` | The key has no Bitrix24 tokens |\n| 403 | `SCOPE_DENIED` | The key does not have the `booking` scope |\n| 403 | `WRITE_BLOCKED_READONLY_KEY` | The key is in read-only mode |\n| 429 | `RATE_LIMITED` | Request rate exceeded. The effective cap is in the `x-ratelimit-limit` header |\n| 502 | `BITRIX_RESPONSE_INVALID` | Bitrix24 did not confirm the deletion |\n\nFull list of common API errors — [Errors](\u002Fdocs\u002Ferrors).\n\n## Known specifics\n\n**Deleting resources does not free the type.** If the type has had at least one resource, it cannot be deleted even after all its resources are deleted. Before binding test resources to a type, keep in mind that the type itself will stay in the Bitrix24 account.\n\n## See also\n\n- [List booking resource types](\u002Fdocs\u002Fentities\u002Fbooking-resource-types\u002Flist)\n- [Booking resources](\u002Fdocs\u002Fentities\u002Fbooking-resources)\n- [Errors](\u002Fdocs\u002Ferrors)\n",1795000271059]