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.
What do you want to send?
Pick a job, not a product name. Each card opens the guide or the exact operation.
POST /v1/sms
Send an SMS
Transactional, promotional, OTP, unicode, flash, DLT templates, and short URLs.
Open →
Templates
WhatsApp after approval
Create a template, wait for Approved, then send. Session messages need the 24-hour window.
Open →
Bot
Start an RCS bot
Register a bot, create a card or carousel template, then send to an RCS-capable number.
Open →
POST /v1/verify
Generate and verify OTP
Create a PIN with configId, deliver it, then validate with verifyId.
Open →
Events
Match delivery reports
Store messageId from the send response. Webhooks later emit DLR and inbound replies.
Open →
Walkthrough
Follow a recipe
Step-by-step first SMS, WhatsApp template, OTP, RCS, and webhook matching.
Open →
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 soonCTWA 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 soonMy CDP
Contacts, opt-ins, attributes, and segments that power every channel. Manage profiles in the console until the contacts API ships.
Engage
Coming soonCustomer 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 soonDrip Campaigns
Lighter nurture sequences across WhatsApp, SMS, email, and RCS. Console-only until a campaign API is published.
Channel
Coming soonEmail 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 soonUnified Inbox
Omnichannel threads, tickets, queues, and SLAs. Agents work this in the console. Thread and ticket APIs are not exposed.
Scale
Coming soonAI 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 soonVoice 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 soonEnterprise 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 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 soonChannel 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.
Latest changes
2026-11-06
Zoho CRM and custom CRM connects
Azmarq for Zoho CRM is linked from Zoho Marketplace. Salesforce, LeadSquad, and WebEngage are custom connects — enable with onboarding, no new Omni HTTP routes.
2026-11-06
Marketplace apps in Integrations
Shopify, Google Sheets (Workspace add-on), Integrately, and Pabbly Connect are listed as installable apps. No new Omni HTTP routes.
2026-11-06
Coming soon CPaaS APIs
CTWA Ads, My CDP, journeys, drips, email, Unified Inbox, AI Agent Studio, Voice 360, SMPP, WhatsApp commerce, and channel fallback are listed as Coming soon. No new HTTP routes or payloads.
2026-11-06
Hub, recipes, and agent index
Landing page rebuilt around messaging journeys. New Recipes, Reference catalog, Changelog, and /llms.txt for coding agents.
2026-10-31
Omni SDK, MCP, and Postman
Official clients in seven languages, Omni MCP 0.1.1 with Source-MCP campaign tags, and a forkable Postman collection. Auth is the apikey header.
Full log on Changelog.
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.