Platform
Developer API
The whole account, over REST
Contacts, the inbox, messages, templates, broadcasts and the sales pipeline over a versioned REST API — with account-scoped keys, signed webhooks, an OpenAPI spec and reference docs.
- Keys scoped to one account, with twelve granular scopes
- Contacts, inbox, messages, broadcasts and deals
- Signed webhooks, cursor pagination, Idempotency-Key
- OpenAPI 3.1 spec and reference docs at /docs
We reply in under an hourOr message us on WhatsApp
A screenshot of the running product. The names and numbers are invented; the software is not.
01 / 04
Keys that are safe to hand out
Admins and owners create keys in Settings → API keys. A key is displayed in full exactly once and stored only as a SHA-256 hash — we cannot show it to you again, and nor could anyone who reached the database. Each key acts on exactly one account; there is no cross-account access at any scope. A key can carry an expiry, an IP allowlist and a lower rate limit than the account default, and every key has a usage view: which endpoints it called, how often, and what came back. Revocation takes effect on the key's very next request; regeneration issues a new secret without touching the key's configuration.
02 / 04
Scopes, not seats
Authorisation is by scope and is independent of who created the key, so a key issued by an owner is not implicitly an owner. Each endpoint requires exactly one scope, the one the docs show is the one the server enforces, and write scopes include the reads they need — a key that can create a contact can read the contact it created. Responses use one envelope — data on success, a coded error on failure — with a stable code and a machine-readable reason to branch on.
- contacts:read · contacts:write
- conversations:read · conversations:write
- messages:read · messages:send · templates:read
- broadcasts:read · broadcasts:send
- deals:read · deals:write · webhooks:manage
03 / 04
The resources, and the rules they share
Contacts with their tags, custom fields and notes. Conversations with assignment, status and AI handover. Messages — text, template and media — to an existing thread or straight to a phone number. Approved WhatsApp templates. Template broadcasts with per-recipient delivery. Pipelines, stages and deals. Every list pages with the same cursor; every create honours an Idempotency-Key so a retried request cannot send twice; every response carries a request id and the rate-limit headers.
04 / 04
Webhooks, the spec, and the docs
Outbound webhooks push events to your endpoint as they happen, each signed with an HMAC you verify against a per-subscription secret, retried on a schedule and disabled automatically if your endpoint stays down. The whole API is described by an OpenAPI 3.1 document generated from the same definitions that validate requests, so a client generated from it validates exactly what the server does. The reference, the guides and the webhook catalogue live at /docs. For conversational access from Claude, the MCP server exposes the same account without any of this.
Explore more
Works well with
Claude & MCP
Connect Claude to your account — on a leash
Paste a URL into Claude, Claude Code or any MCP client and work with your account in plain language — bounded by exactly what you can already do.
Learn moreAI assistants
It drafts, it replies, it knows when to fetch a human
Draft replies and summarise threads, or hand whole conversations to an assistant that answers within limits you set — and steps aside the moment a person takes over.
Learn moreContacts & CRM
One clean record per customer
Tags, custom fields, notes and CSV import with automatic phone-number deduplication — so every customer is one record, not five.
Learn moreReady to answer every customer in one place?
Bring WhatsApp, Messenger and Instagram together with AI that actually helps. Talk to us and we'll get you set up.
We reply in under an hourOr message us on WhatsApp