Hosted Ticketing is for venues and organizers selling their own seated events. SeatLayer runs the checkout, the order, the tickets and the door. You keep the chart, the prices, your payment gateway and your buyers.
If you are building a ticketing product and want to keep your own checkout, use the Platform SDK quickstart instead.
What you get
| Part | What it does |
|---|---|
| Payments | Buyers pay into your own gateway account, through one of 14 gateways. SeatLayer never holds your money. |
| Event setup | Free or paid, the payment account, the booking form, the buyer language and ticket limits. |
| Checkout | Seat hold with a countdown, order lines, one email field, then your gateway’s payment page. |
| Tickets | One ticket per seat, with a QR code, a printable PDF and a confirmation email. |
| Box office | Sell at the counter from the same live map, print on an 80 mm roll or A4, find any order. |
| Refunds and cancellations | Refund in full or in part through the gateway, or cancel when the money was handled elsewhere. |
| Door check-in | Scan tickets in a phone browser. No app to install. |
| Staff roles | Give counter staff a role that can sell and scan but cannot refund. |
Online sales, the counter and the door all read one live inventory. A seat sold at the counter disappears from every buyer’s screen at once.
How it works
Build the chart and create the event
Start from a template or draw the room, then create the event on it. See Your first managed event.
Connect your payment gateway
Connect your gateway on Settings → Payments and assign it to the event in Setup → Checkout. Free events skip this step. See Event setup.
Put it where buyers are
Paste the event block into your website, or share the hosted event page. Open the Box office tab on the day.
What developers can reach
Hosted Ticketing is run from the dashboard, and its orders stay there. There is
no public API to list or read the orders of one event, and no order.*
webhook. What a developer can use:
- Seat webhooks. A hosted sale books seats like any other booking, so
seat.bookedfires for it. See webhook events. - The event’s inventory report as JSON, through the Server API. It shows seats and configured prices, not the money your gateway collected.
- Event settings such as ticket limits, through
PATCH /v1/events/:key. See Event setup.
Order data leaves the dashboard as files, downloaded by a signed-in team member:
| File or view | Where |
|---|---|
orders.csv, every order with its buyer, filtered as on screen |
Orders → Export CSV |
door-list.csv, one line per seat, sorted by buyer name, with no email addresses |
Door → Download door list (CSV) |
| Attendance: checked in, not yet arrived, refunded | Door tab |
| The event report as CSV | Performance → Export CSV |
| Box office money by payment method, and discounts and comps by reason | Performance tab |
Price
Each confirmed ticket costs $0.50, paid from the Hosted Ticket wallet. Every new organization gets 25 Hosted Tickets once. A ticket on a free event uses one Hosted Ticket too. Your gateway charges its own processing fee and sets payout timing. See Pricing.