Webhook for the Verify API
Prelude Verify API can notify your application about events using webhooks. Get notified when your messages are delivered and billed.
Prelude can notify your application about events using webhooks. You can configure a webhook URL using the callback_url
parameter of your request.
The event object
The unique identifier of the event.
The type of the event, possible values are:
Type | Description |
---|---|
verify.authentication | A verification was created and billed |
verify.attempt | A verification attempt was sent to the user |
verify.delivery_status | Sent when we receive a delivery status from the carrier |
The payload of the event, whose structure depends on the event type.
The timestamp of the event creation.
How to set up your Webhook
To start receiving webhook events in your app, create and register a webhook endpoint by following the steps below. You can register and create one endpoint to handle several different event types at once, or set up individual endpoints for specific events.
Implement the handler
Develop a webhook endpoint function to receive event data POST requests.
Pass the URL
Add your webhook endpoint URL to your Verification requests to start receiving events.
Return OK
Return a 200 OK
HTTP response to the POST request to acknowledge receipt
of the event. If you don’t, Prelude will retry sending the event for 2
weeks.
Delivery Statuses
When we receive a delivery status from the carrier, we send a webhook event with the verify.delivery_status
type. The status field in the payload indicates the current state of the message delivery.
Here are the possible status
values:
Status | Code | Description |
---|---|---|
Submitted | submitted | The message has been submitted to the carrier. |
In Transit | in_transit | The message is in transit to the recipient. |
Delivered | delivered | The message was successfully delivered to the recipient. |
Undeliverable | undeliverable | The message could not be delivered to the recipient. |
Unknown | unknown | The delivery status cannot be determined due to unspecified issues or lack of detailed information from the carrier or network. |