Atmosphere
Tickets
Ticketing infrastructure for developers building Atmosphere event apps. Keep discovery, event pages, social context, organizer UX, and attendee experience inside your app. Atmosphere Tickets handles the hard work behind the scenes: scarce inventory, checkout holds, payment-linked issuance, delivery, QR verification, and check-in truth across compatible apps.
Scroll down to see more.
For event app developers
Build the event product your community sees. Tickets gives your app the infrastructure for the parts that must not race, leak, double sell, or drift between apps.
Apps use community.lexicon.calendar.event and RSVP
records, then call ATM Tickets from trusted server code for
availability, setup, holds, free claims, fulfillment, and scanner
workflows.
Organizer-owned ticketed-event config, tiers, capacity groups, checkout holds, free limited claims, issued tickets, pass tokens, attendee answers, waitlists, collaborations, and check-in state.
Paid ticket purchases stay in ATM's unified payment ledger. Organizer approval gates app selling, app fees, receipts, refunds, and delivery all route through ATM.
at://did:plc:organizer/community.lexicon.calendar.event/night-market
290 of 950 tickets leftSales paths
Your app owns the buyer flow and event context. Atmosphere Tickets backs the scarce state behind payment, free claims, waitlists, and entry.
Reserve capacity before payment, send the buyer through ATM checkout, and issue tickets only after payment is confirmed.
Use buyer assertions and transactional capacity for scarce free tickets without creating noisy $0 payment rows.
Keep waitlist order, offer holds, and private counters in Tickets while your app receives signed lifecycle events.
Atmosphere Tickets provides wallet-ready pass data, private QR tokens, and idempotent scan check-ins so event apps can offer wallet support and entry scanning without rebuilding that infrastructure.
Developer surface
Use the ATM App Node SDK or direct XRPC calls from trusted server code. The browser should never hold app service-auth tokens, webhook secrets, buyer assertions, or scan tokens.
ATM
const availability = await atm.getTicketAvailability({
environment: "test",
eventUri,
});
const hold = await atm.createTicketHold({
environment: "test",
eventUri,
buyerDid,
buyerAssertionJwt,
items: [{ tierId, quantity: 2 }],
returnUrl,
cancelUrl,
});
return Response.redirect(hold.url);Mint service-auth on your backend and pass buyer assertions only to the ticket hold endpoint.
createTicketEvent, updateTicketEvent, tiers, capacity groups, public offers.
getTicketAvailability, createTicketHold, releaseTicketHold, claimFreeTicket.
Buyer and organizer lists, verification, check-in, waitlists, collaborations, tier forms, attendee answers.
Signed HTTP webhooks and optional XRPC receiver callbacks for issuance, check-in, forms, waitlists, and collaboration changes.
community.lexicon.calendar.eventcommunity.lexicon.calendar.rsvptickets.atmosphere.ticketTiertickets.atmosphere.capacityGrouptickets.atmosphere.checkInListtickets.atmosphere.publicOffermoney.atmosphere.product and price refsBy ATM
App registration, module enablement, recipient approvals, app fee policy, checkout, payment ledger, refunds, settlement, webhook delivery, and test/live environment controls.
Organizer-owned ticket config, inventory transactions, holds, issuance, pass delivery, scanner access, check-in, waitlists, attendee data, forms, collaborations, audit history.
Event creation, storefronts, ticket picker, discovery, social context, SEO, organizer UX, buyer support, analytics views, and custom scanner or attendee workflows.
Developer ready
Use the same ATM app identity, service-auth, webhook, and XRPC patterns as payments. Your app keeps the event product; Atmosphere Tickets handles holds, issuance, QR passes, scanner verification, waitlists, forms, refunds, voids, and callbacks behind the scenes.