REST API
Contacts, conversations, messages, catalogue, orders, payments, leads and the pipeline. JSON in, JSON out, one consistent error envelope, and rate limits in standard headers.
Developers
Build on it
Everything the dashboard does is available over HTTP — and over MCP, so an AI client can operate an account as a set of tools. Available on the Growth plan and above.
API keys and scopes
Keys are created per integration and scoped to what that integration needs. Each one is revocable on its own, so a leaked key is a rotation rather than an incident.
Outbound webhooks
New lead, paid order, stage change, inbound message — posted to your endpoint, signed so you can verify them, with retries and a failure queue you can see and replay.
MCP server
Model Context Protocol tools over your workspace, so an AI client can read the inbox, look up a contact, create an order or move a lead with your permission model enforced.
Lead capture endpoint
A narrow, token-authenticated endpoint for web forms and ad platforms. The token can only create a lead on one form and read nothing back, so it is safe in page JavaScript.
WordPress plugin
Drop-in capture for a site you already have: enquiries from your existing forms land in the same pipeline as the WhatsApp ones, with UTM attribution intact.
Getting a key
Sign in, open Settings → API keys, and create one. The key is shown once at creation and stored encrypted afterwards — if it is lost, rotate rather than recover. Keys issued before the product was renamed still work and keep their original prefix; nothing you have integrated needs changing.
Base URLs
The public API is mounted at the root rather than under /api, so third-party URLs stay
short: https://app.omnibriq.com/v1/…. The dashboard's own API lives under
/api/v1/ and is not the integration surface.
Verifying a webhook
Every outbound webhook carries a signature over the raw request body. Verify it before parsing, and compare with a constant-time comparison. If you parse and re-serialise the body first, the signature will not match — that is the single most common integration bug on this kind of endpoint, and it is worth getting right on the first day.
Sandbox
The 14-day trial is the sandbox: a full workspace with every feature and evaluation-sized limits. Build against it, then move the key. There is no separate test environment to keep in sync.
Something unclear in the reference? Tell us at [email protected] — API documentation is one of the few things where "I could not work it out" is always our bug, not yours.
Start selling on WhatsApp this week
Fourteen days, every feature, no card. Or take fifteen minutes with us first and we will tell you honestly whether it fits your business.
Prefer to just ask something? WhatsApp us on +91 82690 09378 or email [email protected].