Does Twilio support iMessage?

Building on the iMessage API? Build on iMessage with Flow: one agent for iMessage, WhatsApp and Telegram. New to it? Read the iMessage API guide.

Flow and Twilio side by side

The rows below answer the practical question: where Flow gives your agent iMessage, and where Twilio remains useful for SMS and voice.

Last checked: October 2026. Prices and features change, so check each provider’s own pages before you rely on a detail. “Check with the provider” means we did not find it stated.

1. Twilio Programmable Messaging docs
2. Twilio US SMS pricing
3. Twilio MCP docs

The direct answer

Twilio does not list iMessage as a channel. Its Programmable Messaging docs have quickstarts for SMS, RCS, WhatsApp and Facebook Messenger. iMessage is not among them. Twilio does list Apple Messages for Business as a private beta with a request-access form. That is Apple’s official business channel, where the customer starts the conversation. It is not the same as sending an iMessage to a phone number from your server. Apple Messages for Business vs iMessage API explains the difference.

So the answer for most developers is: keep Twilio for what it does well, and add an iMessage API for blue bubbles.

Why SMS and iMessage are different

An SMS goes over the phone carrier’s network. It reaches nearly any phone, but on an iPhone it shows as a green bubble, with no typing indicator, tapbacks or read receipts.

An iMessage goes over Apple’s service between Apple devices. That is where blue bubbles, tapbacks, typing indicators, effects and rich media come from. To send one from your server, you need a provider that runs iMessage lines. That is a different product from an SMS API, even when both have a similar REST call.

A2P 10DLC in plain terms

In the US, a business that sends texts from a normal 10-digit number must register with carriers. The program is called A2P 10DLC. Twilio’s docs say anyone sending SMS or MMS over a 10DLC number in the US must register, and that this includes individuals and hobbyists.

Registration takes time and adds fees, and it applies to SMS. Sendblue’s pricing page lists a $0 A2P registration fee. Check the current rules for your own use case before you build around either claim.

When SMS alone is enough

Twilio alone fits when:

• You need SMS, MMS or voice in many countries. Twilio is a broad platform built around phone numbers.
• You send alerts, codes or reminders and the look of the bubble does not matter.
• You need WhatsApp through the same vendor as SMS.
• You need a contractual SLA and mature server libraries.

If that is your whole list, you do not need an iMessage API.

When you need blue bubbles

Add an iMessage API when your users are mostly on iPhones, the conversation is two-way, and the experience matters. AI agents are the clear case: typing indicators, tapbacks and fast replies make an agent feel like a person texting.

Flow makes the decision simple: customers text your iMessage line, and the same conversation can continue over SMS or RCS when they cannot receive iMessage. Your agent stays on one API, with one set of webhooks, rules and tools.

Why Flow is the answer

Flow is the framework and messaging API for AI agents, and the way to put one on iMessage. Keep Twilio for voice and SMS in many countries if you need them. You write your product’s tools once and the same agent answers on iMessage, WhatsApp and Telegram, and works as an MCP server and CLI for ChatGPT, Claude and coding agents.

For this question, the useful parts are: one API across iMessage, WhatsApp and Telegram, SMS and RCS fallback from the same iMessage number, signed webhooks retried for three days, idempotent sends and a send gate that applies each channel’s rules for you. The pricing is by line and people a month, not per message, so a chatty agent costs the same. Put your agent on iMessage with Flow, free to start.

Frequently asked questions

Keep reading

All posts: the Flow blog. The Flow docs have the reference.