Most “iMessage API” products are a different system from Apple Messages for Business.
An unofficial sender uses Apple IDs or Macs to push blue-bubble messages. Apple Messages for Business is the channel inside the Messages app that a brand reaches through an approved Messaging Service Provider. It is how a customer starts a chat from a website, Apple Maps, Safari, or a Message Suggest result. It is not a public API key a brand calls on its own.
What a brand actually integrates
Apple does not give brands a standalone REST API. The MSP implements Apple’s server-to-server Messages for Business API. The brand connects to the MSP. Automation has to go through that MSP, with a live agent available during business hours, and the experience has to pass Apple’s Experience Review before it can go public.
The requirement list and the message flow are here: Apple Messages for Business API requirements.
Why the distinction matters
A blue-bubble sender will not put a business in Maps, will not add an Apple Pay button inside Messages, and will not survive Experience Review. If the job is customer-initiated support, booking, or commerce on iPhone, the path is an approved MSP.
A directory of those providers, compared by capability, is at amb.directory/msps.
Disclosure: I publish amb.directory, a directory of brands using Apple Messages for Business and the MSPs that implement the channel.
Top comments (0)