The two channels
There are two independent webhook channels, which can be used together or separately.Account webhook — all sends
Account webhook — all sends
Configured once per account in the Dashboard. It fires for all
sends of the account (single API sends, bulk campaigns and flows),
regardless of the campaign. Use it when a single endpoint centralizes the
status of everything the account sends.
Campaign webhook — that campaign only
Campaign webhook — that campaign only
Configured on the bulk campaign itself. It fires only for that
campaign’s recipients. Use it to route the status of a specific campaign to
a dedicated endpoint.
The
sms.sent event is not delivered to webhooks: billing and acceptance
happen at send time, so only final status events are notified. The product is
outbound-only — there is no inbound SMS event.Envelope — account webhook
The account webhook sends the event content insidedata, together with
channel and timestamp at the root level.
Event name (e.g.
sms.delivered). See Events.Delivery details. See the Events page for each
field.
Envelope — campaign webhook
The campaign webhook is flat: the fields sit at the root level and it includescampaignId and recipientId for correlation.
Resulting delivery status. See Events.
Normalized error code in case of failure, or
null. See the code table in
Events.Headers
X-DAPI-Signature is only sent when a secret is configured. It is the
HMAC-SHA256, in hexadecimal, of the request’s raw body.
The
X-DAPI-Webhook-Channel header is sent only in the account webhook.
The campaign webhook sends only Content-Type (plus any custom headers
configured on the campaign) and, when a secret is set, X-DAPI-Signature.Validating the signature
Compute the HMAC over the raw body received (not over re-serialized JSON) and compare it with the header using a constant-time (timing-safe) comparison:Delivery and reliability
The delivery guarantee differs between the two channels.Account webhook — durable queue
Account webhook — durable queue
Delivered through a durable queue, with retries, a per-URL
circuit breaker and delivery logs (
webhook_logs). In case of a
temporary failure, delivery is retried automatically.Campaign webhook — fire-and-forget
Campaign webhook — fire-and-forget
Delivered by a single HTTP call without retries (fire-and-forget). If
the endpoint is unavailable at that moment, the event is not resent.
