Checkout flow
Reservations, orders, and payments — how a partner completes a ticket purchase.
Status: placeholder. Expand once the checkout endpoints are stabilized and annotated.
The checkout flow is:
- Reserve inventory —
POST /api/v1/reservationslocks ticket inventory for a short window. - Create an order —
POST /api/v1/ordersconverts a reservation into an order. - Collect payment —
POST /api/v1/payments/intentsstarts a payment intent (Stripe under the hood). - Confirm — on successful payment, Pylon issues the tickets.
Each step is documented endpoint-by-endpoint in the sidebar under the Reservations, Orders, and Payments tags.
Idempotency
Mutating endpoints accept an Idempotency-Key header. Partners should always send one to safely retry on network failures.
Errors
Pylon returns RFC 7807 problem details for error responses. See the reference for error schemas per endpoint.