Skip to main content
Webhooks apply to the V2 OAuth API only. They are separate from Delivery Receipts (DLRs) and Inbound Messages.
When you send an SMS via the V2 API, Phonovation sends an HTTP POST to your webhook URL for each recipient in the request. If you send to 5 numbers in one API call, you receive 5 webhook payloads — one per mobile number. This gives you an immediate, per-recipient status report on how the message was processed — including any errors.

Setup

Provide your webhook URL to support@phonovation.com and we will configure it against your account. The endpoint must:
  • Accept HTTP POST requests
  • Respond with a 200 OK

Payload

Each payload is a JSON object sent in the POST body.

Fields

Status values

CAMPAIGN_ERROR payloads do not include a NotifyId field. The error is campaign-level (e.g. an invalid sender ID), but a payload is still sent for each recipient in the request.

Common Message values

One payload per recipient

Webhooks fire once for each recipient mobile number in the send request, not once per API call.

Tracking recipients with notifyId

Set a notifyId per recipient when sending and it will be echoed back in the NotifyId field of every webhook payload for that recipient. The same value also appears in DLRs and can be used to correlate inbound replies — making it the single identifier that spans your entire send-to-reply flow. If no notifyId is set, the NotifyId field will be an empty string. See notifyId for full details, use cases, and end-to-end flow examples.

Relation to DLRs

Webhooks and DLRs serve different purposes: Use webhooks to confirm your API call was processed correctly. Use DLRs to confirm the message reached the recipient’s device.
Last modified on July 16, 2026