Receive ticket events.

Webhooks

Ticket events are delivered to the app endpoints configured in ATM app settings. Public ticket records should not contain arbitrary webhook URLs. Handlers must be idempotent because ATM can retry or redrive delivery.

ticket.hold.created
ticket.hold.expired
tickets.issued
ticket.refunded
ticket.voided
ticket.checked_in
ticket.form_submitted
ticket.waitlist.offered
ticket.collaboration.invited
ticket.collaboration.accepted
ticket.collaboration.revoked

Receiver options

HTTP webhooks are the default because any app can host them. AT Protocol-native apps may also configure an optional XRPC receiver callback for the same event envelope. In both cases, ATM signs the event and apps verify the signature before side effects.

POST https://app.example/xrpc/money.atmosphere.event.receive
Authorization: Bearer <atm service-auth jwt>

{
  "id": "evt_...",
  "deliveryId": "del_...",
  "type": "tickets.issued",
  "environment": "test",
  "data": { "eventUri": "at://...", "issuedCount": 2 }
}

Webhook test console

Build a local test command for signed HTTP webhooks or optional XRPC receivers. Real delivery status and redrive still live in the ATM app dashboard.

curl -X POST "https://your-app.example/webhooks/atm" \
  -H "ATM-Signature: t=...,v1=..." \
  -H "Content-Type: application/json" \
  --data '{"type":"tickets.issued","environment":"test","deliveryId":"del_test_123","data":{"eventUri":"at://..."}}'

Payload schemas

Ticket events use the same ATM event envelope as payment events: event id, delivery id, environment, type, app DID, createdAt, and a typed data payload. App handlers should branch on the event type and validate the data payload before side effects.

{
  "id": "evt_...",
  "deliveryId": "del_...",
  "environment": "test",
  "type": "tickets.issued",
  "appDid": "did:plc:app",
  "createdAt": "2026-06-05T00:00:00.000Z",
  "data": {
    "eventUri": "at://...",
    "issuedCount": 2,
    "buyerDid": "did:plc:buyer"
  }
}

Event catalog

Ticket lifecycle events are delivered through ATM app webhooks or optional XRPC receiver callbacks. Handlers must be idempotent and environment-aware. The table here mirrors the launch event families that ticketing apps subscribe to through the ATM app dashboard.