Skip to content
iMessage APIs
All answers

Apple's position

Where is the iMessage API documentation?

Apple's Messages documentation covers building iMessage apps and does not include a send endpoint. For a working API reference you need a third-party provider: Sendblue, Blooio and LoopMessage publish theirs openly, Blooio ships an OpenAPI specification, and Miss Blue keeps its reference behind a sign-in.

Documentation posture, August 2026

ProviderReferenceSandbox
SendbluePublic, request shapes documentedFree
BlooioPublic, publishes an OpenAPI specFree
LoopMessagePublicFree, 5-contact cap
Miss BlueBehind a sign-inFree
Tuco AIOnboarding-ledNo
LinqPublic referenceTrial
PhotonPublic, SDK-firstFree tier

A gated API reference is itself a signal

It is a decision that you should be qualified before you are informed. Not disqualifying, but worth noticing — and an OpenAPI spec is worth more than a nicely designed docs site, because you can generate a client from it and diff it when it changes.

The five things to look up first

  1. The error table. If there is not one, the platform has not enumerated its failure modes. You specifically want "not on iMessage" distinguished from "rate limited" from "we are broken".
  2. Rate limits, in numbers. Per minute and per day, and whether exceeding them returns a 429 or silently queues. Silent queueing is worse.
  3. The full webhook payload plus the signing algorithm. Unsigned means unauthenticated in practice.
  4. The awkward endpoints — removing a reaction, group threads, number lookup. These reveal how deep the integration goes.
  5. A dated changelog. No changelog means you learn about breaking changes from your error rate.

The full comparison of each provider's reference.