Twilio iMessage Integration

Sendblue is a messaging platform that allows you to send iMessage and SMS on behalf of your business.

‍

Because iMessage is internet-based, all messages have a flat rate and aren't priced by segment. This means that the length of your message does not impact how much it costs to send, and you also don't need to deal with formatting issues on the receiving side.

‍

iMessage also has a much higher media size limit than SMS, which means you can send large files & high-res images (and videos) to your recipients, all for the same price as a single message.

If your number currently lives in Twilio, the messaging line needs to be ported to Sendblue before Sendblue can send iMessage, SMS, MMS, or RCS from that number. After the messaging port, Twilio can still be used for calling/voice on the line, but messaging cannot be split so Twilio sends SMS while Sendblue sends iMessages from the same number.

There are two clean ways to run the setup:

1. Sendblue-Managed Messaging - Sendblue handles iMessage, RCS, SMS, and MMS from the ported messaging line. Use this when you want one messaging provider and consistent inbound/outbound webhooks.
2. Voice on Twilio, messaging on Sendblue - Keep Twilio configured for calls while Sendblue owns the messaging route. This is the right way to preserve Twilio voice workflows without breaking iMessage/SMS routing.

Sendblue's managed messaging setup for teams coming from Twilio offers many benefits:

• Automatic messaging fallback: Sendblue can automatically choose iMessage, RCS, SMS, or MMS from the ported messaging line. You do not need to keep Twilio SMS active for Android fallback.
• MMS Support: Sendblue will send high-res images and videos to iMessage-capable phones, and will automatically compress & downgrade to MMS for non-iMessage phones.
• Keep Twilio for voice: If you already use Twilio for calling, you can keep that call workflow while Sendblue sends and receives messages. The same number can have voice with Twilio and messaging with Sendblue, but Twilio SMS and Sendblue iMessage cannot both own messaging on that number.
• Dynamic content: SMS messages cost more for every 160 characters you send. With Sendblue you can send one message to your iPhone contacts, and a different message to your SMS users. This allows you to save money by shortening your messages for SMS, but still provide a good customer experience.
• End-to-end encryption: All messages sent through Sendblue are end-to-end encrypted, meaning that your messages are safe from prying eyes. Only the sender (you) and the recipient (your user) can read the message.

Why should I use the Sendblue Twilio integration?

You may have already noticed this, but Twilio's delivery reporting is inaccurate, they might be reporting 95%, while only delivering 60%. That's because when an SMS is sent, it hops through tons of different networks/providers before reaching your recipient. This means that if one of those networks is down, or for whatever reason decides that your message should be marked as spam, your message will never reach your recipient. This is why SMS messages are so unreliable.

‍

On the other hand, iMessages have a much higher delivery rate. This is because iMessages are sent directly from your phone number to your recipient's phone, and are only ever routed through one network.

‍

Sendblue can increase your delivery rate by up to 400% based on our case studies. This means that you can send more messages to your users and reduce SMS friction for iPhone recipients. Basically: have your cake and eat it too.

‍

Can I use my Twilio phone number?

Yes, but the messaging line needs to be ported to Sendblue first. Sendblue cannot send iMessages from a number whose messaging route still lives at Twilio. After the messaging port is complete, you can keep Twilio for voice/calling while Sendblue handles iMessage, SMS, MMS, and RCS.

‍

What if I want iMessage and SMS on the same phone number?

With the Sendblue Dedicated plan, one phone number can handle iMessage, SMS, MMS, RCS, and phone calls. The messaging route should live with Sendblue; Twilio can remain configured for calls. You cannot split messaging so Twilio sends SMS while Sendblue sends iMessage from the same line.

‍

Will I receive the inbound Twilio SMS messages?

After the messaging line is ported to Sendblue, inbound SMS and iMessage replies are delivered through Sendblue webhooks. Twilio can still handle inbound calls if you keep voice configured there, but Twilio will not receive SMS for a line whose messaging has been moved to Sendblue.

‍

How to enable a Twilio voice + Sendblue messaging setup?

Reach out to the Sendblue team or start from your Sendblue dashboard. We will help you port the messaging line to Sendblue and keep your Twilio voice setup intact if you want to continue using Twilio for calls.

Choosing between Twilio and Sendblue depends on what kind of messaging your business actually needs. The table below breaks down the key differences across features, compliance, and deliverability.

