Retrieve tickets

Endpoint to poll for order status and retrieve the tickets.

Tickets will be available once the order_status has reached the done state.

If the order_status changes from pending to failed, the order was not successful and cannot be fulfilled. Please refund your customer. Failed orders are not invoiced by Tiqets.

Only once the order_status is done (see example below) the order was confirmed and fulfilled successfully.

Polling versus Webhook

To avoid periodic polling, use the callback_url. When implemented, the callback URL will be called by Tiqets every time the order status changes (e.g., the PDF voucher is ready).

Still opting for polling? Then we recommend implementing an "exponential back-off" mechanism or a 5 - 10 minutes interval wait while retrying until the order is in a final status (failed / done / canceled) for a maximum of 24 hours.

Fulfilment Speed

The majority of Tiqets products are fulfilled immediately.

There are however some products where fulfilment can be delayed because of the ticket supplier, specific handling of the ticket or other circumstances. These Products with a higher risk of fulfilment delay can be identified by the property instant_ticket_delivery being set to false.

These products are typically fulfilled within 30 minutes but there can be circumstances when this can go up to a max of 24 hours.

It is up to the API partner to decide to support these products or not.

Retrieve tickets

get
/orders/{orderReferenceId}/tickets
Path parameters
orderReferenceIdstringRequired

Tiqets Order ID.

Example: 1111111
Query parameters
langstringOptional

Language of the content to retrieve (ISO 639-1). Defaults to English if undefined.

Default: enExample: en
Header parameters
AuthorizationstringRequired

Token <Your_API_Key>.

Default: Token <Partner_API_key>.
Responses
get
/orders/{orderReferenceId}/tickets

Last updated

Was this helpful?