Skip to content

Start here

Choose an integration

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

Choose an integration

Pick the smallest path that fits your site.

Who this is for

Independent venues deciding how to sell tickets with AXYN.

Paths

PathWhenStart
HostedBuyers go to axyn.events. AXYN runs checkout. You do not install @axyn/web-sdk.Link out from your site
EmbedYou have a React site and want checkout on your pageQuickstart
HeadlessYou own the UI and call /v1 from your serverGet started
ScannerDoor staff admit ticketsKeys & login

Same four paths as a one-screen table: Integration tiers.

Hosted

Buyers open your event on axyn.events. AXYN operates that checkout (internal TicketPanel, not a partner mount). You link out. You do not install @axyn/web-sdk for this path.

Embed (React checkout)

Install the private @axyn/web-sdk channel AXYN gives you and mount CheckoutSpineRoot inline. Your server proxies Partner /v1 with x-api-key. Never put that key in the browser.

Headless (Custom API)

Your server holds x-api-key. The browser uses a buyer JWT for checkout calls only. Follow Get started, then How headless works.

Scanner

Door apps use x-scanner-token (or a staff JWT), not the checkout API key. See Keys & login.

Ticket view is separate from checkout. Buyers open a live pass on an AXYN-hosted page (email link) by default. See Ticket delivery, Live pass, and Transfer.

Aggregators

If you sell many venues under one platform, stop here and read Multi-venue platforms. That path is white-glove, not DIY.

Next