For AI agents: markdown of this page — /docs-content-en/entities/bookings/wait-list.md documentation index — /llms.txt

Move a booking to the wait list

POST /v1/bookings/:id/wait-list

booking.v1.WaitList.createFromBooking

Scope: booking. Reads accept READONLY keys.

Booking id in the path. No body is required. Bitrix24 moves clients and the note to the wait list and removes the source booking, freeing the time. The 201 response contains the wait list entry read back. Notifications depend on resource settings.

Example

Terminal 
curl -X POST 'https://vibecode.bitrix24.com/v1/bookings/42/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 · Bookings