Choose a SeatLayer Event Region

Choose one of 11 provider-neutral regions for low-latency live Event inventory, with workspace defaults and per-Event overrides.

SeatLayer supports exactly 11 Event regions. Choose the region nearest the venue. If buyers are concentrated somewhere else, choose the region containing the largest expected buyer audience.

This is a latency preference for live Event inventory. It is not a guarantee that all account, payment, analytics, or backup data stays in that region.

API value	Region	Typical venues or audiences
`western-europe`	Western Europe	Netherlands, Belgium, UK, Ireland, France, Germany, Spain, Italy, Nordics
`eastern-europe`	Eastern Europe	Poland, Czechia, Hungary, Romania, Balkans, Baltics, Ukraine
`north-america-east`	Eastern North America	Eastern and central US or Canada, Caribbean
`north-america-west`	Western North America	Western US or Canada, Mexico
`south-america`	South America	Brazil, Argentina, Chile, Colombia
`asia-pacific`	Asia Pacific	India, Pakistan, Bangladesh, Sri Lanka, or a broadly distributed Asia-Pacific audience
`northeast-asia`	Northeast Asia	Japan, South Korea, Taiwan
`southeast-asia`	Southeast Asia	Singapore, Malaysia, Indonesia, Thailand, Vietnam, Philippines
`oceania`	Oceania	Australia, New Zealand, Pacific islands
`africa`	Africa	African venues
`middle-east`	Middle East	UAE, Saudi Arabia, Qatar, Kuwait, Bahrain, Oman

Resolution order

For a new Event, SeatLayer resolves the region in this order:

the Event request’s region;
the chart workspace’s defaultRegion; and
the platform fallback, western-europe.

During signup, SeatLayer can recommend a workspace default from approximate request geography. The organizer sees and confirms the choice. A manual choice wins, and later workspace creation asks again. The location estimate is not stored as an Event region unless the organizer confirms it.

workspace-and-event.jsonjson

{
  "workspace": { "name": "Rotterdam Events", "defaultRegion": "western-europe" },
  "event": {
    "chartId": "chart_abc",
    "name": "Rotterdam Night",
    "region": "western-europe",
    "currency": "EUR"
  }
}

Region and currency are independent. An India Event can use "region": "asia-pacific" with "currency": "INR"; a Rotterdam Event can use "region": "western-europe" with "currency": "EUR".

Server SDK fields

The optional field names in the 0.8.0 SDKs are:

SDK	Workspace default	Event override
Node.js	`workspaces.create({ name, defaultRegion })`	`events.create({ chartId, region })`
Python	`workspaces.create(name, default_region=...)`	`events.create(chart_id, region=...)`
PHP	`workspaces->create($name, defaultRegion: ...)`	`events->create($chartId, region: ...)`
Java	`workspaces().create(name, region)`	put `region` in the `events().create(...)` map
Go	`WorkspaceCreateParams.DefaultRegion`	`EventCreateParams.Region`
Ruby	`workspaces.create(name:, default_region: ...)`	`events.create(chart_id:, region: ...)`
.NET	`Workspaces.CreateAsync(..., defaultRegion: ...)`	`EventCreateRequest.Region`

Omit the Event override to inherit the workspace default. In languages with typed region constants, prefer those constants over hand-written strings. The wire values remain the 11 API values in the table above; provider or data-center codes are not accepted.

Immutability and retries

The chosen region is frozen when Event inventory is first created. Changing a workspace default affects only later Events. Event update requests cannot move an existing Event. Reuse the same idempotency key and exact request body when a create response is lost; SeatLayer reuses the originally resolved region.

Events created before this field was introduced can return region: null. Do not infer or display a region for those legacy Events. An unknown value, including any infrastructure-specific alias, returns 422 invalid_region.

Continue to Events, Workspaces, and Seasons.