Can I use the Venue Designer without signing up?
Yes. The Designer playground opens without signup. You can work in the browser and create an account when you want cloud continuity, publishing, or team workflows.
Does the same chart power 2D and 3D?
Yes. SeatLayer publishes one venue document. The buyer experience can use the complete 2D Map and optionally add the geometry-generated 3D view.
Can I trace a venue plan?
Yes. PNG, JPEG, or WebP can be used as a private trace reference. For PDF, choose one page from a source up to 15 MB and 100 pages; that page is rasterized for tracing.
Can a ticketing platform embed the Designer?
Yes. JavaScript and React hosts can open an origin-scoped Designer session for one workspace and chart, with explicit save, publish, close, and revocation controls.
What is a seat map designer?
It is the tool that builds the seating model a ticketing system sells from: rows and curved rows, tables, booths, sections, general-admission areas, floors, price categories and accessibility marks, held in one venue document. A seat map designer differs from a drawing tool because its output is structured and versioned — the buyer picker, the optional 3D view, live inventory and the box office all read the same published revision, so the chart is designed once and reused for every event in that room.
Can I embed the seating chart designer in my own product?
Yes. Your server authorizes the host user, decides their Designer authority, and mints a short-lived
dse_… session bound to one workspace, one chart and one origin; the SDK mounts the returned designer URL and validates messages. Your product reacts to ready, saved, published, close and error events, replaces the session before or after expiry, and revokes it immediately when access ends — so organizers edit charts inside your CMS without a SeatLayer login each. The
embedded designer guide has the end-to-end flow.
How is a seat map designer different from a floor-plan or drawing tool?
A drawing tool produces a picture: shapes on a canvas that look like a room. A seat map designer produces a structured, versioned document in which every row, seat, table, booth, section, floor, price category and accessibility mark is an addressable object — which is what makes the same chart sellable. That structure is why one published revision can drive buyer selection, the optional 3D view, live inventory, the box office and reporting at once, and why changing the room is a new reviewed version rather than an edit underneath a running on-sale.
Does the designer have an API?
Yes, at two levels. Your backend uses a server-only sk_ credential to mint a short-lived dse_ Designer session; the browser receives only that origin-, workspace- and chart-scoped session. Published charts are addressed by the rest of the platform: a public buyer picker uses { event, publicKey } for direct public bootstrap, while a private audience replaces publicKey with a token provider. Separately, Designer MCP lets a compatible MCP client work through one authorized chart scope using deterministic tools, validation and review gates; permission, canonical revisions and publishing stay with SeatLayer and the person, and a session may publish only what it was explicitly permitted to.