API reference and integration guide
Send and read blue-bubble iMessages, manage contacts, lines and automations from your own system, your CRM or your AI agent.
Step 1
Send a message today
One POST with the key from Developers in your dashboard. No app to register.
Send a message →Step 2
Build an integration
Register an app, install it with OAuth 2.0 and call the same endpoints the dashboard uses.
Custom integrations →Step 3
Build with AI
Every page in one text file, for Claude, Cursor or any coding assistant.
Build with AI →The Blue Reacher API is JSON over HTTPS at https://api.bluereacher.com/v1. Send a message today with one dashboard key, or install an app with OAuth 2.0 and call the same endpoints the dashboard uses: messages, the inbox, contacts, lines, calls, workflows, pipelines and tasks.
Start here
Send a message
POST /v1/send with the key from Developers in your dashboard. Live today.
Quickstart
From an installed app to a sent message in five steps.
Custom integrations
What an app is, what you get when it is registered, and how a user installs it.
Authentication
The OAuth 2.0 flow: install URL, callback, token exchange, refresh and revocation.
What you can build
| Operation | Reference |
|---|---|
| Send a text with one header | Send a message |
| Send, schedule, react to, edit and unsend messages | Messages |
| Read the inbox and a contact's thread | Conversations |
| Create and update contacts, tags, notes and Do Not Disturb | Contacts |
| List every line with its health | Devices |
| Message iMessage groups | Group chats |
| Place calls and read call history | Calls |
| Build workflows and add contacts to them | Automations |
| Move deals through pipelines | Opportunities |
| Receive inbound messages at your URL | Inbound webhooks |
How it works
Register your app. On the Custom integration page of the dashboard,
or through Blue Reacher support. You receive a client_id and a
client_secret, and you set your redirect_uri and scopes.
Install it. A Blue Reacher user opens your install URL, reviews the scopes and selects Install. Exchange the code for an access token.
Call the API. Every request carries
Authorization: Bearer <ACCESS_TOKEN>. Probe the token first, then read
contacts and send.
Listen. Set an inbound webhook URL on the workspace, and follow outbound delivery by polling the message.
curl https://api.bluereacher.com/v1/integration/me \
-H "Authorization: Bearer <ACCESS_TOKEN>"A 200 here means the install and the token both work.
curl -X POST https://api.bluereacher.com/v1/messages \
-H "Authorization: Bearer <ACCESS_TOKEN>" \
-H "Content-Type: application/json" \
-d '{
"workspace_id": 7,
"phone": "+15551234567",
"channel": "default",
"message": "Hello from the Blue Reacher API"
}'Workspaces, devices, channels, contacts, messages and conversations are defined once in Key concepts.
Going to production
API reference
Base URL, authentication, conventions and the full route table.
Scopes
Every scope, what it unlocks, and the 403 you get without it.
Rate limits
The request budgets, the usage headers, and how to handle a 429.
Errors
The error body, every status the API returns, and what to do next.
Deliverability
Keep lines healthy over months: sending patterns, sustainable volume, reply rate and recovery.
Compliance
Consent, TCPA and what no A2P registration does and does not cover.