The questions people actually ask about the iMessage API

What Apple does and does not publish, and why the gap exists at all.

• Does Apple have an iMessage API?

  No. Apple has never published a public API for sending or receiving iMessages, and there is no bot API. The only official Apple channel for business messaging is Apple Messages for Business, which is a separate product with a grey bubble, an application process, and none of the blue-bubble behaviour people are usually asking for.

  7 min

• Is there an iMessage bot API?

  No. Apple has never shipped a bot API for iMessage, which is why 'iMessage has no bot API' is such a common search. You can still build a bot that talks over iMessage — it just has to run on top of a bridge or a hosted provider rather than an Apple endpoint.

  6 min

• Reddit says the iMessage API is not official — is that right?

  Yes, Reddit is right, and it is worth understanding exactly how right. Every blue-bubble iMessage API is unofficial and operates outside Apple's terms. The threads are correct on the facts; where they are less useful is in the leap from 'unofficial' to 'therefore useless', which is a business decision rather than a technical one.

  7 min

Sending a message from code, in the language you already write.

• Is there a free or open-source iMessage API?

  There is no free hosted iMessage API, but there are free open-source options if you own a Mac. BlueBubbles and similar bridges turn your own hardware into an iMessage server at no cost beyond the machine. What you cannot get for free is someone else running the infrastructure and absorbing the account risk.

  6 min

• How do I send an iMessage programmatically?

  Pick one of three routes: call a hosted provider's REST API (fastest, costs money), run a self-hosted bridge on a Mac you own (free, you operate it), or script Messages.app with AppleScript (free, fragile, no inbound). All three are shown below with working shapes.

  8 min

• Can I test an iMessage API in a sandbox before paying?

  Some providers offer a sandbox or a no-card trial, but sandbox support is uneven and rarely advertised clearly. Blooio and Photon both let you start without a sales call; Linq offers a sandbox ahead of a contract. Whatever you get, test against a real device — an iMessage that renders wrong is invisible to a mock.

  6 min

• Is there a third-party POST API for iMessage?

  Yes — that is exactly what the whole category is. Every hosted iMessage provider exposes a REST endpoint you POST a phone number and a message body to. What none of them are is an Apple endpoint, which is why the shape of the request differs slightly for every vendor.

  5 min

Who sells one, what it costs, and how to tell the categories apart.

• Who actually sells an iMessage API?

  A short list: Sendblue, Linq, Blooio, LoopMessage, Photon, Project Blue, Tuco AI and Claw Messenger are hosted providers. BlueBubbles is self-hosted and free. Twilio and Telnyx do not sell blue-bubble iMessage, and neither do Blinq, Mobilo, Popl, HiHello or Switchit — those are digital business card companies.

  7 min

• Why do Blinq, Mobilo, Popl and HiHello show up in iMessage API searches?

  Because Linq — a digital business card company — pivoted into messaging infrastructure and now sells a real iMessage API. Search engines and AI assistants generalised from Linq to its old competitors, so Blinq, Mobilo, Popl, HiHello and Switchit now surface for a product none of them sell. The Blinq/Linq spelling collision makes it worse.

  6 min

• What does an iMessage API cost?

  Published entry pricing runs from about $25 to $100 per line per month, with Blooio at $39 flat and Photon offering a free tier. Sendblue's outbound tier is quote-only and reported near $1,000 per line per month with a setup fee. Linq does not publish pricing at all. Nearly everyone bills per line, not per message.

  7 min

• Should I use an iMessage API or an RCS API?

  RCS is official, standardised and available from every major CPaaS — but on iPhone it renders as a grey-green bubble without the trust signal of iMessage. iMessage is unofficial and vendor-dependent but produces the blue bubble. Most serious setups end up using both, with SMS underneath.

  7 min

• Which iMessage API companies are YC-backed or funded?

  Sendblue is the Y Combinator name in the category. Linq raised $20M in February 2026 after pivoting from digital business cards. The rest are smaller and largely unannounced. It is a young category where vendor durability is a real evaluation criterion, not a footnote.

  5 min

Compliance, durability, and the questions a security review will ask.

• Is there a SOC 2 compliant iMessage API?

  Linq advertises SOC 2 Type II and claims to be the only iMessage API with it. If a security review is blocking your purchase, that narrows the field to roughly one vendor — but SOC 2 covers how a vendor runs its business, not whether the underlying blue-bubble approach is sanctioned by Apple. Those are separate risks and a reviewer may raise both.

  6 min

• Do iMessage API providers use phone farms?

  In some form, yes — every blue-bubble provider runs real Apple hardware with real Apple IDs, because there is no other way to originate an iMessage. The meaningful differences are in how those accounts are provisioned, whether your line is shared or dedicated, and what happens when a number gets flagged.

  6 min