# List booking wait list records

`GET /v1/booking-wait-list`

`booking.v1.WaitList.list`

Scope: `booking`. Reads accept READONLY keys.

filter is an object or JSON object with only createdWithin {from,to}: YYYY-MM-DD dates, exclusive upper bound. Example: `?filter[createdWithin][from]=2026-10-01&filter[createdWithin][to]=2026-10-03`. Bitrix24 ignores id, createdBy, includeDeleted, searchQuery and searchClients; the wrapper refuses them with 400 to avoid returning unrelated records.

Traversal follows page length and ignores Bitrix24 total. `meta.total` is the collected count and `meta.hasMore` is false. Cap: 5000 records; exceeding it returns 502 BITRIX_RESULT_TOO_LARGE. Narrow filter. Concurrent changes can shift pages. order, limit and offset are refused: the Bitrix24 controller has no order argument and ignores sorting.

## Example

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

## 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)

RU live check on 2026-10-02: a valid createdWithin returned the Bitrix24 refusal `Invalid date` (422). The wrapper forwards that refusal and does not return an unfiltered list.