iMessage Webhooks and REST API
The short answer
Blue Reacher's webhooks and REST API connect any CRM to your iMessage line. Your system posts a message to one endpoint, and Blue Reacher posts back to a URL you own the moment a lead replies or a message changes state. Auth is a bearer token in one header. The inbound payload carries four fields: from, content, channel and external_id. GoHighLevel teams get the same behavior through the native integration, no code. Full reference lives at docs.bluereacher.com.
Key takeaways
- The REST API is how your system sends a message out.
- The webhook fires on every reply and carries four fields: from (lead's E.164 number), content (raw text), channel (imessage/rcs/sms), and external_id (stable message ID).
- Delivery event webhooks report state changes: accepted, delivered, read, not completed, or opt-out.
- Every endpoint sits under https://api.bluereacher.com/v1/messages.
- Teams wire webhooks into every stage of the funnel.
- White-glove activation stands up your line and issues your API key.
How a message falls back
What are Blue Reacher webhooks and the REST API?
The REST API is how your system sends a message out. Webhooks are how Blue Reacher sends events back: replies, delivery state changes, opt-outs. A webhook is a URL you own that receives a JSON POST the instant something happens, so nothing in your stack has to poll.
- For an operator, that split matters. Polling means your CRM finds out about a reply on the next cycle. A webhook means the record updates and the rep gets pinged while the lead is still holding the phone. On 98% open rate and 90% read inside three minutes, that difference decides conversation or voicemail.
What does the inbound message webhook send you?
The webhook fires on every reply and carries four fields: from (lead's E.164 number), content (raw text), channel (imessage/rcs/sms), and external_id (stable message ID).
- Store external_id to keep replies deduplicated and threads threaded. It's what turns "a reply came in" into "this exact reply, once" and prevents automated follow-ups from firing twice on a retry.
Reading how it works is not the same as watching it answer one of your own leads. The Blue Funnel Map does the second one.
See it on your own listWhat do delivery event webhooks tell you?
Delivery event webhooks report state changes: accepted, delivered, read, not completed, or opt-out. Your CRM learns the status without opening the platform.
- Operators use delivery events three ways. Delivery state gates the next step so reminders only go out if confirmations landed. Read state with no reply triggers a nudge. Channel tells you which contacts landed on iMessage versus RCS or SMS.
Sent
- What it means
- Blue Reacher accepted the message and pushed it to your line
- Typical workflow move
- Stamp the activity on the CRM record
Delivered
- What it means
- The message reached the recipient's device
- Typical workflow move
- Release the next step in the sequence
Read
- What it means
- The recipient opened the thread
- Typical workflow move
- Start the no-reply timer, alert the rep on high-intent sends
Not delivered on that channel
- What it means
- The send did not complete on the rail it was tried on
- Typical workflow move
- Stamp the record and let the RCS then SMS fallback carry it
Opt-out
- What it means
- The contact asked to stop
- Typical workflow move
- Suppress the contact everywhere, immediately
What can you do with the REST API?
Every endpoint sits under https://api.bluereacher.com/v1/messages. Authentication is a bearer header. No request signing, no OAuth, no SDK. Anything that can make an HTTP request can drive it, including Make, n8n and Zapier.
- Four capabilities carry most workflows: sending a message, sending with media, checking iMessage availability before send, and pulling a thread. Your key is issued with your line at activation.
How do teams use webhooks across the funnel?
How do teams use webhooks across the funnel?
Teams wire webhooks into every stage of the funnel. Speed-to-lead: a form fill triggers a message within seconds, and the reply lands on the webhook while the prospect is still on your pricing page. In the middle, booking confirmations and reminders run off delivery events. At the bottom, no-show recovery and post-call follow-up carry the highest value per trigger.
- Outbound is the smaller half. The bigger half is converting traffic you already pay for: reactivation, qualification, confirmations, reminders, onboarding, retention, referrals and reviews, where 2-3x the reply rate of cold email turns a campaign into actual results.
How do you set up webhooks and API access?
How do you set up webhooks and API access?
White-glove activation stands up your line and issues your API key. Give Blue Reacher the webhook URL, map four inbound fields to your CRM, and add a send step to your workflows.
- Pick the path matching your stack. GoHighLevel connects natively. HubSpot, Salesforce, Pipedrive, Close and Attio: one HTTP action and one webhook. Make, n8n, Zapier: generic HTTP step and catch-hook. In-house apps: thin client with bearer header and receiver route. Pricing: $249/mo or $1,949/year, unlimited iMessages, no per-message fees, 50 opted-in / 30 cold new conversations daily.
GoHighLevel
- How you connect
- Native integration
- What you build
- Nothing. Sends and replies flow into the existing conversation view
HubSpot, Salesforce, Pipedrive, Close, Attio
- How you connect
- REST API plus webhooks
- What you build
- An HTTP action in your workflow builder and one webhook receiver
Make, n8n, Zapier or another automation layer
- How you connect
- Generic HTTP step plus a catch-hook
- What you build
- One scenario per direction, no code
In-house app or AI agent stack
- How you connect
- REST API plus webhooks
- What you build
- A thin client with the bearer header and one receiver route
Frequently asked questions
Do I need a developer to use Blue Reacher's webhooks and API?
No. Make, n8n and Zapier can call the API and catch webhooks without code. GoHighLevel teams need nothing; the integration is native. A developer helps for in-house apps or agents, and even then it's one header and one receiver route.
What does the Blue Reacher inbound webhook payload look like?
The inbound webhook posts JSON with four fields: from (lead number), content (message), channel (imessage/rcs/sms), external_id (stable message ID for deduping).
How does authentication work on the Blue Reacher API?
Every request carries Authorization: Bearer brk_live_your_key. No signing, no OAuth, no token refresh. Your key is issued at activation; full reference at docs.bluereacher.com.
What should my endpoint do when a webhook arrives?
Your endpoint should acknowledge fast and process afterward. Return a 2xx as soon as the payload is stored, then run classification, the CRM write and routing on your own time. Keep external_id as the dedupe key so one reply is never handled twice. Retry behavior is published in the API reference.
Which CRMs can connect through the API?
Any CRM that can send an HTTP request and receive one can connect, which in practice covers every CRM a B2B team is likely to run. HubSpot, Salesforce, Pipedrive, Close, Attio and in-house systems connect the same way: an outbound HTTP action for sends, a webhook endpoint for replies and delivery events. GoHighLevel connects natively instead.
Are there per-message fees on API sends?
No. Blue Reacher is $249 per line per month or $1,949 per line per year, and iMessages are unlimited, with new conversations paced at up to 50 opted-in / 30 cold per line per day. A sequence that fires six touches per contact costs exactly what a single send costs, so follow-up depth is a strategy decision rather than a budget one.
Do API sends require A2P 10DLC registration?
No A2P registration is required to send on your Blue Reacher iMessage line. There's no brand vetting queue and no campaign approval sitting between your key and your first send, so going live is a same-day decision.
Can I use the API alongside the GoHighLevel integration?
Yes. Both paths point at the same iMessage line and the same message history, so a team can keep conversations inside GoHighLevel while an in-house scoring service or agent listens on the webhook. Events post to your URL regardless of which path sent the message.
Connect your CRM to the one inbox that still answers
Book your Blue Funnel Map and we'll map your inbound webhook to your CRM fields on the call, and if you ask us to open it by text you'll have a real payload from your own reply before we hang up. White-glove activation stands up your dedicated line with nothing for you to install, the $449 activation fee is waived on annual billing, and lines are $249 a month with unlimited iMessages paced at up to 50 opted-in / 30 cold new conversations per line per day. Full API reference at docs.bluereacher.com.