create a seating chart and event in seats.io and render it on a page
domain: docs.seats.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
POST an optional JSON body (name, venueType, categories) to /charts to create a chart; venueType is SIMPLE, WITH_SECTIONS_AND_FLOORS, or WITH_ZONES, defaulting to SIMPLE.
Design the chart's seats/sections in the seats.io Designer (or embedded Designer) and publish the draft version so it's usable.
POST to /events with the required chartKey and an optional eventKey, name, and date (yyyy-MM-dd) to create an event linked to that chart.
Embed the interactive floor plan in a page using the seats.io renderer, passing session: 'start' or 'continue' to generate a hold token for the visitor.
Reuse the same chart across multiple events by creating additional events against the same chartKey instead of redesigning the floor plan each time.
Known gotchas
Chart and event creation endpoints are not in the priority rate-limit lane — don't call them inside your live ticket sales flow, only for setup.
Chart-level categories are separate from per-event categories/objectCategories — you can override categorization at the event level without touching the chart.
An event's date must be between 2014-01-01 and up to 10 years in the future, or the create call fails.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?