# Delete an entry

`DELETE /v1/booking-wait-list/:id`

Deletes a record from the wait list. A deleted record cannot be restored through the API — create a new one if needed.

## Parameters

| Parameter | Type | Required | Description |
|----------|-----|:-----:|----------|
| `id` (path) | number | yes | Record identifier. List: [`GET /v1/booking-wait-list`](/docs/entities/booking-wait-list/list) |

## Examples

### curl — personal key

```bash
curl -X DELETE "https://vibecode.bitrix24.com/v1/booking-wait-list/29" \
  -H "X-Api-Key: YOUR_API_KEY"
```

### curl — OAuth application

```bash
curl -X DELETE "https://vibecode.bitrix24.com/v1/booking-wait-list/29" \
  -H "X-Api-Key: YOUR_APP_KEY" \
  -H "Authorization: Bearer USER_SESSION_TOKEN"
```

### JavaScript — personal key

```javascript
const res = await fetch('https://vibecode.bitrix24.com/v1/booking-wait-list/29', {
  method: 'DELETE',
  headers: { 'X-Api-Key': 'YOUR_API_KEY' },
})

const { data } = await res.json()
console.log(data.id, data.deleted)
```

### JavaScript — OAuth application

```javascript
const res = await fetch('https://vibecode.bitrix24.com/v1/booking-wait-list/29', {
  method: 'DELETE',
  headers: {
    'X-Api-Key': 'YOUR_APP_KEY',
    'Authorization': 'Bearer USER_SESSION_TOKEN',
  },
})

const { data } = await res.json()
console.log(data.id, data.deleted)
```

## Response fields

On success, the method returns `200 OK` with a response body.

| Field | Type | Description |
|------|-----|----------|
| `success` | boolean | `true` on success |
| `data.id` | number | Identifier of the deleted record |
| `data.deleted` | boolean | Always `true`: the record is deleted |

## Response example

```json
{
  "success": true,
  "data": {
    "id": 29,
    "deleted": true
  }
}
```

## Error response example

404 — there is no record with this `id`, including when you delete the same record again:

```json
{
  "success": false,
  "error": {
    "code": "ENTITY_NOT_FOUND",
    "message": "Booking record not found"
  }
}
```

## Errors

| HTTP | Code | Description |
|------|-----|----------|
| 404 | `ENTITY_NOT_FOUND` | There is no record with this `id`, including when you delete the same record again. Message `Booking record not found` |
| 400 | `INVALID_PARAMS` | `id` is not a positive integer. Message `id must be a canonical positive safe integer` |
| 401 | `MISSING_API_KEY` | The `X-Api-Key` header is not passed |
| 401 | `TOKEN_MISSING` | The key has no Bitrix24 tokens |
| 403 | `SCOPE_DENIED` | The key does not have the `booking` scope |
| 403 | `WRITE_BLOCKED_READONLY_KEY` | The key is in read-only mode |
| 429 | `RATE_LIMITED` | Request rate exceeded. The effective cap is in the `x-ratelimit-limit` header |
| 502 | `BITRIX_RESPONSE_INVALID` | Bitrix24 did not confirm the deletion. Message `Bitrix24 did not confirm the booking operation` |
| 502 | `BITRIX_RESPONSE_INVALID` | Bitrix24 returned the record in an unexpected shape during the pre-deletion check. The record was not deleted |

Full list of common API errors — [Errors](/docs/errors).

## See also

- [List wait list records](/docs/entities/booking-wait-list/list)
- [Create a wait list record](/docs/entities/booking-wait-list/create)
- [Book from the wait list](/docs/entities/booking-wait-list/booking)
- [Errors](/docs/errors)