Apple Messages for Business, and why you probably cannot use it
The only route into iMessage that Apple sanctions, what it requires, why it is closed to almost everyone, and what that means for the rest of the market.
Apple Messages for Business is the only route into iMessage that Apple sanctions. It is also not what most people mean when they say iMessage API, it is closed to almost everyone who wants it, and understanding why explains the shape of this entire market.
What it actually is
It is a customer-service channel. A person taps a button on a business's website, in Maps, in Safari or in Search, and a conversation opens in Messages. The business answers.
Two structural facts follow, and they matter more than any feature.
Conversations are customer-initiated. The person messages the business first. There is no supported way for a brand to open a conversation with someone who has not opened one with it. An agent that texts you first is not a thing this programme is built to allow.
You do not integrate with it directly. A business selects an Apple-approved Messaging Service Provider, and the MSP holds the connection. You are a customer of an MSP, not of Apple.
Why becoming an MSP is not a workaround
Apple's own onboarding documentation sets out what an MSP must have: a messaging platform supporting asynchronous conversations and intent-based routing, a channel connector, a live agent console customisable for the channel's features, and virtual assistant or bot flows to triage incoming conversations. On top of that, a team able to build integrations into each brand's back-end systems: CRM, order management, authentication.
That is a contact-centre company. It is a reasonable specification if you are Apple and you want the channel to be reliable, and it is an insurmountable one if you are three people building an agent.
The programme has also been reported as closed to new MSP partners in 2026, which removes even the theoretical path.
The one exception, and what it proves
Poke, built by The Interaction Company, was approved as the first independent third-party AI agent on the programme. It launched in March 2026, exchanged more than 100 million messages, and was acquired by Cognition in July.
One approval, in a market with dozens of products trying. In this directory, 28 agents reach iMessage and 27 of them do it some other way.
That ratio is the fact to take away. If your plan depends on Apple approving you, the base rate is not encouraging, and it should be a hope rather than a dependency.
What everyone else does instead
Two routes, both outside the programme.
A managed API. A third party operates Apple infrastructure and gives you a REST API and webhooks. Published prices start around $5 a month metered and run to $289 for a dedicated line. This is what almost every agent here runs on, and the full breakdown is in iMessage API providers, compared.
A Mac you run yourself. An open-source bridge such as BlueBubbles on a machine with Messages signed in. Free, and the uptime, the Apple account and the absence of any support arrangement are yours.
Neither is sanctioned by Apple, and it is worth being clear-eyed that this is a platform-dependency risk rather than a technical one. One provider is unusually candid about the mechanics, itemising its setup fee as a dedicated Mac mini, a warmed Apple ID and carrier KYC in your business name, which is a fair description of what the whole managed category is doing.
What to take from this
If you are building customer service for an established brand, Messages for Business is your route and an approved MSP is your supplier. The customer-initiated model fits support naturally, because the customer is initiating anyway.
If you are building an assistant that reaches out, the programme is structurally wrong for you regardless of approval, and you should stop treating it as the goal.
If you are choosing a managed provider, ask what happens when the Apple account behind your line is flagged, how quickly it is restored, and whether anything contractual backs that answer. Only one provider in our comparison publishes an uptime SLA and only one publishes a recovery commitment.
Apple's own design here is a legal architecture as much as a product one, and the customer-initiated rule is the clearest expression of it. That is worth reading alongside who you are allowed to message, because the same principle shows up in consent law from a different direction.