The basics
What is an iMessage API?
An iMessage API is a service your software can call to send and receive real iMessages. Apple does not offer one, so every commercial iMessage API is run by a third party that operates genuine Apple accounts and devices at scale and exposes them through a REST interface. You send an HTTP request with a phone number and a message; the recipient gets a blue bubble from a number assigned to you.
The one-request version
curl --request POST 'https://api.sendblue.co/api/send-message' \
--header 'sb-api-key-id: YOUR_KEY_ID' \
--header 'sb-api-secret-key: YOUR_SECRET' \
--header 'Content-Type: application/json' \
--data-raw '{
"number": "+19998887777",
"content": "Your 2pm window is confirmed.",
"status_callback": "https://acme.co/webhooks/imessage"
}'Sendblue's documented request shape. Field names differ by provider; the structure does not.
What comes back
- Synchronously: a message handle and an accepted status. Not a delivery confirmation — nothing has reached a phone yet.
- Asynchronously to your callback: sent, delivered, read, failed, and inbound replies.
- The distinction matters. Counting the 200 response as a delivery is the most common measurement error in this category.
Verify the callback before you trust it
Your webhook URL is public and guessable. Compute the HMAC over the raw request bytes before any body parser touches them — verifying against re-serialized JSON fails every time and looks like a wrong secret. The full inbound guide.
What you are actually buying
- A phone number that sends and receives as a blue bubble.
- Delivery events — sent, delivered, read — pushed to your endpoint.
- Inbound replies as webhooks, so a customer's answer reaches your application.
- iMessage-native features: typing indicators, tapback reactions, full-quality photos.
- SMS or RCS fallback on most providers, for recipients not on iMessage.
Why it is priced per line, not per message
Because there is physical Apple infrastructure behind every number. The line is the scarce resource, so once you have one, an extra message costs the provider almost nothing. That is why a business sending 400 messages a month pays roughly what one sending 4,000 pays — and why nothing here is unlimited. The full pricing picture.
The three routes, ranked by how long they keep working
| Route | Setup | Survives production? | Cost |
|---|---|---|---|
| Third-party REST provider | About an hour | Yes — this is what the category is for | $20–$250/line/month |
| Self-hosted bridge on your Mac | An afternoon | Personal projects only | Free, plus your uptime |
| Apple Messages for Business | Weeks to months | Yes, but inbound-only | Via a CSP contract |
| AppleScript on a Mac | Minutes | No delivery signal, no replies | Free |
If you need to send the first message — a reminder, a follow-up, an alert — only the first two rows can do it, and only the first is business infrastructure. The full comparison with working code.
Who does
| Provider | Entry price | Notable for |
|---|---|---|
| Sendblue | $100/line/month | Public docs, automatic SMS and RCS fallback |
| LoopMessage | $20/month shared | Cheapest real entry point |
| Blooio | $195/line promotional | Publishes an OpenAPI specification |
| Miss Blue | $78/month shared | Shared team inbox is the product |
| Tuco AI | $149/month + setup | CRM-native, they do the wiring |
| Linq | Quote only | SOC 2 Type II, uptime SLA |
| Photon | $0 / $25 / $250 | Agent-first, publishes prices |
Who does not, despite the searches
Twilio and Telnyx sell SMS, MMS, RCS and WhatsApp but not iMessage — there is no wholesale door for them to buy through. Blinq, Popl, Mobilo, HiHello and Switchit are digital business card companies whose APIs sync contacts to a CRM. Linq is the one company in that competitive set that genuinely became an iMessage vendor, which is where the confusion comes from.
The full directory, sorted by how much we actually know about each.
The part vendors do not lead with
Apple has never sanctioned this. Providers reach iMessage by means Apple's terms do not contemplate, which means a line can be flagged and stop delivering. The category has operated for years and providers manage that risk professionally, but the sensible posture is to treat iMessage as your best channel rather than your only one — here is the honest version of that risk.
This page also answers
- api imessage
- api for imessage
- imessage third-party post api
Further reading
Go deeper
What is an iMessage API?
What these services actually are, how they send a blue bubble without Apple's involvement, what you get for the money, and what you are trusting when you buy one.
7 min readComparisonsBest iMessage API in 2026
Sendblue, Miss Blue, LoopMessage, Blooio and Tuco AI, compared on price, capability and who each one actually suits. Including which to avoid for cold outreach.
12 min readOperationsiMessage from Node.js
A working Node.js integration: a typed client, webhook verification with Express, retries that respect rate limits, and a send queue that will not get your line flagged.
12 min read