Tickets

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, app dashboards, and app callbacks. The detailed ticket API guides live on atmosphere.tickets.

• 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.
• Ticket email delivery attempts are app-visible operational logs, but raw QR/pass secrets stay private.
• Ticket pages and emails may use event images plus organizer and app avatars as presentation metadata; validity still comes from ATM's private ticket state and opaque scan tokens.
• Add to Wallet actions appear only when ATM has generated active Apple/Google wallet pass URLs from platform provider credentials; QR remains the fallback.
• Printable PDF ticket attachments are deferred until after QR email, hosted ticket pages, and wallet passes are stable.
• First-party scanner staff sign into the scanner PWA and need private grants before they can verify or check in tickets.
• Event apps keep consumer-facing event pages and social UX.
• ATM Tickets handles payment-linked ticket truth and webhook events.
• Standard ticket callbacks and XRPC access are core integration surfaces, not paid add-ons.

1. The event app creates ticket tiers and capacity through ATM Tickets.
2. The buyer selects tickets in the event app.
3. The app creates a hold through the ticket API.
4. ATM checkout collects payment for paid tickets.
5. ATM issues tickets after payment succeeds.
6. The app receives signed events and shows tickets to the buyer.