Is there an official iMessage API?

No. Apple has never published a public iMessage API. Every iMessage automation product works by running macOS — either on hardware the vendor hosts, or on a Mac you own.

How many iMessages can you send per day before Apple flags you?

Apple publishes no official limits, and there is no single number — the ceiling scales with your account's age and history. Hosted platforms publish caps near 50 new conversations per day because that is the safe figure for a freshly provisioned Apple ID in a farm; an established personal account has more headroom. Cold outreach draws scrutiny far more than replies in existing threads. Apple enforces these limits itself and they tighten on a number that reads as bulk outreach rather than conversation, so ramp up gradually and keep your reply rate healthy.

Is iMessage automation against Apple’s terms?

Apple’s terms prohibit spam and bulk unsolicited messaging. Automation used for one-to-one conversation — drafting replies, scheduling follow-ups, connecting an AI assistant to your own account — operates in the same space as any Mac app that reads and sends messages on your behalf. Respecting Apple’s observed rate limits and messaging people who want to hear from you is what keeps an account healthy.

Guide

What is iMessage automation?

iMessage automation is software that sends and receives Apple iMessages programmatically — so texts can come from a CRM, a workflow, or an AI assistant instead of thumbs on a keyboard. autoMessage is an iMessage automation platform that runs on your own Mac and connects your account to AI tools like Claude, Cursor, and ChatGPT through an MCP server, plus a REST API and web dashboard.

Why iMessage is different from SMS

SMS has official carrier APIs (Twilio and friends). iMessage has none — Apple has never published a public API. iMessage only exists inside Apple's ecosystem: blue bubbles, read receipts, tapbacks, high-resolution media, and encryption, delivered through Apple's Messages app on Apple hardware. That's precisely why it converts better — iMessage is where real conversations happen, and messages from a real Apple ID look and feel personal — and why automating it requires a Mac somewhere in the loop.

The two architectures

1. Hosted Mac farms

The vendor racks Mac minis in a farm, provisions Apple IDs and phone numbers, and sells you a "line." This is how Tuco, Sendblue, Linq Blue, and Project Blue work. It's turnkey but expensive — $149 to $1,000+ per line per month — and the messages come from a stranger's Apple ID in a farm, not from you.

2. Your own Mac (BYOD)

The software runs on a Mac you already own, using your own Apple ID and number. Messages are genuinely from you; contacts see the same thread they've always had with you. This is how autoMessage works — the Mac app syncs your conversations to a cloud dashboard and exposes them to AI tools and an API, priced as software rather than as someone else's hardware.

What about rate limits?

Apple publishes no official numbers, and the real answer is that there is no single number — the ceiling scales with your account. A long-standing Apple ID carrying real two-way conversation has materially more headroom than one provisioned last week.

This is why most hosted platforms publish caps near 50 new conversations a day. Their model concentrates sending into accounts they provisioned in bulk — no history, outbound-only traffic, many accounts on shared infrastructure. That concentration is what has to be capped. It's an accurate limit for that setup. It isn't Apple's law.

What's consistent across every account: cold outreach is scrutinised far more than replies in existing threads, template-blast patterns (many near-identical messages, low reply rate) draw attention faster than raw volume, and sudden jumps draw it faster than gradual growth. autoMessage surfaces deliverability warnings instead of capping you — but the account is yours, so the judgement is too.

Worth knowing: Apple enforces these limits itself, and they tighten on a number that reads as bulk outreach rather than conversation. No vendor can override that — so ramp up gradually and keep your reply rate healthy.

What AI agents change

The first generation of iMessage automation was campaign blasts and CRM drips. The current generation is conversational: an AI assistant that reads a thread with full context, drafts the reply in your voice, schedules the follow-up, and updates your CRM — across tools like Claude, Cursor, and ChatGPT. The bridge that makes this possible is the Model Context Protocol (MCP): autoMessage exposes your iMessage account as MCP tools, so any AI client you already use can read and send on your behalf — with you in the approval loop as much or as little as you want.

Common questions

Is there an official iMessage API?: No. Apple has never published one. Every iMessage automation product — hosted or BYOD — works by running macOS somewhere and driving the Messages app.
How many iMessages can I send per day?: There's no fixed number — it scales with your account's age and history. Hosted platforms mostly publish caps near 50 new conversations a day because that's the safe figure for a freshly provisioned Apple ID in a farm; an established personal account has more room. Cold outreach is what gets scrutinised, not replies in existing threads. Start conservative, scale gradually, and watch your reply rate.
Is iMessage automation against Apple's terms?: Spam and bulk unsolicited messaging are. One-to-one conversation with automation assistance — drafting, scheduling, AI replies on your own account — is the same space as any Mac app that works with your messages. Message people who want to hear from you and respect the observed limits; that's what keeps an Apple ID healthy.

Try iMessage automation on your own Mac

autoMessage sets up in about ten minutes. 14-day free trial, from $59/month. Cancel anytime.

Start free trial