FAQ
Straight answers, including the awkward ones.
The questions people actually ask about this category — including whether it is legal, whether Apple could shut it down, and whether you should bother at all.
The basics
Is there an official iMessage API from Apple?
No. Apple has never published a public API, SDK, or developer programme for sending iMessages. The closest sanctioned thing is Apple Messages for Business, which is customer-initiated support messaging routed through approved partners — it cannot send an outbound reminder to a list. How it works covers the detail.
Then how do services like Sendblue and Miss Blue do it?
They operate the Apple-side sending infrastructure themselves and put a conventional REST API in front of it. You send JSON to an HTTPS endpoint; they handle everything on the Apple side. From your codebase it behaves like any other messaging API. See the provider comparison.
Will my messages actually arrive as blue bubbles?
To recipients who use iMessage, yes. To everyone else — Android users, and iPhone users with iMessage disabled — a good provider falls back to SMS automatically, which arrives green. One send call, two delivery paths. Blue vs green explains what changes between them.
What happens to my Android customers?
They receive SMS, in the same thread, and they will not notice anything unusual. This is why SMS fallback is the single most important feature to confirm before choosing a provider — roughly half your list depends on it.
Legality and risk
Is using a third-party iMessage API legal?
Using these services is not itself illegal, and businesses use them openly. What you do have to get right is messaging law — consent, opt-outs, timing — which applies to any channel. That part is not optional and the penalties are per message. See compliance.
Could Apple shut these services down?
It is a real risk and you should plan for it. Apple has not sanctioned this category, and the technical arrangements these services rely on are theirs to change. Keep your customer list, your consent records and your opt-out state in systems you own, so switching providers is an inconvenience rather than a catastrophe.
Is running my own Mac bridge safer?
No — it is riskier in the ways that matter to a business. It uses a consumer Apple Account in a manner that conflicts with Apple's terms, sends from a personal number, has no SMS fallback, and fails when macOS updates. The full comparison makes the case properly.
Do I need consent to text my existing customers?
For transactional messages they are expecting — an appointment reminder, an order confirmation — express consent is generally enough. For marketing, US rules require express written consent that you can prove, and an existing business relationship does not count. Getting consent right has the operational detail.
Cost and setup
What does it cost?
Typically a monthly platform fee per number plus per-message usage. iMessage sends carry no carrier fee; SMS fallback does. We deliberately do not publish specific rates here because they change often and a stale number would cost you more than no number — check each provider's live pricing page. How to model it.
How long does it take to set up?
A first delivered message takes under an hour with a hosted provider. A production setup — inbound webhooks, opt-out handling, consent records and link tagging — is roughly a day for a competent developer. Send your first message.
Can I use my existing business phone number?
Sometimes, depending on the provider and the number. Ask before you sign up, and ask about porting out as well — the number is the one thing that is genuinely hard to move later, because your customers save it. Choosing your stack covers the questions to ask.
Do I need a developer?
For an API integration, yes. Some providers also ship a shared inbox your front desk can use with no code at all, which is a reasonable way to start before you build anything.
Tracking and results
Why does my analytics show text traffic as direct?
Links tapped inside Messages generally pass no referrer, so analytics has nothing to attribute the visit to. UTM parameters are the fix and they are the only fix. Build one in the UTM builder.
Should utm_source be the provider name?
No — use imessage. Source should describe the channel, not the vendor, so your historical data stays comparable if you switch providers. Keep utm_medium as sms so iMessage and SMS fallback aggregate into one number.
How do I know if it actually made money?
Withhold the message from a random 10% and compare completion rates. The gap is your real effect — everything else is measuring habits your customers already had. Measuring ROI has the method.
Why did some messages never arrive?
Almost always carrier filtering on the SMS side, which is silent — the API returns success and the message is dropped. Public link shorteners are the most common trigger. Shorteners and spam filters covers how to avoid it.
About this site
Do you sell an iMessage API?
No. We do not sell a messaging product and we are not affiliated with Apple or with any provider listed here. This site exists to explain a confusing category honestly. More about us.
How do you decide what goes in the comparison?
We list the options a small business is realistically going to encounter, including the free and self-hosted ones we advise against. Where we cannot verify a capability we mark it unknown rather than guessing in a vendor's favour.
Something here is out of date. Can you fix it?
Please tell us — this category moves quickly and provider capabilities change without notice. Send us a correction and we will update it.
Still stuck on something?
Tell us what you are trying to send and we will tell you the shortest route to it — including when the answer is that you do not need iMessage for this at all.