Reserved seating infrastructure

SeatLayer developer documentation.

Build the choose-your-seat moment: add reserved seating to ticketing, marketplaces, venue software, or a completely custom product—without giving up your checkout or brand.

Start building How it works

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/ev_9f3a/book', {
  method: 'POST',
  headers: { authorization: `Bearer ${secretKey}` },
  body: JSON.stringify({ holdId, bookingRef: order.id })
})

Choose your path

From first chart to confirmed booking.

Understand the model

Charts, events, seat lifecycle, and the browser/server trust boundary.

Read the overview

Embed the picker

Script tag, npm, and React examples with a complete checkout handoff.

Open Quickstart

Book from your server

Authentication, request fields, responses, conflicts, and safe retries.

Browse the API

One seating layer, many products

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

SeatLayer is a composable seating platform, not a replacement ticketing system. Start with an embeddable picker, or connect the Designer, live inventory, server API, control room, and webhooks into your own workflow.

Ticketing platforms

Isolate organisers with workspaces and run SeatLayer invisibly behind your own CMS.

Venues & marketplaces

Reuse venue charts across events while every performance keeps independent inventory.

Custom applications

Compose the SDK and HTTP API into booking, membership, travel, or internal tools.

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 agent—how to prove the integration is safe.

Integration best practices Build with an agent

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