Vonage
The Vonage webhook receives SMS delivery receipts from Vonage (formerly Nexmo). These receipts track whether messages were delivered, failed, or are still in transit.
Endpoint
Section titled “Endpoint”POST /api/rpc/webhooks/vonage
Security
Section titled “Security”This endpoint supports JWT or signature verification, depending on your Vonage account configuration.
Supported statuses
Section titled “Supported statuses”| Vonage Status | Platform Event | Description |
|---|---|---|
delivered | sms_delivered | Message delivered to recipient |
failed | sms_failed | Message failed |
rejected | sms_failed | Message rejected by carrier |
accepted | sms_sent | Message accepted by carrier |
buffered | — | Skipped (message buffered) |
unknown | — | Skipped |
expired | sms_undelivered | Message expired |
Payload fields
Section titled “Payload fields”| Field | Description |
|---|---|
message-id | Vonage’s unique message ID |
status | Delivery status |
to | Recipient phone number |
network | Mobile network code |
price | Message cost |
Response
Section titled “Response”{ "success": true, "processed": 1}- In your Vonage dashboard, configure the Delivery receipt URL for your messaging application.
- Set the URL to your platform’s Vonage webhook endpoint.
- Configure signature verification in your Vonage account settings if desired.
Related pages
Section titled “Related pages”- Twilio SMS — alternative SMS provider integration
- Plivo — alternative SMS provider integration
- Webhooks overview — how webhooks work