The short version: there is no official iMessage API. Not a private beta, not an application form, not an enterprise tier. Apple has never published an interface that lets your server send an iMessage to a customer, and the absence is deliberate rather than an oversight.
This surprises people because every other major messaging platform has one. Telegram, Slack, Discord, WhatsApp and even RCS all publish a documented way for software to send a message. iMessage is the conspicuous exception, and it has been the exception for the entire fourteen-year life of the product.
What Apple actually publishes
There are three things on developer.apple.com that come up when you search for an iMessage API. None of them is one. It is worth knowing exactly what each one is, because the confusion between them is where most wasted engineering time goes.
| What Apple ships | What it actually does | Can it send from a server? |
|---|---|---|
| Messages framework | Lets you build iMessage apps, sticker packs and interactive message bubbles that run inside the Messages app on a user's device. | No — it runs on-device, inside a conversation the user already opened. |
| Apple Messages for Business | Apple's official business channel. Customers start a conversation from Maps, Safari, Search or your website. Your brand gets a verified name and logo. | Yes, but only in reply to a conversation the customer started, through an approved partner, in a grey bubble. |
| Business Chat (legacy name) | The original name for Apple Messages for Business. Old blog posts and docs still call it this. It is the same product. | Same as above. |
The grey bubble is not the blue bubble
This is the single most important distinction in the whole category. Apple Messages for Business renders in a grey bubble with your logo — it reads as an official corporate channel. Person-to-person iMessage renders in a blue bubble. If your goal is for a message to look like it came from a human at a local business, Messages for Business is the wrong product. See Apple Messages for Business for the full breakdown.
Why Apple has never shipped one
Apple has never given an official reason, so anything here is inference — but the inference is not hard. iMessage is a retention feature, not a platform. Its value to Apple is that the blue bubble is scarce and means something: a message from a real person on a real iPhone.
A public bot API would destroy that in a quarter. The moment any server can send a blue bubble, the blue bubble stops signalling anything, and the social pressure that keeps teenagers on iPhones evaporates. Every other platform that shipped a bot API got spam as a consequence and absorbed it, because messaging was their product rather than a moat around a hardware business.
What a public API would give Apple
- Developer goodwill
- Parity with Telegram, Slack, WhatsApp
- A business messaging revenue line
- One less reason to leave iOS
What it would cost Apple
- The blue bubble stops meaning 'a real person'
- Spam arrives in the one inbox that has none
- End-to-end encryption claims get more complicated
- The strongest social lock-in in consumer tech, gone
Read the trade that way and the fourteen-year silence stops looking like neglect. Apple is not slow to ship this. Apple is not going to ship this.
So how do the services that sell one work?
Every vendor in this category is bridging to iMessage rather than calling an Apple endpoint, because there is no Apple endpoint to call. There are three broad approaches, and knowing which one you are buying tells you almost everything about how it will behave.
- Hosted infrastructure. The vendor runs Apple hardware and real Apple IDs at scale, and puts a REST or gRPC API in front of it. You send an HTTP request; a machine somewhere sends the actual iMessage. This is what Sendblue, Linq, Blooio, LoopMessage and Photon are all doing underneath, whatever the marketing says.
- Self-hosted bridge. You run the Mac. Software like BlueBubbles turns a Mac you own into a server with a local API. No third party holds your Apple ID, and no per-line fee — but you now operate a Mac that must never sleep.
- Scripting. AppleScript or the Shortcuts app driving Messages.app on a Mac you are sitting at. Free, fragile, and fine for a few dozen messages a day.
The full comparison is on the providers page, and the architectural trade-off between the first two is in hosted API vs self-hosted bridge.
None of this is Apple-sanctioned
Every blue-bubble service operates outside Apple's terms of service. That is not a hidden detail — it is the structural fact of the category, and it should shape how you build. Read iMessage vendor risk before you make this channel load-bearing.
What to do instead
The question behind 'does Apple have an API' is almost always 'can I text my customers from my software'. The answer to that is yes — you just pick a lane based on how much risk you can carry.
- You want blue bubbles and you accept the risk. Use a hosted provider. Start with the provider comparison and what it costs.
- You want an official, durable, Apple-blessed channel. Use Apple Messages for Business, accept the grey bubble, and accept that customers must start the conversation.
- You want zero vendor risk and you own a Mac. Run a self-hosted bridge.
- You mostly want reliable delivery, not blue specifically. Use SMS or RCS from a normal CPaaS, and read iMessage vs RCS first.
Related questions
- Is there an official Apple iMessage API for developers?
- No. Apple publishes no REST, gRPC or SDK interface for sending iMessages from a server. The Messages framework in iOS only lets you build iMessage apps and stickers that run inside the Messages UI on a user's own device.
- Where is the iMessage API documentation on developer.apple.com?
- It does not exist. Searching Apple's developer documentation returns the Messages framework (for iMessage apps and stickers) and Apple Messages for Business — neither of which is a send-a-message-from-your-server API.
- Does iMessage have a bot API?
- No. Unlike Telegram, Slack or Discord, Apple has never shipped a bot API for iMessage. Every service that offers one is bridging to iMessage by other means.
Still deciding?
Compare the services that can actually send this on the providers page, see what each one costs, or read the step-by-step guides.