Concepts

SeatMap separates venue ownership, map publication, event lifecycle, channel access, and live inventory so each transition can be checked independently.

Venue and map

A venue contains one or more maps. Draft revisions are editable; a published version is the immutable layout referenced by an event occurrence.

Occurrence and listing

An occurrence schedules a published map at a venue. A channel listing grants a workspace permission to sell that occurrence and has its own lifecycle.

Seat inventory

Availability is projected for fast reads. Holds, allocations, reservations, sales, blocks, and releases change seat state through backend-controlled operations.

Realtime state

The SDK synchronizes a snapshot before applying realtime changes. It reports recovering, degraded, and terminal states instead of presenting stale availability as ready.