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, journeys, inbox, voice, email, and AI Agent Studio are console products — APIs coming soon. My CDP identity and opt-in: My CDP.

How to start

Work through these in order. Each item is also in the Start group in the sidebar.

  1. 1Send one SMSAPI key, base URL, and POST /v1/sms.
  2. 2Authenticateapikey header on every request. Not Bearer.
  3. 3Match deliveryStore messageId. DLR and inbound arrive later.
  4. 4Read errorsHTTP status, failed sends, and when to retry.
  5. 5Follow a recipeSMS, WhatsApp template, OTP, RCS, webhooks.
  6. 6Watch changesWhat shipped in the docs. Contracts stay stable unless noted.

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

Host

https://api.azmarq.com

$API_BASE_URL for every send.

Auth

apikey

Header on every call. Not Bearer.

Live HTTP

SMS · WhatsApp · RCS · OTP

Same apikey. Store messageId. Delivery arrives on webhooks.

CPaaS APIs on the way

CTWA, journeys, inbox, voice, email, and AI already run on the Azmarq console. HTTP contracts are not published yet — no Try it, no guessed payloads. My CDP identity and opt-in are on My CDP; the contacts API is still coming.

Acquire

Coming soon

CTWA Ads

Click-to-WhatsApp Ads (CTWA) are documented as a portal product on the WhatsApp App guide: account setup, campaigns, ads, and leads. There is no public apikey HTTP API for campaign objects — do not call CTWA as POST /v1/whatsapp.

Read the CTWA guide →

Know

Coming soon

My CDP

Contacts, opt-ins, attributes, and segments that power every channel. Portal is live. Add leads with a public form slug or inbound webhook. There is no POST /v1/cdp list/send API.

Read the My CDP guide →

Engage

Coming soon

Customer Journeys

Multi-channel orchestration with waits, branches, goals, and DND-aware timing. Enrollment comes from CDP entry rules. 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

Team Inbox is documented as a portal product: WhatsApp and RCS queues, assign, reply, and handoff to Automations. There is no public apikey inbox API — do not call agent JWT routes as a customer developer API.

Read the Team Inbox guide →

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 on POST /v1/whatsapp. Commerce catalogs and Meta WhatsApp Flows are portal products on the WhatsApp App guide. There is no public /v1/commerce HTTP send route.

Read Commerce and Flows →

Engage

Coming soon

Channel fallback

Fallback Routing is documented as a portal product: create a rule, pick statuses, enable it on SMS / WhatsApp / RCS compose. There is no public apikey API to create or fire fallback rules.

Read the Fallback guide →

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

Message lifecycle

1

Authenticate

Create a developer key. Send it as the apikey header on every call.

2

Send

POST SMS, WhatsApp, or RCS. HTTP 200 with error null means the job was accepted.

3

Keep messageId

Store data[].messageId with your own user or order id. You will join webhooks on it.

4

Listen

Webhooks (or Number report) carry delivered, failed, read, and inbound. 200 on send is not delivery.

Status codes and retry rules are on Errors. Event payloads are on Webhooks. Copy a full path on Recipes.

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?