Set it up. Build on it.
Run the night.
Guides, Blueprints and reference for Backstage, Live and every app at the venue. Pick your door, or just ask.
Which one are you today?
Three doors into the same docs. Every feature page has a section for each of you.
Set up events, seat maps, prices, channels and your team in Backstage, and know what each setting does for your fans.
- Seat maps, capacity and holdsFeature
- Live Storefront or Elements?Choose
- Put your storefront liveTask
- Tag members and VIPsConcept
- Price per channel with offersConcept
<!-- Your event page --> <tl-event-list columns="3"></tl-event-list> <tl-buy-tickets-button event-id="evt_..."> </tl-buy-tickets-button>
Sell on your own site with Elements, build on the Backstage and Live APIs, and follow Blueprints across Backstage and code.
- Sell on your site in five minutesQuickstart
- Get API keysTask
- Memberships with ticket discountsBlueprint
- Receive webhooksTask
- Connect Claude or CursorTask
Short, step-by-step help for Box Office, Go, printers and scanners. Written for the moment there is a queue.
Open At the venueNot sure which way to go?
Everything Ticketlayer does
The same eight names as Backstage and the website. One page per feature, for every role.
Build the thing, the proven way.
End-to-end recipes across Backstage and the API. One way, not every way.
Your assistant reads the same docs.
llms.txt, llms-full.txt and the OpenAPI documents are generated from the pages you read. The MCP server does the work.
claude mcp add --transport http ticketlayer \ https://mcp.ticketlayer.com/mcpConnect an assistant
Ask Cue inside Backstage, or talk to a person. Include the request id from any error and we can see exactly what happened.