Limited offer

Build with our iMessage API/MCP. Get our sandbox for free.

Wire iMessage into any stack

One POST sends a message from your dedicated line. Signed webhooks bring replies, delivery states and opt-outs back the moment they happen.

Included on every line. Full reference at docs.bluereacher.com.

9:415G
AR

Alex Rivera

iMessage

iMessage · Today

Hi Alex, your demo request came through. Free for 15 minutes tomorrow?

Yes, 11 works.

Booked. The calendar invite is on its way.

Sent by your API

A form fill triggered the send. The reply went straight to the CRM by webhook.

One POST to sendSigned webhooks for every eventBearer-token auth

Send with one request, hear back instantly

The API sends, webhooks receive. Nothing polls and nothing waits on a dashboard.

Trigger

New lead in CRM

Under 9 seconds

Send iMessage

No code required

Make, n8n and Zapier call the API and catch webhooks without code. GoHighLevel connects natively, with nothing to build.

Delivered1,184
Read1,067
Replied312
Opted out9

Events drive your automations

Replies, delivery states and opt-outs post to your endpoint as signed events, each with a timestamp and the channel used.

MariaDelivered viaiMessage
JonDelivered viaRCS
PriyaDelivered viaiMessage
SamDelivered viaSMS

Every channel, one payload

Replies over iMessage, RCS or SMS arrive in the same message.received shape, with service_type telling you which rail carried them.

Proposal attached. Happy to walk it through.
Sent2:02 PM
Delivered2:02 PM
Read2:14 PM
Replied2:16 PM

States as they change

Sent, delivered, read and replied post as they happen, so a workflow can gate its next step on a real event.

What your endpoint receives

Every webhook is a signed JSON envelope. message.received carries phone_number, content, service_type, message_id and contact_id. Verify the signature, return a 2xx fast, and dedupe on event_id so a retry is handled once.

message.receivedcontact.opted_outSigned envelopes

POST /v1/messages

{ "to": "+15125550142", "content": "..." }

webhook message.received

{ "service_type": "iMessage", "content": "Yes, Thursday" }

What are Blue Reacher's REST API and webhooks?

The REST API at api.bluereacher.com/v1 sends messages from your dedicated line: POST to /messages with a bearer key in the Authorization header and you get a message_id back. Webhooks are the return path. Register an https endpoint and replies, delivery states and opt-outs arrive there as signed JSON the moment they happen.

Questions about the API and webhooks

The questions buyers ask before they start. Anything not here is answered in the answers library.

Do I need a developer?+

No. Make, n8n and Zapier call the API and catch webhooks without code, and GoHighLevel connects natively. For an in-house app, it is one header and one receiving route.

How does authentication work?+

Every request carries Authorization: Bearer brk_live_your_key. There is no OAuth flow and no token refresh, and test keys start with brk_test_. The full reference is at docs.bluereacher.com.

What should my endpoint do when a webhook arrives?+

Store the payload, return a 2xx straight away, then do the CRM write on your own time. Keep event_id as the dedupe key so a retried delivery is only handled once.

Can an AI agent use it?+

Yes. The same surface is exposed as an MCP server with tools to check availability, send, list messages and check delivery status, and it works in Claude and Cursor.

Are there per-message fees on API sends?+

No. Every line is $249 a month with unlimited iMessages paced at 50 opted-in / 30 cold new contacts a day, whether you send from the platform or the API.

Wire your CRM to the channel that answers

Book your Blue Funnel Map and we map your webhook to your CRM fields on the call, using a real reply from your own phone.

No A2P registrationWhite-glove setup includedUnlimited iMessages, paced at 50 opted-in / 30 cold a day

Most teams are live within a week.