Use TaskRouter with Twilio Regions
Public beta
TaskRouter 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 TaskRouter in IE1 generally available. Public beta features aren't covered by the Twilio Support Terms or Twilio Service Level Agreement.
TaskRouter 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 TaskRouter in Twilio's Ireland (IE1) Region for EU data residency. TaskRouter 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.
To use TaskRouter 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 Workspaces, TaskQueues, and Workers only exist 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 TaskRouter API requests to the dublin edge, using the following base URL.
Resource Base URL TaskRouter REST API taskrouter.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' });
If your application uses the TaskRouter JS SDK to build a Worker-facing UI, pass region: 'ie1' to both the Worker's Access Token and the Worker client. The JS SDK doesn't take an edge parameter — only region.
1const token = new AccessToken(accountSid, apiKeySid, apiKeySecret, {2identity: workerIdentity,3region: 'ie1',4});5token.addGrant(new AccessToken.TaskRouterGrant({ workerSid, workspaceSid, role: 'worker' }));
const worker = new Worker(token.toJwt(), { region: 'ie1' });
A Workspace that runs in IE1 can only reference TaskQueues, Tasks, Workers, and Workflows that also exist in IE1. You can't mix US1 and IE1 resources within a single Workflow.