Use Studio with Twilio Regions
Public beta
Studio in IE1, including the API, is available as a public beta release, and the information on this page is subject to change. Some features are not yet implemented, and others may change before Twilio declares Studio in IE1 generally available. Public beta features aren't covered by the Twilio Support Terms or Twilio Service Level Agreement.
Studio in IE1 is not PCI compliant or a HIPAA Eligible Service and should not be used in workflows that are subject to HIPAA or PCI.
You can use Studio in Twilio's Ireland (IE1) Region for EU data residency. Studio in IE1 works the same way it does in US1, with the differences called out on this page. For the complete list of Twilio Regions and product availability, see Regional product and feature availability.
Every widget in the Studio widget library works the same way in IE1 as it does in US1, with four exceptions:
| Widget | Available in IE1 | Related unsupported feature |
|---|---|---|
| Send to Flex | No | Flex ^1 |
| Connect Virtual Agent | No | <VirtualAgent> TwiML noun |
| Resolve Profile, Create or Update Profile | No | Twilio Profiles ^1 |
| Incoming Conversation (classic) trigger | No | Studio's webhook integration with Conversations (classic) ^2 |
^1: See Regional product and feature availability for the current list of IE1-supported products
^2: See Use the Conversations API with Twilio Regions. Conversations (classic) in IE1 only supports the Chat channel. SMS, WhatsApp, and Facebook Messenger aren't supported.
Studio flows in IE1 can't be triggered by inbound SMS. For more information, see Messaging IE1 Feature Availability.
To use Studio in IE1, complete the following steps.
-
In the Twilio Console, use the region selector to switch to Ireland (IE1). When you set the Console to the IE1 region, created Flows only run in IE1.
-
Use Region-specific credentials. Twilio isolates its Regions. When you target IE1, a US1 Auth Token or API key doesn't work. To learn more, see Manage Regional API Credentials.
- In the Console, go to API keys & tokens.
- Change the region selector to Ireland (IE1).
- Find your IE1 Auth Token.
- Create API keys with the Console region selector set to Ireland (IE1). Any keys you create only work in IE1.
-
Send Studio API requests to the dublin edge, using the following base URL.
Resource Base URL Studio REST API studio.dublin.ie1.twilio.com Using the Twilio CLI, sign in with the IE1 region and the dublin edge.
twilio login --region ie1 --edge dublinUsing a Twilio helper library, pass both the region and the edge when you create the client. In Node.js:
const client = require('twilio')(accountSid, authToken, { region: 'ie1', edge: 'dublin' });
A flow that runs in IE1 can only reference resources that also exist in IE1. A widget that points to Voice, Messaging, Functions, or another resource that exists only in US1 doesn't work when the flow runs in IE1.