Skip to main content
Use webhooks to receive real-time notifications in your system whenever a call is completed or a WhatsApp message event occurs from our platform.

Webhook Endpoint

You are required to provide us with a publicly accessible HTTPS endpoint (e.g., https://yourdomain.com/webhook). Our system will send a POST request to this endpoint with the event data.

Request Method

All webhook notifications will be sent using the HTTP POST method with a JSON payload.

Secret Token Authentication

To ensure that the webhook request is coming from an authorized source, a secret token will be included in the request headers. This helps verify that the payload originated from our system and not from a third-party source. The secret token will be shared with you securely during setup and must be validated on your server for every webhook request. Header Example:
On your server, you should verify the token before processing the payload. If the token is invalid, respond with an HTTP 401 Unauthorized status.

Expected Response

Your endpoint should respond with an HTTP 200 status code upon successful receipt and processing of the data. If the response code is not 200, our system may retry the webhook delivery.

Sample Payloads

IdentifierDepending on your campaign type, you will either get a loan_id (for Debt Collection) or a lead_id (for Lead Generation).

Call Webhook Payload

Call webhooks are triggered for the following events: Contacted, No Contact, Failed.When a call is completed, the following payload will be sent to your webhook endpoint:

Field Descriptions


Retry Policy

If the webhook fails (non-200 response or timeout), we will retry up to 2 times with exponential backoff.

Security

It is strongly recommended to verify the webhook source using the provided secret token. All webhook requests will be sent over HTTPS only.
For any questions or configuration changes, please contact our technical team.