Developers · WhatsApp
Program WhatsApp Business conversations
Send template and session messages, handle inbound replies, and connect chats to your CRM or backend — on Azmarq’s WhatsApp Business stack (Meta Business Partner).
Built for: Backend, growth engineering, and CX platform teams
- Templates & session messaging
- Inbound webhooks
- CTWA → chat handoff
What you can build
01
Outbound messaging
Template and conversation messages for notifications, support, and commerce flows your WABA entitles.
02
Inbound & session continuity
Receive customer replies and keep context for agents, bots, or your own orchestration.
03
Works with the console
Pair API traffic with Unified Inbox, My CDP, and Journeys when teams operate in Azmarq CPaaS.
Quick start
01
Enable WhatsApp on your account
Confirm WABA / number setup and plan entitlements with Azmarq — API access follows account readiness.
02
Create API credentials
Generate keys in the Azmarq console for your environment (sandbox vs production as provided).
03
Send a test template
Use an approved template, then subscribe webhooks for delivery and inbound events.
04
Wire to your app
Map opt-ins, template categories, and handoff rules before you scale campaign volume.
Auth
Credentials from your console
Authenticate with API credentials from your Azmarq console. Never embed production secrets in client-side apps. Confirm live base URL and auth scheme after login — site samples are illustrative.
Illustrative send (shape only)
httpPOST /v1/whatsapp/messages
Authorization: Bearer <AZMARQ_API_KEY>
Content-Type: application/json
{
"to": "+9198XXXXXXXX",
"type": "template",
"template": { "name": "order_update", "language": "en" },
"components": []
}
# Confirm path, fields, and Meta category rules in your console docs.Illustrative only — not a live contract. Confirm paths and fields in developers.azmarq.com.
Common use cases
Order & utility alerts
Push approved templates for confirmations, then continue in-session when the user replies.
CTWA lead capture
Ads open chats; your backend or Azmarq inbox/CDP receives the conversation for follow-up.
Agent + bot hybrid
Automate FAQs via API or AI Agent Studio, escalate to Unified Inbox when needed.
- Meta conversation / category fees are typically separate from Azmarq plan or wallet charges.
- Template approval and quality ratings follow Meta policies — plan launches accordingly.
FAQs
WhatsApp API — FAQs
Integration basics, credentials, and how this API relates to the product console.
Talk to salesRelated but different. WhatsApp API is for integrators sending/receiving programmatically. The WhatsApp Business page covers the full product surface including console workflows.
Typically yes — Azmarq plan/wallet plus Meta category-based conversation fees by market. We don’t publish Meta rate cards on the site.
Yes — many teams keep agents in Unified Inbox while also consuming webhooks in their backend. Confirm packaging with sales.
Build on WhatsApp
Grab credentials in the console, or talk to sales if you need channel enablement, WhatsApp WABA setup, or SMPP packaging.
