Orders
Multi-booking checkout. An order is a shopping cart that groups one or more bookings. The typical flow is:
- Reserve —
POST /v2/booking-orderscreates the order and one or more bookings inON_HOLDstatus. Each booking holds its slot for 15 minutes. - Adjust —
POST .../addandPOST .../removemanage the cart contents;PATCH .../{id}updates order-level fields and patches individual bookings (payment details, extra-field answers, meeting point, notes...). - Confirm —
POST .../confirmfinalizes all bookings, transitioning them fromON_HOLDtoACCEPTED(instant confirmation) orPENDING(organizer review), and fires all side effects (confirmation emails, PMS folio entries, QR tickets).
An order can also carry retail lines (retailItems): products and gift vouchers sold from SKUs,
alongside bookings or on their own. They are held, confirmed and counted in the order's status and
totals just like bookings; see the Retail group.
Order status lifecycle
An order has no stored status of its own — status is derived from its bookings and retail lines:
| Status | Meaning |
|---|---|
ON_HOLD |
All active lines are still ON_HOLD (cart not yet confirmed). |
BOOKED |
At least one line has progressed past ON_HOLD (a booking ACCEPTED, PENDING, COMPLETED or CANCELLED; a retail line PAID, DELIVERED or CANCELLED). |
EXPIRED |
The order has lines but none are active — every hold timer ran out (or all were removed). |
Access scoping
Authentication uses the global x-api-key (+ optional x-partner-id) headers. You
only see orders you created — an order belonging to someone else returns 404, never
403, so its existence isn't leaked.
Choosing resources
To book a specific therapist, room, sunbed, table or rental unit, pass its id in a
booking's resources (ids come from the option's resourceGroups). Each resource
must belong to one of the option's resource groups and be free for the slot, or the
request returns 400. Leave resources out and Turneo assigns them.
Concierge-only fields
skipCutoff, and skipPending on confirm, along with booking slots in the past,
are reserved for Turneo's own concierge tooling and are not available to API-key
integrations: skipCutoff and skipPending are silently ignored, and a past slot
returns a 400. Omitted payment details default to processedBy: null /
status: PAYMENT_PENDING.
Endpoints
- GET
/v2/booking-ordersList booking orders - POST
/v2/booking-ordersCreate a booking order - GET
/v2/booking-orders/{id}Retrieve a booking order - PUT
/v2/booking-orders/{id}Replace a booking order's editable fields - DELETE
/v2/booking-orders/{id}Soft-delete a booking order - PATCH
/v2/booking-orders/{id}Update a booking order - POST
/v2/booking-orders/{id}/addAdd bookings or retail lines to an order - POST
/v2/booking-orders/{id}/removeRemove bookings or retail lines from an order - POST
/v2/booking-orders/{id}/confirmConfirm a booking order - POST
/v2/booking-orders/{id}/payment-linkSend a payment link email - POST
/v2/booking-orders/{id}/vouchersApply a promo code to an order - DELETE
/v2/booking-orders/{id}/vouchersRemove the promo code from an order - POST
/v2/booking-orders/{id}/remove-voucherRemove the gift voucher from an order - POST
/v2/booking-orders/{id}/concierge-discountApply a concierge discount to a booking - DELETE
/v2/booking-orders/{id}/concierge-discountRemove a concierge discount from a booking - POST
/v2/booking-orders/add-custom-bookingCreate a custom one-off booking