# Create an entry

`POST /v1/booking-wait-list`

`booking.v1.WaitList.add`

Scope: `booking`. Reads accept READONLY keys.

Body: note is an optional string or null. `{}` is allowed and creates an empty entry with note: null. The 201 response contains the entry read back.

## Example

```bash
curl -X POST 'https://vibecode.bitrix24.com/v1/booking-wait-list' \
  -H 'X-Api-Key: YOUR_API_KEY' \
  -H 'Content-Type: application/json' -d '{"note":"VIBE-PROBE"}'
```

## Response

```json
{
  "success": true,
  "data": {
    "id": 42,
    "note": "VIBE-PROBE"
  }
}
```

## Errors

- `400 INVALID_PARAMS`: malformed id, body or filter; correct the parameters.
- `401 TOKEN_MISSING`: the key has no Bitrix24 connection.
- `403 SCOPE_DENIED`: add the `booking` scope. `WRITE_BLOCKED_READONLY_KEY` on writes: use a key that allows writes.
- `404 ENTITY_NOT_FOUND`: the record or CRM client is missing or inaccessible.
- `422 BITRIX_ERROR`: a Bitrix24 business refusal; the message contains its reason.
- `429`: rate limit; retry after `Retry-After`.
- `502`: invalid Bitrix24 response or incomplete traversal. No partial data is returned.
- `503`: Bitrix24 timeout.

## See also

[Wait list](/docs/entities/booking-wait-list) · [Bookings](/docs/entities/bookings)