Skip to content
imessageapi

Review / Platform

Miss Blue logoMiss Blue review

An iMessage API, a shared inbox and a CLI and MCP server, on one line that also falls back and calls.

Miss Blue gives your business a virtual iMessage line and then gives you two ways to work it: an API for building sending and replies into your own product, and a Message Center — a shared team inbox — for people who will never touch code. It also offers CRM workflows and AI agents with human handoff, which puts it closer to a complete platform than to a bare sending endpoint.

What it is good at

  • **The only vendor here with a shared team inbox alongside the API** — the Message Center is what non-engineers actually work in.
  • **The cheapest published dedicated line in the category** at $99/mo, against $250 at Photon and $289 at Blooio.
  • **Automatic RCS and SMS fallback on the same number**, so an Android contact does not need a second vendor or a second line.
  • Ships an `mb` CLI and an `mb mcp` MCP server over the same capability list as the API — rare in this category, and the shortest path to letting an agent send.
  • The sandbox simulates outcomes rather than capping a real number: a scenario header forces delivered, read, reply, failed, offline-queued, rate-limited or timeout, so you can test error handling on demand.
  • Unlimited team seats on the dedicated tier, where competitors charge per line.
  • A free sandbox to build against before paying, though it has no live number.
  • Covers both audiences — an API for developers, a no-code inbox for your front desk.
  • CRM workflow and AI-agent features aim at sales follow-up, not just notifications.
  • A dedicated blue line keeps business threads separate from anyone's personal number.
  • Human handoff on the agent side is the right default for a channel customers reply to.

Where it will bite you

  • **Volume outbound is capped, and enforced.** Fifteen messages a minute per line, and outbound guidance of roughly 30 new conversations a day at a 30%+ rolling reply rate. Their answer to needing more reach is more lines, not a higher ceiling.
  • Headline pricing is promotional; the stated regular rate is $198 per dedicated number.
  • A specific area code is a $205 one-time fee, conversational AI is a $100/mo add-on with $250 setup, and calling is $75–$300/mo per line — none of it is in the base price.
  • The GoHighLevel connector is Beta access rather than a public Marketplace listing, and needs an active dedicated number.
  • Leaving a group thread and editing a sent message are both documented as unsupported through the API.
  • No SOC 2 or HIPAA posture is listed, unlike Linq and Sendblue at their enterprise tiers.
  • A broader platform means more surface area to evaluate than a pure sending API.
  • Published response-rate and revenue figures are the vendor's own; treat them as claims.

What Miss Blue claims

Reported as the vendor's own marketing claims. We have not independently reproduced these numbers, and neither should you treat them as benchmarks.

  • 80% higher response rates than SMS outreach
  • 37% more attributed revenue than SMS outreach

The shape of the API

Illustrative — parameter names and endpoints change. Treat this as the flavour of the integration, and copy the real thing from the official docs.

Send from a Node script
// A send names the line it comes from. GET /v1/numbers lists them.
const res = await fetch("https://api.missblue.dev/v1/messages", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.MISSBLUE_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
number_id: process.env.MISSBLUE_NUMBER_ID,
recipient: "+15551234567",
text: "Your invoice is ready: " + tagged("https://acme.co/inv/8821", {
campaign: "invoice_ready",
}),
status_callback: "https://acme.co/webhooks/missblue",
}),
});
 
// 201 means accepted, not delivered. Delivery arrives on the callback.
if (!res.ok) throw new Error(`send failed: ${res.status}`);

Tracking links with Miss Blue

UTM note

If you use the CRM workflow features, set the UTM convention once at the workflow level so campaigns launched from the inbox tag identically to campaigns launched from your code.

Whatever you send with, build the URL from one helper so tagging is consistent across every job and campaign. Open the UTM builder to generate one now.

Still weighing options?

The comparison table puts all five side by side.