githubEdit

globeRegions

List available deployment regions

Regions define where your Spice apps are deployed. Each region is operated by a cloud provider (AWS, Azure, or Teraswitch).

List Regions

GET https://api.spice.ai/v1/regions

Returns a list of available regions where apps can be deployed.

Required scope: apps:read

Response

{
  "regions": [
    {
      "name": "US East (Ohio)",
      "region": "us-east-2",
      "cname": "us-east-2.spice.cloud",
      "provider": "aws",
      "providerName": "AWS"
    },
    {
      "name": "US West (Oregon)",
      "region": "us-west-2",
      "cname": "us-west-2.spice.cloud",
      "provider": "aws",
      "providerName": "AWS"
    }
  ],
  "default": "us-east-2"
}

Response Fields:

Field
Type
Description

name

string

Human-readable region name

region

string

Region identifier

cname

string

Region identifier used when creating apps

provider

string

Cloud provider (aws, azure, teraswitch)

providerName

string

Human-readable provider name

default

string

The default region identifier

Examples

cURL:

Response:

Python:

Node.js:

Using Regions

When creating an app, use the cname field from the regions response:

Region Selection

Consider these factors when selecting a region:

  • Latency: Choose a region close to your users or data sources

  • Compliance: Some regions may be required for data residency requirements

  • Availability: Check region availability for your plan tier

circle-info

The default region (us-east-2) is recommended for most use cases.

Last updated

Was this helpful?