Skip to content

Seating charts in 2D and 3D, ticketing from chart to door

SeatLayer developer documentation.

Draw a chart and run the event end to end in the dashboard, build the same pieces into your own platform with the SDK, or let an AI agent build the chart over MCP. Every chart up to 60,000 seats has a 3D view and a view from each seat, built from the chart itself, and the picker offers both by default.

Test mode includedBrowser holdsServer books
checkout.ts
// Browser: hold and hand off
onCheckout: (_, __, handoff) =>
  fetch('/api/checkout', {
    body: JSON.stringify({
      holdId: handoff.holdId
    })
  })

// Server: confirm the sale
await fetch('https://api.seatlayer.io/v1/events/<YOUR_EVENT_KEY>/book', {
  method: 'POST',
  headers: { authorization: `Bearer ${secretKey}` },
  body: JSON.stringify({ holdId, bookingRef: order.id })
})

Choose your path

From first chart to confirmed booking.

One seating layer, many products

Use the pieces you need. Keep the product you already have.

For platforms, SeatLayer is a seating layer that sits inside the ticketing you already run. Start with an embeddable picker, or connect the Designer, live inventory, server API, control room, and webhooks into your own workflow.

Built to be implemented

Explanation for people. Precise contracts for agents.

01 · Understand

Mental model first

Every journey begins with ownership, trust boundaries, and the lifecycle, not a wall of endpoints.

02 · Implement

Complete examples

Copy-ready browser and server code includes retries, conflicts, security, and production failure paths.

03 · Verify

A definition of done

Best practices and checklists tell a developer or an agent how to prove the integration is safe.

Agent-ready by default

The same pages work for developers and coding agents.

Every guide has a Markdown twin, while the docs homepage negotiates the generated llms.txt agent index.

View agent index

Type to search…

↑↓ navigate↵ selectEsc close