Create order (checkout)
Authentication
Headers
Client app version. Required for ios, android, and web platforms. Optional for server platform. Format: Semantic version (e.g., “3.1.0”, “2.5.1”)
Idempotency key for safe retries. Required for order creation. Same key + same cartId within 24h returns existing order (200 OK). Same key + different cartId returns 409 Conflict. Format: idem_ prefix + random string.
Preferred language for error messages (defaults to en-US if not provided). Supported languages: en-US, en-GB, es-ES, fr-FR, de-DE, ja-JP. Format: RFC 9110 language tags with quality values.
Client-generated request identifier for distributed tracing. Server echoes this value in response headers. Format: req_ prefix + random string.
Request
Expected total amount that the client intends to pay. Critical for price validation: Server will reject the order if the cart’s actual total doesn’t match this value. This prevents unexpected charges if prices change between cart creation and checkout.
Contact information for this order (ticket pickup, delivery, and confirmation). Important: This contact information is per-order and may differ from the customer’s profile.
Response
Order ID (machine-readable)
Human-readable confirmation number for customer support and emails.
Contact information for this order (pickup, delivery, confirmation). Single source of truth for order contact details.
Items representing what was purchased (OrderItems with embedded tickets).
Structure: Each OrderItem contains a nested tickets[] array with fulfillment tickets.
Does NOT include: Fees, protection, or credits — see receiptLines for those.
Server-ordered display lines for receipt rendering. Iterate in sequence. Always includes SubtotalLine. Conditionally: FeeLine, VoucherLine, ProtectionLine.
Total amount charged. Server-computed. Never derive from parts.
When the order was created (UTC).
DISCLOSURE ONLY - taxes already included in total. Omitted when not disclosed (e.g., UK market).