About
An independent guide to a deliberately confusing category.
Apple ships no iMessage API, a handful of services sell access to one anyway, and almost everything written about it is either vendor copy or a forum thread from 2019. This site is the resource we wanted when we first went looking.
Why this exists
The search results were bad
If you run a small business and go looking for “iMessage API”, you get three kinds of result. Vendor landing pages that will not tell you what anything costs or what it cannot do. Blog posts that are lightly rewritten vendor landing pages. And Stack Overflow threads about AppleScript from before half the current options existed.
None of them answer the questions an owner actually has. Is this legal. Will it break. What happens to my Android customers. What does it cost when I have four hundred people on a list. Who fixes it when it stops working on a Saturday.
So we wrote the answers down. 61 guides, 10 options compared honestly including the ones we recommend against, a UTM builder because attribution is the part everybody skips, and a compliance page because the rules are load-bearing and nobody enjoys reading about them.
What we are not
We do not sell a messaging product. We are not affiliated with Apple, and Apple does not endorse anything here. Apple and iMessage are trademarks of Apple Inc. The full position is in our terms of use, and what we collect is in the privacy policy.
How we work
Four rules we hold ourselves to
Comparison sites go bad in predictable ways. These are the guardrails against the ways we would go bad.
Say when we do not know
Provider capabilities change without notice. Where we cannot verify something, we mark it unknown and tell you to check — rather than guessing in a vendor's favour and letting you find out the hard way.
No prices we cannot keep current
Rates in this category move. A stale price on a comparison page costs you more than no price at all, so we describe pricing shape and link straight to the live page.
Recommend against things
Half of what we cover — self-hosted bridges, AppleScript, texting a cold list — we actively advise against for customer messaging. A guide that likes everything is a catalogue.
Write for the person who has to build it
Working code, real trade-offs, and the failure modes stated out loud. If a guide would not survive contact with a Tuesday afternoon, it is not finished.
How the comparison is built
Where the ratings come from
Capabilities come from each provider's own public documentation and product pages, read directly rather than summarised from elsewhere. Where a vendor states a capability plainly, we mark it supported. Where it is implied, inconsistent, or absent, we mark it partial or unknown.
Marketing claims — response-rate lifts, revenue multipliers — are reported as the vendor's claims, never as our findings. We have not independently reproduced anyone's numbers and we will say so rather than launder a statistic.
Trade-offs and recommendations are editorial: they are our judgement about what matters to a small business, and you are welcome to disagree. The reasoning is always stated so you can.
Corrections
Tell us when we are wrong
This category changes faster than most. Providers ship features, change pricing, and occasionally disappear. If something here is out of date or simply wrong, we would rather hear it from you than leave it up.
That goes double if you work at one of the providers we cover. If we have misrepresented what your product does, send the correction and the documentation and we will fix it.
Start where it makes sense
The business case, then the providers, then one message to your own phone.