Skip to main content

Fulfilment

Answers one question about an accepted order: where is the actual ticket? Retail polls this every 10 minutes for every accepted order that has not been delivered, which is the window where a buyer has paid and holds nothing. Each system releases tickets differently: a document, a list of barcodes per seat, a transfer into an account, a parcel. Your integration translates that into one of the states below.
References here, never the credential. This endpoint is polled and its results are logged. Return a pointer in barcodeRef (an id or URL you can resolve later), never the scannable barcode itself. The barcode goes out once, through Credentials.

Query Parameters

string
required
Your supplier identifier.
string
required
Your order id, from Place order.
Answer 404 if you do not know this order. Retail reads that as “not yet” and asks again. Any other failure is reported as a failure, never as “nothing to deliver”.

Response

string
required
The order asked about.
string
required
array
default:"[]"
One entry per admission credential. Required and non-empty when state is ready. Retail refuses a ready with no tickets, because that would mark an order delivered with nothing delivered.
object
Required when state is shipped.
string
The delivery format actually used, with the same values as format on Listings. Kept for the audit trail.
any
Your system’s payload, as evidence. Must not contain barcodes or buyer data.