Base URLs and regions

Where each Tanqory API lives — and how to resolve your store's regional base URL.

Tanqory exposes three APIs. Two sit on fixed global hosts; the Store API is deployed per store, in the cloud region you provisioned it in, so its base URL is resolved per store rather than fixed.

The three services

API	Base URL	Notes
Admin	`https://api.tanqory.com`	Auth, stores, billing, domains. One global host.
AI	`https://ai.tanqory.com`	Chat, RAG, embeddings, agents. One global host.
Store	per-store regional pod	Products, orders, themes, analytics. Resolved per store — see below.

Store base URLs are per-region

Each store runs in a specific cloud provider + region that you chose when the store was created. Its data lives there (a data-residency decision), and its API is served from a matching regional host of the form:

https://api-{provider}-{region}.tanqory.com

For example, a DigitalOcean Singapore store is served from https://api-do-sgp1.tanqory.com. The Store API contract is identical across every region — only the host differs.

Don't hard-code or hand-build a store's host. Region naming can change; resolve the base URL from the store's record instead (next section). The host pattern above is for understanding, not for string-building in production code.

Resolve your store's base URL

The Admin API is the source of truth for where a store lives. Read the store record and use its cloud provider + region (the platform is adding a ready apiBaseUrl field — prefer it once available):

# Admin API — always api.tanqory.com
curl https://api.tanqory.com/api/v1/stores/STORE_ID \
  -H "Authorization: Bearer $TANQORY_API_KEY"
# → use the store's provider + region to address the Store API host

Then call the Store API at that regional host with the same Bearer token.

Available regions

Stores can be provisioned in any of these regions, across three clouds:

Provider	Regions
DigitalOcean	`sgp1` · `fra1` · `nyc3` · `sfo3` · `lon1` · `ams3` · `tor1` · `blr1`
AWS	`ap-southeast-1` · `ap-northeast-1` · `eu-west-1` · `eu-central-1` · `us-east-1` · `us-west-2`
Google Cloud	`asia-northeast1` · `asia-southeast1` · `europe-west1` · `europe-west4` · `us-west1` · `us-central1` · `us-east1`

Data residency. A store's data stays in its region. Choose the region closest to your customers (latency) and aligned with your compliance needs. A store does not move regions after creation.

Next steps

Topic	When to read it
Quickstart	Make your first authenticated call.
Authentication	The same Bearer token works across all three APIs.
Store API	The full Store reference (resolve the host as above).