Admin — list fulfillment orders for a user

Returns the fulfillment orders belonging to the given external user, newest first (by last_mutation_date). Each item includes its issued tickets inline, so a single paginated call is enough to render "all tickets for this user".

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.

Orders without tickets yet (PENDING / CONFIRMED before barcodes are assigned) are returned with an empty tickets array.

Deliverable PDF URLs are not included in list responses — call the single-order endpoint for a presigned download URL.

Unknown external_user_id yields an empty list (no 404). This avoids leaking user-existence signals to integrators.

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.

Query Params
integer
1 to 100
Defaults to 20

Number of items to return per page.

string

Opaque pagination cursor returned by a previous response.

string
enum

Filter results to orders in the given lifecycle state.

Allowed:
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