Prelude Verify API can notify your application about events using webhooks. Get notified when your messages are delivered and billed.
callback_url
parameter of your request.
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 |
Implement the handler
Pass the URL
Return OK
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.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. |
rsassa-pss-sha256=
in the X-Webhook-Signature
header of each request to your webhook endpoint.
To enable the webhook signature, go to your Dashboard in the Settings->Keys section and generate a webhook signing key for your application.
You can then verify the signature of the webhook events in your webhook endpoint and process the event only if the signature is valid.