Using the Twilio REST API in a non-US Region
This guide shows you how to manage resources in your target Twilio Region by using Twilio's REST API. By the end of the guide, you'll learn to:
- Select a target Region for API requests
- Authenticate requests with Region-specific credentials
- Interact with Region-specific resources by using the REST API
- Select a target Region in Twilio SDKs
This guide uses cURL examples instead of language-specific SDKs to highlight core REST API principles without higher-level abstractions.
Action required by April 28, 2026
We are making changes to the PRODUCT.REGION.twilio.com domain pattern. The following domains will stop working on April 28, 2026: api.ie1.twilio.com, api.au1.twilio.com, api.br1.twilio.com, api.de1.twilio.com, api.jp1.twilio.com, api.sg1.twilio.com, and api.us2.twilio.com.
Note: api.us1.twilio.com remains valid.
See the API domain migration guide for migration instructions.
The Twilio REST API operates on a per-region basis. When making requests to the API, it's up to you to select which Region will handle the request. Whichever Region you choose will be the Region that processes and stores data related to the request.
If you don't specify a target Region, Twilio handles the request in the default US1 Region.
To specify a target Region for a request, include the name of the target Region in the request's hostname, also known as the fully qualified domain name (FQDN).
The FQDN format follows a convention that encodes three pieces of information in the hostname:
- The Twilio Product
- The target Edge Location
- The target Region
An FQDN has the following format:
{product}.{edge-location}.{region}.twilio.com
Some example FQDNs targeting API products in different Regions (through various Edge Locations) include:
| FQDN | Target Region |
|---|---|
| api.sydney.au1.twilio.com | Australia (AU1) Region |
| voice.ashburn.us1.twilio.com | United States (US1) Region |
| insights.dublin.ie1.twilio.com | Ireland (IE1) Region (not yet available) |
Info
Understanding Edge Locations and Region Processing
The edge location portion (e.g., sydney, dublin, ashburn) in the FQDN is optional and ignored for routing—Twilio's CDN automatically selects the optimal ingress path based on your geographic location and network conditions. However, when specified, the edge and region combination (e.g., sydney.au1) determines where your data is processed. You control the processing region (ie1, au1, us1), but the CDN determines where your traffic enters Twilio's network.
To learn more about how ingress and region processing work, see Understanding Edge Locations.
When making requests using any of Twilio's server-side SDKs, you don't need to worry about constructing an FQDN. Instead, provide the client constructor with an edge and region parameter, and the client will construct the FQDN accordingly.
Always specify both edge and region
When specifying a region parameter for an SDK client, be sure to also specify the edge parameter. For backward compatibility purposes, specifying a region without specifying an edge will result in requests being routed to US1.
In order to provide Region-specific access control, Twilio manages your account's API credentials on a per-region basis. This means that you'll need to use different Auth Tokens and API Keys based on which Region you are sending API requests to. Refer to the Twilio Regions overview for more information about the Region isolation model.
You can manage API Keys for a Region using the Twilio Console or the REST API. See our guide to managing Regional API credentials for complete instructions.
Most Twilio resources can be managed via REST API in a target Region using standard API Keys which exist in the Region.
For example, to list your account's TwiML Applications in the AU1 region using cURL (again with the appropriate environment variables present in your shell):
1curl -u $API_KEY_SID:$API_KEY_SECRET \2https://api.sydney.au1.twilio.com/2010-04-01/Accounts/$ACCOUNT_SID/Applications.json
Warning
Some API endpoints aren't available in Regions outside of US1.
For example, REST API operations that manage Push Credentials for the Notification service are supported only in US1.
To learn more about building with Twilio's global infrastructure, see Make an outbound call using the Twilio REST API in a non-US Region.