API · SDK · runtime · authentication lifecycle intelligence

Last updated · 9 September 2026

SchemaTrace

Breaking changes, enforcement dates and migration requirements.

ST-2026-087 · API endpoints & versions

Twilio deprecates legacy region-specific API domain patterns

Twilio deprecated seven regional API domain patterns and directs applications, SDK initialisation and network allowlists to api.twilio.com.

Twilio APIregional domainsapi.twilio.comdeprecation

Previous state

Applications could use api.ie1.twilio.com, api.au1.twilio.com, api.br1.twilio.com, api.de1.twilio.com, api.jp1.twilio.com, api.sg1.twilio.com or api.us2.twilio.com as regional API domains.

Current state

Those regional patterns are deprecated and Twilio directs callers to api.twilio.com, with the migration path determined by data-processing requirements.

Who needs to care

Twilio integrations with regional API base URLs, regional SDK initialisation or DNS, proxy and firewall rules tied to the deprecated hosts.

What to do

Follow the Twilio API Domain Migration Guide, update API and SDK configuration and permit api.twilio.com in network controls.

What the source does not prove

Twilio states that deprecation starts on 28 April 2026 but does not publish a universal final shutdown date in this notice. Regional processing requirements still affect the migration path.

Lifecycle history

Dated event sequence

  1. Deprecation announced

    Twilio listed the seven affected regional domains and the api.twilio.com replacement.

  2. Deprecation began

    The legacy region-specific domain patterns entered deprecation.

Evidence ledger

First-party sources

  1. 01
    Twilio Changelog — Deprecation of legacy Twilio API domain patterns

    Official API-domain deprecation and migration notice · 2026-02-04

    Open official source ↗