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

Delete a booking

DELETE /v1/bookings/:id

Deletes a booking by id. A deleted booking cannot be restored through the API — create a new one if needed.

Parameters

Parameter Type Required Description
id (path) number yes Booking id

Examples

curl — personal key

Terminal 
curl -X DELETE "https://vibecode.bitrix24.com/v1/bookings/27" \
  -H "X-Api-Key: YOUR_API_KEY"

curl — OAuth application

Terminal 
curl -X DELETE "https://vibecode.bitrix24.com/v1/bookings/27" \
  -H "X-Api-Key: YOUR_APP_KEY" \
  -H "Authorization: Bearer USER_SESSION_TOKEN"

JavaScript — personal key

javascript 
const res = await fetch('https://vibecode.bitrix24.com/v1/bookings/27', {
  method: 'DELETE',
  headers: {
    'X-Api-Key': 'YOUR_API_KEY',
  },
})

if (res.status === 204) {
  console.log('Booking deleted')
}

JavaScript — OAuth application

javascript 
const res = await fetch('https://vibecode.bitrix24.com/v1/bookings/27', {
  method: 'DELETE',
  headers: {
    'X-Api-Key': 'YOUR_APP_KEY',
    'Authorization': 'Bearer USER_SESSION_TOKEN',
  },
})

if (res.status === 204) {
  console.log('Booking deleted')
}

Response

On successful deletion an HTTP status 204 No Content is returned with an empty body. The success indicator is the response code, not the body.

Response example

http 
HTTP/1.1 204 No Content

Error response example

422 — the booking is already deleted or does not exist:

JSON 
{
  "success": false,
  "error": {
    "code": "BITRIX_ERROR",
    "message": "booking not found"
  }
}

Errors

HTTP Code Description
422 BITRIX_ERROR The booking with the given id was not found or is already deleted. Message: booking not found
403 SCOPE_DENIED The API key does not have the booking scope
401 MISSING_API_KEY The request was sent without the X-Api-Key header
401 TOKEN_MISSING The API key has no configured tokens

Full list of common API errors — Errors.

See also