Pour les agents IA : markdown de cette page — /docs-content-en/entities/booking-wait-list/update.md index de la documentation — /llms.txt

Les articles de documentation sont actuellement disponibles en anglais.

Update an entry

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

booking.v1.WaitList.update

Scope: booking. Reads accept READONLY keys.

id in the path; note is an optional string. An empty string clears the note; null or omitted note leaves it unchanged. Returns the entry read back.

Example

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

Response

JSON 
{
  "success": true,
  "data": {
    "id": 42,
    "note": "VIBE-PROBE updated"
  }
}

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