Messaging Flow
Flow iMessage API
Connect an application to Flow’s hosted messaging service for supported channels without operating a local Mac.
Source review: 2026-10-27 · Imported: 1 November 2026
A practical starting point
What could you build?
An opted in user can exchange messages with a personal assistant through a supported messaging channel.
Before you connect
The trial is limited and ongoing lines are paid. Obtain recipient consent and review channel requirements before sending messages.
Capabilities & requirements
Dated specifications from the licensed source dataset. “Not published” indicates missing information, rather than confirmed absence.
| Capability | Details and source |
|---|---|
| Status | Newly launched Site banner reads “Now launching iMessage API”; launch post dated Oct 27, 2026. SMS is a pilot; no SLA published. Source (external) · Verified 2026-10-27 on https://flow.engineer/pricing |
| API key required | Bearer key; iMessage needs an account Our keyless GET /v0/app on 2026-10-27 returned HTTP 401. A keyless sandbox key covers Telegram only; iMessage starts on a signed-in account. Source (external) · Verified 2026-10-27 on https://api.flow.engineer/llms.txt |
| Free tier | Trial: 25 people, once Free trial on the shared iMessage line for 25 people ever; Shared $25/month at launch ($30 list), Dedicated $100/month. Source (external) · Verified 2026-10-27 on https://flow.engineer/pricing |
| Rate limit | People per day/month, not messages Shared: 300/month, 200/day. Dedicated: 250/day ramping to 1,000 in 14 days; 429 with retry_after past it. Source (external) · Verified 2026-10-27 on https://flow.engineer/pricing |
| Official MCP server | Hosted, api.flow.engineer/mcp Bearer key; Flow says it is for development, not a runtime dependency. Keyless call returned 401. Source (external) · Verified 2026-10-27 on https://api.flow.engineer/llms.txt |
| Official SDK | TypeScript + Python @flow-engineer/messaging (npm 0.4.2) and flow-messaging (PyPI 0.2.2); Go not published yet. Source (external) · Verified 2026-10-27 on https://api.flow.engineer/llms.txt |
| Data license / terms | Proprietary service; framework Apache-2.0 The hosted API is under Flow’s terms; the Flow Framework repo is Apache-2.0. Source (external) · Verified 2026-10-27 on https://flow.engineer/terms |
| Commercial use allowed | Yes, under the acceptable-use policy No health, card, bank or government ID data on iMessage; no spam or limit dodging. Apple or the line provider can stop a line. Source (external) · Verified 2026-10-27 on https://flow.engineer/acceptable-use |
| CORS / browser use | No CORS header Our GET and preflight to /v0/app with a third-party Origin on 2026-10-27 returned 401 with no Access-Control-Allow-Origin; call it from your server. Source (external) · Verified 2026-10-27 on https://api.flow.engineer/llms.txt |
| Freshness / coverage | Not published Not applicable as a dataset; delivery mechanism behind the iMessage lines is not published. Source (external) · Not published by vendor: checked 2026-10-27 on https://flow.engineer/blog/imessage-api-without-mac |
Operational reference
Additional facts and qualifications retained from AgentAPIList’s CC BY 4.0 dataset, with provider references.
Price
iMessage free trial: 25 people on the shared line, ever (no monthly reset). Shared: $25/month at launch (listed as $5 off $30) for 300 people a month and 200 a day. Dedicated: $100/month for your own US number. Outbound add-on (agent writes first, Dedicated only): +$40/month. No per-message fees; SMS/RCS fallback included. Flow Cloud Pro ($25/month) is a separate plan for hosting and does not include iMessage.
Provider reference (external)API key / auth
Authorization: Bearer with an fk_test_ (sandbox) or fk_live_ key. A keyless sandbox key can be created with one POST, but it covers Telegram only; iMessage starts with the free trial on a signed-in Flow account (Google, GitHub or email link). Webhooks are signed with an HMAC-SHA256 Flow-Signature header. Our keyless GET /v0/app on 2026-10-27 returned HTTP 401.
Provider reference (external)Rate limits
Plans count people, not messages: each person counts once per UTC day and month. A new dedicated line starts at 250 people a day and ramps to 1,000 within 14 days; past it, sends to a new person get 429 rate_limited with retry_after. Outbound starts 2 new conversations a day, up to 40 from day 22, and the API docs list 4 new iMessage contacts an hour. Senders that look spammy are throttled for 24 hours.
Provider reference (external)Terms and Apple risk
Flow’s terms (updated Oct 27, 2026) say Apple or Flow’s iMessage line provider can limit or stop a line at any time and Flow cannot reverse a platform’s block. Its acceptable-use policy says people’s spam reports can get a number blocked by Apple, and on a new line one report can be enough. On iMessage you may not send or ask for health information, card or bank numbers, or government ID numbers. Using several accounts or rotating numbers to dodge limits or blocks is banned.
Provider reference (external)How iMessage is delivered
Hosted US numbers (shared or dedicated) run by Flow through an unnamed iMessage line provider; you do not run a Mac. Not Apple Messages for Business, which Flow’s own guide describes as a separate Apple service. Not verified: the underlying technology (Mac relays, Apple IDs or devices) and the provider’s name, which Flow does not publish.
Provider reference (external)SDK / MCP
TypeScript SDK and CLI @flow-engineer/messaging (0.4.2 on npm on the check date), Python SDK flow-messaging (0.2.2 on PyPI). MCP server at https://api.flow.engineer/mcp with the same Bearer key, meant for development; Flow says apps should call the REST API at runtime. The Flow Framework for building the agent is open source (Apache-2.0).
Provider reference (external)Status
Newly launched: the site banner reads “Now launching iMessage API” and the launch post is dated Oct 27, 2026. Flow labels its US SMS channel as a pilot; no SLA is published. Group chats need a dedicated line, and Flow reviews each dedicated line before setting it up (usually within a day).
Provider reference (external)Setup references
HTTP request example
Adapted from the attributed source dataset. Review before running; these examples were not executed by Tech in General.
# Run without a key on 2026-10-27: shows the auth scheme
curl -sS https://api.flow.engineer/v0/app
# Not run: reply in an iMessage conversation (needs a key from a Flow account)
curl -sS -X POST https://api.flow.engineer/v0/conversations/$CONVERSATION_ID/basic \
-H "Authorization: Bearer $FLOW_MESSAGING_KEY" \
-H "Idempotency-Key: evt_123:reply" \
-H "Content-Type: application/json" \
-d '{"text":"Your table for two is booked for 7 pm."}'Agent connection example
Adapted from the attributed source dataset. Review before running; these examples were not executed by Tech in General.
// Claude Code, for building and testing (Flow says not to use MCP at runtime):
// claude mcp add --transport http flow https://api.flow.engineer/mcp \
// --header "Authorization: Bearer $FLOW_MESSAGING_KEY"
// Runtime: verify Flow-Signature, then reply in the webhook answer
import express from "express";
const app = express();
app.post("/webhook", express.raw({ type: "application/json" }), (req, res) => {
// check Flow-Signature (HMAC-SHA256 of "t.{t}.{raw body}" with your whsec_ secret) first
const event = JSON.parse(req.body);
if (event.type !== "message.received") return res.sendStatus(200);
res.json({ reply: { kind: "basic", text: "Thanks, looking into it now." } });
});
app.listen(3000);A tool schema needs an HTTP implementation; it does not by itself install an MCP server. Keep credentials out of browser code.
Other connections to explore
Back to the full directory →Source & reuse
Download the complete licensed source snapshot (JSON), including the original source’s caveats, alternative notes and examples.