Skip to content
Docs
Ticketlayer docs

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.

Ask Cue

Which one are you today?

Three doors into the same docs. Every feature page has a section for each of you.

EventsCreate event
Midsummer Comedy ClubFri 12 Jun · Pier TheatreOn sale
The TempestFri 9 Oct · Main HouseOn sale
Winter GalaSat 12 Dec · Main HouseDraft
ManageAdministrators and organisers

Set up events, seat maps, prices, channels and your team in Backstage, and know what each setting does for your fans.

Open Manage
index.html
<!-- Your event page -->
<tl-event-list columns="3"></tl-event-list>

<tl-buy-tickets-button
  event-id="evt_...">
</tl-buy-tickets-button>
BuildDevelopers

Sell on your own site with Elements, build on the Backstage and Live APIs, and follow Blueprints across Backstage and code.

Open Build
DevicesPier Theatre
Ticket printerUSBReady
Door 1 scannerGoScanning
Box OfficeTill 2Signed in
At the venueBox office and door staff

Short, step-by-step help for Box Office, Go, printers and scanners. Written for the moment there is a queue.

Open At the venue
Choose your setup

Not sure which way to go?

All guides

Everything Ticketlayer does

The same eight names as Backstage and the website. One page per feature, for every role.

Blueprints

Build the thing, the proven way.

End-to-end recipes across Backstage and the API. One way, not every way.

All Blueprints
For AI agents

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/mcp
Connect an assistant
Still stuck?

Ask Cue inside Backstage, or talk to a person. Include the request id from any error and we can see exactly what happened.