Contact sales Start for free
Contact sales Start for free

Hello, Ireland! Sending SMS in Twilio’s Ireland Region

Time to read:

August 18, 2026
Written by
Gary Spencer
Twilion
Reviewed by
Bill Higbee
Twilion
Paul Kamp
Twilion

Hello, Ireland! Sending SMS in Twilio’s Ireland Region

Have you thought about moving your Programmable SMS workloads to Twilio’s Ireland region (IE1) within the EU to meet your data residency desires? You are not alone! Since we announced in June that Data Residency in the EU is generally available, customers that I work with have been moving their traffic onto the IE1 region. And did I mention that there are no additional costs?

Using Programmable Messaging in IE1 means that the storage and processing of personal data in the SMS messages that you send to your customers, including end user phone numbers and message bodies, stays in the EU all the way to the supplier edge. If your business has data residency requirements, or simply prefers to keep that data within the EU, then this API is for you.

But what does adopting IE1 mean for your code? Not much - and I’ll show you. Let’s build…

Be aware that today SMS messages to and from numbers with +1 prefixes are not currently supported through the IE1 region. Additionally, RCS and WhatsApp are not currently supported. Learn more here, and keep your eyes on the Twilio Changelog for future enhancement releases.

Get your IE1 credentials

Twilio accounts themselves are singletons - you do not need a separate account to use IE1. What you will need is a separate Auth Token, or separate API key and secret to make the calls. You can create those here in the Twilio Console.

Create an IE1 Messaging Service

A Messaging Service is a container that groups your senders, handles compliance, enables messaging features, and controls what happens when somebody replies to a message. You do not have to use a Messaging Service, but it is a good idea to do so.

Messaging Services are available in IE1, and you can create one here. You cannot use your US1 Messaging Services in IE1.

Call the API

Now that you have your credentials and your Messaging Service, you are ready to send a message!

Here is how to send an SMS using cURL with a Messaging Service:

curl --request POST \
  --url https://api.dublin.ie1.twilio.com/2010-04-01/Accounts/AC1234xxxx/Messages.json \
  --header 'Authorization: Basic xxxx' \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data 'Body=Hello, Ireland!' \
  --data 'To=+447832690000' \
  --data MessagingServiceSid=MG1234xxxx
  --data From=TwilioHarp

The only difference in the API call (credentials and Messaging Service aside) is the hostname - instead of api.twilio.com, you are calling api.dublin.ie1.twilio.com. The response that you get and the way that you construct the call is still exactly the same.

Using one of our Client SDKs? The change is even more straightforward. You just need to switch the region from us1 to ie1 when you set up the Client. Let us take Python as an example, where today you might be using us1:

#SMS from US1
client = Client(
    ie1_api_key_sid,
    ie1_api_key_secret,
    account_sid=account_sid,
    region="us1",
    edge="dublin"
)
message = client.messages.create(
    body="Ahoy from US1!",
    from_=TwilioHarp,
    to=+447832690000
)

Here, I am using Twilio’s processing and storage region in the US, and am entering the Twilio backbone using the Dublin edge. You can use any edge to get into any of Twilio’s regions.

To have that same message be processed and stored in Ireland, all I have to do is switch out that region identifier.

 

#SMS from IE1
client = Client(
    ie1_api_key_sid,
    ie1_api_key_secret,
    account_sid=account_sid,
    region="ie1",
    edge="dublin"
)
message = client.messages.create(
    body="Ahoy from IE1!",
    from_=TwilioHarp,
    to=+447832690000
)

Switching the region is only a matter of changing the region parameter.

It worked! But how do I know this got processed in IE1?

I get it, you need more confirmation – since you may know us as a company who rickrolls people.

Twilio has a filter in your logs so you can be certain of the region they were sent from and processed. Here is a direct link to view your IE1 SMS logs. Or, from the sidebar, click on Messaging -> Logs -> click on the region, and voilà!

Screenshot of Twilio Programmable Messaging Logs interface showing message details and status.

Congratulations, you are sending your messages in Twilio’s IE1 region!

What is next?

Our engineering team is hard at work bringing new capabilities to the platform across all of our regions. One initiative you might find exciting is our effort to enable Studio and TaskRouter in IE1.

Studio is Twilio’s low/no code visual workflow builder that lets you design, build, and manage communication apps like chatbots, surveys, and automated alerts.

TaskRouter is a skills/attributes based routing system that matches incoming tasks (like messages) to the best worker to take on the task.

Want more information?

Thanks for reading, we can’t wait to see what you build in IE1!

Gary Spencer is a Presales Architect working at Twilio, based in London. Gary has over ten years of experience in customer-facing technology roles, helping businesses design and build solutions using APIs. Feel free to reach out to him at linkedin.com/in/gspncr

Related Posts

Related Resources

A newspaper article

Twilio Docs

From APIs to SDKs to sample apps

API reference documentation, SDKs, helper libraries, quickstarts, and tutorials for your language and platform.
An Open book

Resource Center

The latest ebooks, industry reports, and webinars

Learn from customer engagement experts to improve your own communication.
User group reactions

Ahoy

Twilio's developer community hub

Best practices, code samples, and inspiration to build communications and digital engagement experiences.