Deprecation of region-specific Twilio API domain patterns

After April 28, these domains won't accept requests anymore. The api.us1.twilio.com domain will remain valid and continue to work. 

To keep everything running smoothly, update your applications to use {product}.twilio.com instead by April 28. Here's what to check and update:

• API base URLs: Review your application logic to remove the region segment from any hostnames. For example, replace api.ie1.twilio.com with api.twilio.com.

  • Note: This doesn’t apply to hostnames that include a city segment (api.{city}.{region}.twilio.com, such as api.dublin.ie1.twilio.com). These hostnames don't need to be changed.

• SDK initializations: See the Twilio API domain migration guide for detailed steps.

• Network configurations: Make sure that DNS allowlists, proxies, and firewall rules are updated to accept the new {product}.twilio.com domain.

If you need data processing primarily in a specific region (IE1 or AU1), continue to use api.{city}.{region}.twilio.com. This requires region-specific credentials and data migration. Our regional product and feature availability reference has more details.

Need a hand?

For more details on the Twilio API, check out these resources:

• Twilio API domain migration guide

• Regional product and feature availability reference

• Twilio regions

• Using the Twilio REST API in a non-US region

• Edge Locations