---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/global-infrastructure/studio-with-twilio-regions#article
headline: Use Studio with Twilio Regions
description: Learn how Studio works in Twilio's Ireland (IE1) Region for EU data residency, including widget support, credentials, and API endpoints.
url: https://www.twilio.com/docs/global-infrastructure/studio-with-twilio-regions
inLanguage: en
dateModified: 2026-10-06T20:49:51.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# Use Studio with Twilio Regions

> \[!IMPORTANT]
>
> 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][].

## Widget support

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.

## Trigger support

Studio flows in IE1 can't be triggered by inbound SMS. For more information, see [Messaging IE1 Feature Availability][].

## Configure your account for IE1

To use Studio in IE1, complete the following steps.

1. 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.
2. 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][].
   1. In the Console, go to **API keys & tokens**.
   2. Change the region selector to Ireland (IE1).
   3. Find your IE1 Auth Token.
   4. Create API keys with the Console region selector set to Ireland (IE1). Any keys you create only work in IE1.
3. 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.

   ```bash
   twilio login --region ie1 --edge dublin
   ```

   Using a Twilio helper library, pass both the region and the edge when you create the client. In Node.js:

   ```javascript
   const client = require('twilio')(accountSid, authToken, { region: 'ie1', edge: 'dublin' });
   ```

## Keep flows and their resources in the same Region

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.

[Connect Virtual Agent]: /docs/studio/widget-library/connect-virtual-agent

[Create or Update Profile]: /docs/studio/widget-library/create-or-update-profile

[Manage Regional API Credentials]: /docs/global-infrastructure/manage-regional-api-credentials

[Messaging IE1 Feature Availability]: /docs/global-infrastructure/messaging-eu-feature-availability

[Regional product and feature availability]: /docs/global-infrastructure/regional-product-and-feature-availability

[Resolve Profile]: /docs/studio/widget-library/resolve-profile

[Send to Flex]: /docs/studio/widget-library/send-flex

[Studio widget library]: /docs/studio/widget-library

[Use the Conversations API with Twilio Regions]: /docs/global-infrastructure/conversations-api-with-twilio-regions