Every other major messaging platform has a bot story. Telegram's Bot API is a weekend project. Slack has an app directory. Discord has a whole ecosystem. Meta runs official business platforms for WhatsApp and Messenger.
Apple has none of this for iMessage, and has never signalled that it intends to. If you have been searching for the endpoint, this is the answer: it does not exist, and no entitlement unlocks it.
What Apple offers that is close, and is not it
- iMessage apps run inside the Messages UI and can insert content into the compose field. The user sends. Not a bot — a keyboard accessory.
- Messages for Business is a real, Apple-sanctioned conversational channel with a REST API, and your side of it can be entirely automated. The customer must start the conversation. Full guide.
- Siri is Apple's assistant, not a platform you can put an agent on.
The complete tour of what Apple actually ships is here, and the pattern across all of it is the same: a person, or a prior customer action, stays in the loop.
Why not
A bot API on iMessage would mean automated senders reaching any phone number. Apple's read is evidently that this destroys the channel: the moment the blue bubble carries bulk automation, it stops being the trusted one and starts being SMS with better typography.
There is a second reason worth stating plainly. iMessage is end-to-end encrypted between devices. A server-side bot is by definition an endpoint that reads plaintext, and every bot platform is an argument about where that boundary sits. Apple has consistently chosen not to open one.
What people build anyway
| Approach | How it reaches iMessage | Realistic use |
|---|---|---|
| Third-party provider API | The provider runs Apple accounts and devices; you call REST | The only production-viable route for outbound bots |
| Self-hosted bridge on your own Mac | Your Apple ID, your hardware | Personal bots, prototypes, hobby projects |
| Messages for Business | Apple's official channel through an approved CSP | Customer support at real scale, inbound only |
| Shortcuts automation | On-device, as the phone's owner | Auto-replies for one person, not a product |
Row one is what almost every commercial "iMessage bot" you have seen actually is. The provider is carrying the unofficial part; you are calling a normal HTTP API. How that works.
If you are building an agent
This has become the dominant use of the category — an LLM holding a real conversation in a blue bubble rather than a chat widget nobody opens. Two providers position explicitly for it: Photon, which publishes prices and offers a free tier, and Linq at the enterprise end. Sendblue sells a dedicated AI Agent line.
The rules that matter more than the model
An agent on this channel will get things wrong in a thread the customer keeps forever, next to messages from their family. Rate-limit it, cap how many exchanges it handles before a human takes over, never let it invent a price or a commitment, and make the handoff to a person obvious and fast. What running one actually involves.
Design for the constraint
There is a real design advantage hiding in all this. Because there is no bot ecosystem, there is no bot fatigue — people are not conditioned to ignore automated messages in iMessage the way they are in every other channel. A well-written automated message here gets read, which is exactly why the channel is worth the trouble.
- Write it so it does not announce itself as a bot. How to write a message that reads as human.
- Reply fast, because that is the expectation the channel sets.
- Hand to a person at the first sign the conversation matters. Someone has to be there.
- Keep the volume low. What paces a line safely.
- Keep the consent record. The compliance rules apply to bots exactly as they do to people.
Northgate Realty
iMessage
Hi Sam — Elena's assistant at Northgate. She's got Saturday 11am or Sunday 2pm free for the Oak St walkthrough. Either work?
Sunday's better
Booked for Sunday 2pm. Elena will confirm the details tomorrow morning — she's copied on this thread.
Will Apple ever ship one?
Nothing in the public record suggests it. Regulatory pressure in the EU has pushed Apple on interoperability, and it adopted RCS — which addresses cross-platform messaging without opening iMessage itself to programmatic senders. That is a telling choice: given a reason to open something, Apple opened the standard, not the network.
Plan for the current state. If it changes, you will have a migration; if you plan for a change that never comes, you have nothing at all. Where the category stands now.