Atmosphere Tickets Docs
Built on AT Protocol

Atmosphere Tickets

Federated ticketing infrastructure for AT Protocol event apps. Use the community event lexicon for the public event graph; keep social, discovery, organizer UX, and attendee experience in your app. Tickets coordinates holds, issuance, refunds, transfers, and check-in state across every app selling into the same event.

By ATM

Scroll down to see more.

The split

Your app runs the event experience. Tickets coordinates the shared scarce state.

Event apps

Use community.lexicon.calendar.event and community.lexicon.calendar.rsvp. Build discovery, event pages, organizer tools, social surfaces, widgets, SEO, scanner UI, analytics, and the branded attendee journey.

Atmosphere Tickets

Enforce inventory, create capacity holds, issue tickets after ATM payment, verify entry tokens, and preserve an audit trail.

ATM

Handles checkout, fees, payment attestations, organizer settlement, refunds, and the unified money dashboard.

Checkout flow

A ticket purchase starts with a hold, not a charge.

  1. 01

    Read public catalog

    Your app reads event records and public ticket tier metadata from AT Protocol.

  2. 02

    Create a private hold

    Tickets locks the tier and capacity groups in a transaction, then reserves inventory for a short checkout window.

  3. 03

    Send the buyer to ATM

    ATM starts checkout using the hold reference, app DID, organizer DID, ticket tier, amount, fees, and safe display metadata.

  4. 04

    Issue after payment

    Tickets promotes the hold only after ATM confirms a paid or settled state by webhook.

Developer surface

Small XRPC contracts for the ticketing path.

GET  /xrpc/atmosphere.tickets.getTicketAvailability
POST /xrpc/atmosphere.tickets.createTicketHold
POST /xrpc/atmosphere.tickets.releaseTicketHold
GET  /xrpc/atmosphere.tickets.listBuyerTickets
GET  /xrpc/atmosphere.tickets.listOrganizerTickets
POST /xrpc/atmosphere.tickets.verifyTicket
POST /xrpc/atmosphere.tickets.checkInTicket

Public records stay public

Events and RSVPs stay in the community event lexicon. Ticket tiers, capacity group labels, check-in list metadata, and intentional public offers live under the atmosphere.tickets namespace.

Private state stays private

Buyer PII, exact counters, holds, issued ticket IDs, QR secrets, attendee answers, and check-in logs remain off protocol.

By ATM

Ticket payments belong in the same money dashboard.

ATM remains the shared money layer for organizers: ticket sales, shop purchases, subscriptions, fees, payouts, refunds, and attestations. Atmosphere Tickets coordinates the operational layer: inventory, attendees, check-in, transfers, voids, and ticket status.

ATM Dashboard Payments, Products, Tickets, Payouts, Reports

Unified financial truth with a lightweight Tickets bridge.

Atmosphere Tickets Events, Orders, Attendees, Check-in, Promos

Operational truth for ticket inventory and entry.

Developer ready

Sell tickets without sacrificing app UX or shared availability.

Add ticketing to an Atmosphere app while keeping event pages, social context, organizer workflows, and attendee UX in your product. Tickets coordinates checkout-linked issuance, verification, and audit state across apps selling into the same event.

Read the integration docs