Native delivery
Blue bubbles.
Not a workaround.
Send real iMessage from a device you control. V1 stays iMessage-only and fails cleanly for unsupported destinations.
Delivered
Your reservation is confirmed.
BlueText API
iMessage.
Now programmable.
The messages people actually read, now inside your product. Send and receive native blue bubbles through one focused API.
- No credit card
- Bring your own iPhone
- Private beta support
9:41◒ ⌁
SA
Sarah at AcmeiMessageBuilt for connection
Reach people where
conversation already happens.
Native iMessage delivery. Rich media. Real delivery state. No carrier-registration maze.
<1sWebhook target
0Carrier fees
1 APIFocused surface
Everything you need
Powerful by design.
Simple by default.
Blue bubbles.
↗
One request
REST that stays out of your way.
Predictable JSON, stable IDs, idempotent sends, and signed webhooks.
✓
Delivery truth
Sent. Delivered. Read.
Observe native state changes instead of guessing from transport success.
⌘
Agent ready
Built for controlled automation.
Tenant isolation, explicit approvals, audit history, and revocable credentials.
Rich messaging
More than text.
Photos, video, files, voice, threaded replies, and group conversations — delivered at native quality as capabilities ship.
For developers
One endpoint.
One blue bubble.
A small API surface with boring semantics: authentication, idempotency, explicit errors, durable state.
Get developer access# Send one blue bubble curl https://api.bluetext.app/v1/messages/send \ -H "Authorization: Bearer $TOKEN" \ -d '{ "to": "+14155551234", "content": "Your table is ready." }'
await fetch("https://api.bluetext.app/v1/messages/send", { method: "POST", headers: { Authorization: `Bearer ${token}` }, body: JSON.stringify({ to, content }) });
requests.post( "https://api.bluetext.app/v1/messages/send", headers={"Authorization": f"Bearer {token}"}, json={"to": number, "content": message}, )
Private by architecture
Your messages.
Your devices. Your control.
Security is a system property, not a badge.
Private origin
API services stay on a private network behind an outbound Cloudflare Tunnel.
Separate principals
Browser users, devices, and operators use different credentials with no fallback.
Revocable access
Opaque sessions and device credentials are hashed, scoped, expiring, and revocable.
No content logs
Operational logs carry IDs and state — never message bodies or credentials.
Private beta
Start small.
Scale when it works.
Approved beta access is currently free. Production pricing will be published before paid launch.
Developer
Explore the API.
One device. Core API access. Built for prototypes and internal tools.
Request access ›Pro
Ship to customers.
Higher volume, rich messaging, approval workflows, and priority support.
Talk to us ›Scale
Build your platform.
Multiple devices, isolated credentials, dedicated infrastructure, and direct support.
Contact sales ›