Where an Apple Messages for Business chat starts
Customers do not install a separate app to message a brand on Apple Messages for Business. They start inside Messages, from a place the brand has registered. Typical entry points: A button or link on the brand's website Apple Maps A conversation URL A QR code Message Suggest, when Apple surfaces the brand The customer starts the thread. Consented invitations are a narrower path, and they are not…
Brands search for an Apple Messages for Business API key. Yet Apple does not provide such a key to brands. The channel exists. A customer can converse with a business via the Messages app, Apple Maps, Safari, or a Message Suggest result. However, this integration is not a public REST API that can be called from a separate backend.
Apple mandates an approved Messaging Service Provider (MSP). The MSP handles the server-to-server Messages for Business API. Your brand connects to the MSP. This distinction is crucial. Most products labeled as iMessage APIs are separate systems offering unofficial iMessage sending via Apple IDs or Macs. These are not Apple Messages for Business, and they cannot grant a business presence in Apple Maps or display an Apple Pay button in Messages.
Public availability necessitates Apple's onboarding rules, which place the gate on the MSP and the experience, not a developer token. An Apple-approved MSP is required. The organization must have an Apple Business Register account. The conversation must include a live agent during business hours. A bot-only flow is not approved.
Apple Experience Review is required before moving from test to commercial. Customer-initiated entry points are not permitted. The channel is not for unsolicited outbound iMessages. The requirements, message flow, and CRM integration process (handled by the MSP's connectors, not an Apple CRM specification) are documented at Apple Messages for Business API requirements.
Apple maintains its own list of approved providers. The difference between providers lies in the interactive features they offer, such as list pickers, time pickers, Apple Pay, authentication, rich links, and live-agent handoff. A directory of capabilities is available at amb.directory/msps. Pricing for the channel is not charged per-message by Apple.
Instead, the MSP charges based on seats, volume, and the extent of integration. This information is outlined in Apple Messages for Business pricing. If you intend to develop the MSP platform rather than purchase one, begin with Apple's own documentation: Messages for Business REST API MSP onboarding. Disclosure: I operate amb.directory, a directory of brands utilizing Apple Messages for Business and the MSPs that implement the channel.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
This story
This is one outlet's version. Read the fullest account.
