Admin — retrieve tickets for a fulfillment order

Returns the tickets issued for a specific fulfillment order, plus a short-lived presigned download URL for the consolidated ticket PDF when one has been produced.

external_user_id is the same identifier the integrator supplied to POST /session when generating the user's authorization code — there is no separate platform user ID.

The order is resolved by fulfillment_order_id and must belong to the external_user_id in the path. If either the order does not exist or it belongs to a different user, 404 Not Found is returned without distinguishing between the two — this prevents enumeration of order IDs across users.

If the order exists and belongs to the user but tickets have not yet been assigned (status PENDING / CONFIRMED), 409 Conflict is returned with the current status so the caller can poll.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

Identifier of the user in the integrator's system. This is the same value the integrator supplied as external_user_id when generating an authorization code via POST /session (see GenerateAuthCodeRequest.external_user_id). The platform stores it verbatim and uses it as the canonical user reference across loyalty, fulfillment, and other admin endpoints — there is no separate platform user ID to look up.

uuid
required

Platform-generated identifier of the fulfillment order.

Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Language
Credentials
OAuth2
Missing 1 required scope
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
application/problem+json