The bottom line: Twilio is a solid SMS/MMS platform, but it cannot send iMessages. If your recipients are iPhone users — and in the U.S., roughly 60% of smartphone users are — you are leaving significant engagement on the table by using SMS alone. Sendblue lets you send iMessages to iPhone users while automatically falling back to RCS or SMS for everyone else, giving you the best of both worlds.

If you already have a Twilio-based messaging workflow, adding iMessage through Sendblue starts by moving the number's messaging route to Sendblue. The walkthrough below shows how to send messages through Sendblue while keeping Twilio available for calling/voice if you need it.

Step 1: Get Your Sendblue API Credentials

Sign up at sendblue.com/signup and grab your API key and secret from the API dashboard. You will have sandbox access immediately — no approval process required.

Step 2: Install the Sendblue SDK

For Node.js projects, install via npm:

npm install sendblue

For Python projects:

pip install sendblue

If you prefer raw HTTP requests, the REST API works with any language that can make POST requests.

Step 3: Initialize the Sendblue Client

Here is how to set up the client in Node.js (TypeScript):

import Sendblue from 'sendblue';

const sendblue = new Sendblue(
  process.env.SENDBLUE_API_KEY,
  process.env.SENDBLUE_API_SECRET
);

And in Python:

from sendblue import Sendblue

sendblue = Sendblue(
    api_key=os.environ['SENDBLUE_API_KEY'],
    api_secret=os.environ['SENDBLUE_API_SECRET']
)

Step 4: Send Your First iMessage

Sending an iMessage is a single API call. Node.js example:

const response = await sendblue.sendMessage({
  number: '+19998887777',
  content: 'Hey! Just following up on your inquiry.',
  sendStyle: 'celebration', // optional iMessage effect
  mediaUrl: 'https://example.com/brochure.pdf' // optional attachment
});

console.log(response.status); // 'QUEUED'

Python equivalent:

response = sendblue.send_message(
    number='+19998887777',
    content='Hey! Just following up on your inquiry.',
    send_style='celebration',
    media_url='https://example.com/brochure.pdf'
)

print(response.status)  # 'QUEUED'

Sendblue automatically detects whether the recipient has iMessage enabled. If they do, the message is delivered as a blue bubble iMessage. If not, it falls back to RCS first, then SMS from the ported messaging line — no extra routing logic needed on your end.

Step 5: Keep Twilio for Calls, Use Sendblue for Messaging

The supported pattern is to move the number's messaging route to Sendblue, then continue using Twilio for voice/calling if you need it. Do not send SMS from Twilio and iMessage from Sendblue on the same number; all messaging for that line should flow through Sendblue.

// Use Sendblue for outbound messaging from the ported line
const response = await sendblue.sendMessage({
  number: recipientPhone,
  content: messageBody
});

// Sendblue chooses iMessage, RCS, SMS, or MMS as needed.
console.log(response.status);

When you send through Sendblue, it automatically detects the recipient's device and chooses iMessage, RCS, SMS, or MMS accordingly. Keep your Twilio call handling separate on the voice side of the number.

Step 6: Set Up Webhooks for Inbound Messages

Configure your webhook URL in the Sendblue dashboard under Settings. When recipients reply, Sendblue sends a POST request to your endpoint with the following payload structure:

{
  "accountEmail": "you@yourcompany.com",
  "content": "Yes, I'd love to schedule a demo!",
  "is_outbound": false,
  "number": "+19998887777",
  "send_style": "invisible",
  "date_sent": "2026-02-11T10:30:00.000Z",
  "date_updated": "2026-02-11T10:30:00.000Z",
  "was_downgraded": false,
  "media_url": null,
  "message_type": "message",
  "group_id": null
}

Your webhook handler can then route this into your CRM, trigger automations, or feed it into an AI agent for intelligent auto-replies. Full webhook documentation is available at docs.sendblue.com.

Step 7: Send Contact Cards for Higher Trust

One of the most impactful things you can do after connecting is send a vCard (contact card) via the API. This is unique to Sendblue — no other iMessage API provider supports this. When the recipient saves the contact, your future messages show your business name instead of an unknown number:

await sendblue.sendMessage({
  number: '+19998887777',
  content: '',
  mediaUrl: 'https://yourdomain.com/contact.vcf'
});

This single step dramatically increases trust and long-term engagement with your contacts.

If you are interested in trying out Sendblue, you can book a demo anytime and we'll be happy to show you how it works!