Skip to content
iMessage APIs
All answers

Apple's position

Why do developers say the iMessage API is not official?

Because it is not. Apple publishes no iMessage API and licenses no wholesale access, so every commercial provider reaches iMessage by operating Apple accounts and devices in ways Apple's terms do not contemplate. The correction is accurate. The conclusion sometimes drawn from it — that the providers are scams — is not: they are real companies whose messages genuinely arrive.

What the criticism gets right

  • There is no official API, and no vendor's enterprise language changes that.
  • The infrastructure is Apple devices and Apple identities, however it is described on a pricing page. What is actually behind your number.
  • Lines can be flagged and stop delivering, usually after volume is ramped too fast or messages are identical and cold.
  • Deliverability is something you manage, not something you buy.

What it gets wrong

That unofficial means fraudulent. These are real businesses running real infrastructure, some for years, and the blue bubbles genuinely arrive. What is true is that the risk sits somewhere unusual: with the provider, in a contractual grey area with Apple, rather than with you in a legal one.

Two questions people collapse into one

Messaging law — consent, quiet hours, honouring opt-outs — applies exactly as it does to SMS and carries statutory damages. That is your problem and you should take it seriously. Apple's terms are a contract question between the provider and Apple. Different questions, different exposure. The legal overview.

The sensible posture

Use it, and do not depend on it exclusively. Customer records in your own systems, a tested fallback channel, and monitoring on delivered rate rather than API uptime. Then the failure mode is a channel you lose, not a business you cannot operate. The full community view, theme by theme.