[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-entities\u002Fbooking-wait-list\u002Fdelete":3,"docs-tabs-entities\u002Fbooking-wait-list\u002Fdelete":6},{"content":4,"lastmod":5},"# Delete an entry\n\n`DELETE \u002Fv1\u002Fbooking-wait-list\u002F:id`\n\nDeletes a record from the wait list. A deleted record 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 | Record identifier. List: [`GET \u002Fv1\u002Fbooking-wait-list`](\u002Fdocs\u002Fentities\u002Fbooking-wait-list\u002Flist) |\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X DELETE \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fbooking-wait-list\u002F29\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\"\n```\n\n### curl — OAuth application\n\n```bash\ncurl -X DELETE \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fbooking-wait-list\u002F29\" \\\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-wait-list\u002F29', {\n  method: 'DELETE',\n  headers: { 'X-Api-Key': 'YOUR_API_KEY' },\n})\n\nconst { data } = await res.json()\nconsole.log(data.id, data.deleted)\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fbooking-wait-list\u002F29', {\n  method: 'DELETE',\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.id, data.deleted)\n```\n\n## Response fields\n\nOn success, the method returns `200 OK` with a response body.\n\n| Field | Type | Description |\n|------|-----|----------|\n| `success` | boolean | `true` on success |\n| `data.id` | number | Identifier of the deleted record |\n| `data.deleted` | boolean | Always `true`: the record is deleted |\n\n## Response example\n\n```json\n{\n  \"success\": true,\n  \"data\": {\n    \"id\": 29,\n    \"deleted\": true\n  }\n}\n```\n\n## Error response example\n\n404 — there is no record with this `id`, including when you delete the same record again:\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` | There is no record with this `id`, including when you delete the same record again. Message `Booking record not found` |\n| 400 | `INVALID_PARAMS` | `id` is not a positive integer. Message `id must be a canonical 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. Message `Bitrix24 did not confirm the booking operation` |\n| 502 | `BITRIX_RESPONSE_INVALID` | Bitrix24 returned the record in an unexpected shape during the pre-deletion check. The record was not deleted |\n\nFull list of common API errors — [Errors](\u002Fdocs\u002Ferrors).\n\n## See also\n\n- [List wait list records](\u002Fdocs\u002Fentities\u002Fbooking-wait-list\u002Flist)\n- [Create a wait list record](\u002Fdocs\u002Fentities\u002Fbooking-wait-list\u002Fcreate)\n- [Book from the wait list](\u002Fdocs\u002Fentities\u002Fbooking-wait-list\u002Fbooking)\n- [Errors](\u002Fdocs\u002Ferrors)\n","2026-10-13",{},1795000274317]