Book from the wait list

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

booking.v1.Booking.createFromWaitList

Scope: booking. Reads accept READONLY keys.

Wait list id in the path. resourceIds is a non-empty resource id array. datePeriod matches booking creation: from/to each require timestamp (Unix seconds) and timezone (IANA).

Bitrix24 moves clients and the note into a new booking and removes the source wait list entry. The 201 response contains the booking read back in the GET /v1/bookings/:id shape. Notification-enabled resources may send SMS/messages to clients.

Example

curl -X POST 'https://vibecode.bitrix24.com/v1/booking-wait-list/42/booking' \
  -H 'X-Api-Key: YOUR_API_KEY' \
  -H 'Content-Type: application/json' -d '{"resourceIds":[42],"datePeriod":{"from":{"timestamp":1800000000,"timezone":"UTC"},"to":{"timestamp":1800003600,"timezone":"UTC"}}}'

Response

{
  "success": true,
  "data": {
    "id": 43,
    "resourceIds": [
      42
    ]
  }
}

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