Skip to content

Custom API

Webhooks

Reference only. Not a decision unless cited in product/DECISIONS.md.

Webhooks

There are two different webhook systems. Do not mix them up.

Who this is for

Engineers who need async order or ticket updates in their own systems.

1. Stripe → AXYN (shipped)

Stripe sends payment events to AXYN at /v1/webhooks/stripe. AXYN verifies Stripe signatures and updates orders. You do not implement this endpoint.

2. AXYN → your server (partner outbound)

Product intent: signed partner webhooks for events such as order paid, ticket issued, refund approved, and ticket scanned.

Status: not a complete public partner delivery surface yet. Do not build production fan-out against invented HMAC headers. When partner outbound webhooks ship, this page will document:

  • Event catalog
  • Signature header and verification
  • Retry and idempotency rules
  • Local tunnel testing

Until then, poll documented order and ticket read endpoints, or use the hosted/embed surfaces that already handle post-purchase UX.

Upgrade status after pay: poll GET /v1/ticket-url/{token} (guest) or GET /v1/me/tickets (signed-in). Do not invent a ticket.upgraded HMAC. See Upgrade.

Common mistakes

  • Pointing Stripe webhooks at your app instead of AXYN.
  • Assuming partner outbound webhooks are live because Stripe inbound is.
  • Documenting or copying secrets into client code.

Next