Set a phone number's inbound processing Region using the REST API

Your phone number's webhook configuration is Region-specific and may vary between different Regions. Before making any changes to your phone number's call routing, it's a good idea to double-check the number's configuration in the specific Region that you plan to set the number's routing to.

To manage a phone number's configuration via Twilio Console, follow the instructions under the phone number section of our guide to managing Region-specific resources in the Console.

To inspect a phone number's configuration via the API, make a request to fetch the IncomingPhoneNumber resource in the target Region. Make sure that the request's FQDN targets the desired Region, and remember that the default FQDN of api.twilio.com defaults to the US1 Region.

For example, to check a phone number's configuration in the IE1 Region, you might make the following request using cURL or another HTTP client:

1
curl -u $API_KEY_SID:$API_KEY_SECRET \
2
  https://api.dublin.ie1.twilio.com/2010-04-01/Accounts/$ACCOUNT_SID/IncomingPhoneNumbers/$PHONE_NUMBER.json

Alternatively, you can issue these requests using a Twilio server-side SDK or the Twilio CLI. See the guide to using the REST API with Twilio Regions for more information.

If the phone number's configuration in the target Region is not correct, use the REST API or the Console to adjust the number's configuration in the target Region before proceeding.

To check the Region that your number is routed to, make a GET request to the Inbound Processing Region API.

1
curl -u $API_KEY_SID:$API_KEY_SECRET \
2
  https://routes.dublin.ie1.twilio.com/v2/PhoneNumbers/+16505551212

Look for the voice_region key in the response. This will indicate which Region your number's inbound voice calls will be routed to for processing.

To set the Region that your number is routed to, make a POST request to the Inbound Processing Region API with the VoiceRegion parameter.

In this example, the request sets the Region for inbound calls to IE1:

1
curl -u $API_KEY_SID:$API_KEY_SECRET \
2
  https://routes.dublin.ie1.twilio.com/v2/PhoneNumbers/+16505551212 \
3
  -d VoiceRegion=ie1

To demonstrate that calls to your phone number are being handled in the appropriate Region after a routing change, perform the following steps:

1. Place a call to your phone number from any phone.
2. Visit the phone number's Call Logs in the target Region.
3. Verify that you find a new Call Log that corresponds with your sample call from step 1.
4. Visit the phone number's Call Logs in a different, non-Active Region.
5. Verify that you do not find a Call Log that corresponds with your sample call.

Twilio routes inbound calls to your Twilio-powered SIP Trunks and SIP Domains using the same system as for phone numbers.

To manage routing for these resources types using the Inbound Processing Region API, adjust the request URL paths illustrated above as follows:

1. Replace the word PhoneNumbers with Trunk or SipDomain, depending on which resource type you are managing.
2. Replace the phone number in the path with the Trunk or Domain's full URI.

V3 includes support for setting the messaging region for a phone number or short code to Ireland (IE1) for EU SMS data residency. See the SMS Data Residency Guide to learn more about this feature.

1
{
2
  "phoneNumber": "+33123XXXXXX",
3
  "url": "https://routes.twilio.com/v3/PhoneNumbers/+33123XXXXXX",
4
  "voiceRegion": "ie1",
5
  "messagingRegion": "us1",
6
  "dateCreated": "2026-03-15T10:00:00Z",
7
  "dateUpdated": "2026-03-18T14:30:00Z"
8
}

The messaging and voice regions can be set independently, so you can choose to only update one at a time. Twilio recommends keeping voice and messaging regions aligned to ensure consistent behavior.

To specify a short code, add the relevant ISO 3166-2 country code to the path of the API endpoint URL: routes.twilio.com/v3/ShortCodes/{ISO_CODE}/{SHORT_CODE}