Developers · Events
Delivery, inbound, and status events to your URL
Subscribe HTTP callbacks for message delivery receipts, inbound customer messages, and channel status events — so you don’t poll for every update.
Built for: Anyone integrating channel APIs in production
- DLR & status
- Inbound messages
- Retry-friendly receivers
What you can build
01
Delivery receipts
Know when SMS, WhatsApp, email, RCS, or voice attempts succeed, fail, or expire — per channel support.
02
Inbound messages
Receive user replies on WhatsApp and two-way SMS into your backend or Azmarq Inbox.
03
Operational signals
Use events to drive fallbacks (OTP retry), ticket creation, and analytics pipelines.
Quick start
01
Expose an HTTPS endpoint
Public URL that accepts POST JSON; verify signatures if your account provides them.
02
Register the webhook
Configure URL + subscribed event types in the Azmarq console for each channel.
03
Acknowledge quickly
Return 2xx fast; process asynchronously so Azmarq retries don’t stack.
04
Handle retries idempotently
Deduplicate by event/message id so repeated deliveries don’t double-charge side effects.
Auth
Credentials from your console
Prefer signature validation or shared secrets when available. Exact header names and event schemas are confirmed in your console — examples below are illustrative.
Illustrative event payload (shape only)
json{
"id": "evt_01HEXAMPLE",
"type": "message.delivered",
"channel": "sms",
"created_at": "2026-07-26T06:30:00Z",
"data": {
"message_id": "msg_01HEXAMPLE",
"to": "9198XXXXXXXX",
"status": "delivered"
}
}
# Subscribe per channel. Verify signatures when enabled.
# Return HTTP 200 after persisting the event id.Illustrative only — not a live contract. Confirm paths and fields in developers.azmarq.com.
Common use cases
OTP fallback
On SMS failure events, trigger email or voice with the same code.
CRM sync
Push inbound WhatsApp messages into your ticket or CRM system.
Billing & ops
Reconcile delivered vs failed counts against wallet and campaign reports.
- Webhooks complement — not replace — Unified Inbox when humans should operate the thread.
- Enterprise / SMPP CDR workflows may use separate reporting paths — ask sales if you need wholesale reconciliation.
FAQs
Webhooks — FAQs
Integration basics, credentials, and how this API relates to the product console.
Talk to salesTypically delivery/status receipts and inbound messages — per channel support. Exact event names are confirmed in your console.
Return HTTP 2xx quickly after accepting the event; process asynchronously and deduplicate by event/message id on retries.
No. Use webhooks for systems integration; keep Inbox when humans should operate the conversation.
Build on Events
Grab credentials in the console, or talk to sales if you need channel enablement, WhatsApp WABA setup, or SMPP packaging.
