Soft-delete a booking order
DELETE/v2/booking-orders/{id}
Requires your API key in the X-API-Key header.
Soft-deletes the order: it is flagged inactive and disappears from list and retrieve endpoints, but the row is kept and its bookings are left completely untouched — bookings have their own lifecycle and are never cascaded. This is never a hard delete.
curl -X DELETE "https://api.turneo.co/v2/booking-orders/0f47ac10-b58c-4372-a567-0e02b2c3d479" \
-H "X-API-Key: <your-api-key>"Path parameters
idstring (uuid)requiredUUID of the booking order.
- Example:
0f47ac10-b58c-4372-a567-0e02b2c3d479
Responses
204
Order soft-deleted. No content.
Errors
- 401
Missing or invalid
X-API-Keyheader.- 404
The resource does not exist or belongs to another partner (existence is not leaked across partners).
Error body
typestringError class.
- Allowed values:
validation_errorclient_errorserver_error- Example:
validation_error
errorsobject[]Child fields
codestringMachine-readable error code.
- Example:
required
fieldstringnullableOffending field, or null/'general' for non-field errors.
- Example:
startTime
messagestringHuman-readable message.
- Example:
This field is required.
{
"type": "validation_error",
"errors": [
{
"code": "required",
"field": "startTime",
"message": "This field is required."
}
]
}