Skip to content

Azmarq HTTP API

API Hub

One apikey for SMS, WhatsApp, RCS, and OTP. Send a message, keep messageId, then listen for delivery. Host: https://api.azmarq.com. CTWA, CDP, journeys, inbox, voice, email, and AI Agent Studio are console products — APIs coming soon.

Press ⌘K to search. Auth is the apikey header — not a Bearer token.

CPaaS APIs on the way

CTWA, CDP, journeys, inbox, voice, email, and AI already run on the Azmarq console. HTTP contracts are not published yet — no Try it, no guessed payloads.

Acquire

Coming soon

CTWA Ads

Click-to-WhatsApp campaigns from Meta ads. Leads land in My CDP in the Azmarq console today. The HTTP API for campaign and lead objects is not published yet.

Know

Coming soon

My CDP

Contacts, opt-ins, attributes, and segments that power every channel. Manage profiles in the console until the contacts API ships.

Engage

Coming soon

Customer Journeys

Multi-channel orchestration with waits, branches, goals, and DND-aware timing. Design journeys in the console. No start/stop journey HTTP contract yet.

Engage

Coming soon

Drip Campaigns

Lighter nurture sequences across WhatsApp, SMS, email, and RCS. Console-only until a campaign API is published.

Channel

Coming soon

Email Marketing

Email sits on the Azmarq CPaaS timeline next to SMS and WhatsApp. There is no Omni send-email HTTP route yet — do not post to /v1/sms or /v1/whatsapp for mail.

Serve

Coming soon

Unified Inbox

Omnichannel threads, tickets, queues, and SLAs. Agents work this in the console. Thread and ticket APIs are not exposed.

Scale

Coming soon

AI Agent Studio

Guarded agents with knowledge, tools, evals, window hours, and inbox handoff. Configure agents in the console. No agent-run HTTP API yet.

Scale

Coming soon

Voice 360

Numbers, IVR, inbound/outbound, AI voice, and callbacks. Voice is a CPaaS channel on the Azmarq platform, not an Omni HTTP send API yet.

Scale

Coming soon

Enterprise SMS (SMPP)

Wholesale SMPP binds, routing, and wallets. That is a bind protocol, not REST. HTTP SMS remains POST /v1/sms. SMPP onboarding stays with sales and the console.

WhatsApp

Coming soon

WhatsApp Flows, Payments & Commerce

Template, session, interactive, and group sends are live. Flows, payments, and commerce catalogs are console products until those operations are published.

Engage

Coming soon

Channel fallback

WhatsApp → SMS/RCS fallback is a console journey capability. There is no fallback object on the current send payloads. Keep sending each channel with its own route.

Full list on Coming soon. Live sends stay on API reference.

Message lifecycle

1

Send

POST SMS, WhatsApp, or RCS with apikey.

2

Keep messageId

The HTTP response is accept, not delivery.

3

Listen

Webhooks report delivered, failed, read, and inbound.

Status codes and retry rules are on Errors. Event payloads are on Webhooks.

For agents

Coding agents should read /llms.txt and connect Omni MCP with the same apikey as HTTP. Humans can stay on Recipes or the Reference catalog.

Was this page helpful?