Docs
Tickets
ATM ledger and app configuration for ticketing, with ticket-specific docs living on atmosphere.tickets.
Compatible with the closed-beta ATM app APIs and versioned ATM event headers. Check atm-api-version on every webhook or XRPC receiver event.
Where ticket docs live
Ticketing has its own developer surface because it includes inventory, holds, QR/pass tokens, scanner flows, event app integration, and organizer operations. ATM docs cover how ticket purchases fit into payments, auth, and app webhooks. The detailed ticket API guides should live on atmosphere.tickets.
ATM boundary
- Ticket purchases appear in the unified ATM payments ledger.
- Ticket apps use app service-auth plus user assertions for buyer or organizer actions.
- Scarce inventory, holds, attendee data, QR secrets, and check-ins stay private.
- Event apps keep consumer-facing event pages and social UX.
- ATM Tickets handles payment-linked ticket truth and webhook events.
Developer flow
- The event app creates ticket tiers and capacity through ATM Tickets.
- The buyer selects tickets in the event app.
- The app creates a hold through the ticket API.
- ATM checkout collects payment for paid tickets.
- ATM issues tickets after payment succeeds.
- The app receives signed events and shows tickets to the buyer.