Skip to main content
With the iBubbl API, your software sends real iMessages, the blue bubbles, from a dedicated line that iBubbl runs for you, and gets every reply pushed to your server, usually within a minute. There’s no Mac, Apple ID or phone to manage on your side.
  • Send messages to one contact or to a group, from your iBubbl line. When the recipient can’t be reached on iMessage, the message goes out as a text instead, and its channel tells you which.
  • Receive replies and status changes as webhooks: inbound messages, sent / delivered / read, reactions, edits and opt-outs.
  • Keep contacts in sync: create, update and tag them.
  • Stay compliant by default: opt-outs, each contact’s sending hours and your line’s send limits are enforced for you.
The API is HTTPS and JSON, authenticated with one Bearer API key. There’s no SDK to install: any HTTP client works.
The API answers 202 Accepted right away; the message then goes out from your line, and its progress arrives as webhook events. The Quickstart walks through it end to end, sending to your own phone.
Every request is live: there is no sandbox or test mode, and a send delivers a real message. You need an active iBubbl line before you can send; iBubbl sets it up for you.

​
Base URL

All endpoints are under /v1. See Versioning for what can and can’t change within it.

​
Where to go next

Quickstart

Create a key, send to your own phone, check the status, receive a reply.

Authentication

API key format, rotation and security practices.

Webhooks

Get replies and status changes pushed to your server.

API reference

Every endpoint, with request and response schemas.

Build with AI

llms.txt, Markdown pages, the docs MCP server and a system prompt for coding agents.

Support

Email us, and what to include so we can answer quickly.