Orders

Multi-booking checkout. An order is a shopping cart that groups one or more bookings. The typical flow is:

  1. Reserve — POST /v2/booking-orders creates the order and one or more bookings in ON_HOLD status. Each booking holds its slot for 15 minutes.
  2. Adjust — POST .../add and POST .../remove manage the cart contents; PATCH .../{id} updates order-level fields and patches individual bookings (payment details, extra-field answers, meeting point, notes...).
  3. Confirm — POST .../confirm finalizes all bookings, transitioning them from ON_HOLD to ACCEPTED (instant confirmation) or PENDING (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