Order & fulfilment status

After a booking is created, its tickets move through a fulfilment lifecycle. The current state is exposed as logistic_status on the bookingorder resource.

Happy flow

1. The tickets are booked.
2. logistic_status is processing: the sports venue or circuit is preparing the tickets.
3. The tickets are handed out by the venue.
4. logistic_status becomes completed: the tickets are ready to be printed or downloaded. (waitforactivation is deprecated.)
5. The end client logs in on xs2ticket.com with the booking code and email and can download the tickets.

Waiting for completion

Poll logistic_status until it reaches completed, see E-tickets & e-invoices for the recommended filter pattern. To be notified instead, subscribe to the bookingorder_completed and bookingorder_cancelled events in Webhooks.

logistic_status values

Value	Meaning
processing	The ticket is being prepared by the sports venue or circuit
completed	The ticket is available for download by the end client
cancelled	The ticket is cancelled and won't be delivered anymore
postponed	Delivery is postponed, for example because the event has been rescheduled
returned	The tickets were retrieved and can't be used anymore
review	The ticket file is under review
blocked	The item is blocked; the ticket is (being) sold on the marketplace
pendingticketupload	Waiting for the ticket file to be uploaded
administrative	Internal state; treat as not yet completed
waitforactivation	Deprecated: use completed

Treat unknown values defensively: new statuses may be added over time.

Payment status

Payment is tracked separately from fulfilment, in distributorfinancial_status on the same bookingorder. See the FAQ for how financial status relates to ticket release.

Next steps

• E-tickets & e-invoices: download tickets once an order is completed
• Webhooks: get notified on status changes
• FAQ