All data in your account (charts, events, object statuses...) is stored within a geographical region. You can choose it when signing up. It's important to pick the region closest to you, to reduce API call latency.
Europe (Dublin - Ireland)
North-America (Iowa - USA)
South-America (São Paulo - Brasil)
Oceania (Sydney - Australia)
To see your region, go to the company settings page.
Migrating your account to a different region
Accounts created before March 12th, 2021 are stored in Europe. We can migrate your data to an other region if you wish. This will lead to some downtime, so make sure to migrate outside of business hours. Please contact email@example.com for more info.
Before the migration
Make sure you're using the latest version of our API client libraries. You'll need to pass in a region, which for now is EU.
Then, please get in touch to schedule the migration. We'll give you an estimate as to how long your account will be unavailable while migrating.
During the migration
The migration happens in 3 phases:
Non-event data is copied (charts, workspaces, users)
You cannot create new charts, events, workspaces or users. However, ticket buyers can still render charts and book seats.
Event data is copied
Your account is completely read-only. Charts still render (unless you've enabled hold-on-select), but bookings fail. Also, you still cannot create new charts, events, workspaces or users.
Status changes are copied
Almost everything is back to normal: ticket buyers can see charts and book seats. You can create new charts, events, workspaces and users. The only thing that doesn't work is retrieving status changes through our API.
So as far as ticket buyers are concerned, seats.io will only be 'down' in phase 2.
After the migration
You need to switch to the new region in a couple of places:
Chart renderer: use a regional CDN url.
Event manager (if you're embedding it in your site): use a regional CDN url.
Chart designer (if you're embedding it in your site): use a regional CDN url.
Chart manager (if you're embedding it in your site): use a regional CDN url.
As long as you don't change the region in your API client (or you don't change the CDN url), our European server will forward requests to your new region. E.g. if you migrated to North America, you'll be calling our European server, which forwards the request and sends the response back.
That requires an extra round-trip between Europe and North-America, so it's important that you switch regions in the API client and CDN as soon as possible.