Skip to content
XOS Developers

Delete a BEO

Hospitality module

DELETE/beos/{id}beos.delete

A banquet event order. Soft-deletes the BEO: it moves to Trash and can be restored for its table's retention period.

  • Requires the capability hospitality.beo.write.
  • OAuth scopes: hospitality.
  • Error statuses: 401, 404, 422, 429. Errors are RFC 9457 problem details.

Path and query parameters

beos.delete: Path and query parameters
FieldTypeRequiredDescription
idstring (uuid)YesIdentifier of the beo.

Response 204: no body.

Code samples

curl -X DELETE "$XOS_BASE_URL/beos/0192f1e2-7c3a-7b4d-9e8f-1a2b3c4d5e6f" \
  -H "Authorization: Bearer $XOS_API_KEY"
const { data } = await xos.beos.delete("0192f1e2-7c3a-7b4d-9e8f-1a2b3c4d5e6f");
response = xos.beos.delete("0192f1e2-7c3a-7b4d-9e8f-1a2b3c4d5e6f")
xos beos delete 0192f1e2-7c3a-7b4d-9e8f-1a2b3c4d5e6f