Check webhook logs
Monitor webhook logs in real-time to track and resolve issues.
This page explains how to read and analyze webhook logs.
To verify that you are receiving the relevant applicant status, check the
createdAtMsfield in the webhook payload.
| Field | Description |
|---|---|
| Triggered source | Displays a link to the applicant whose status update triggered the webhook. |
| Webhook | Shows the name and type of the webhook that was triggered. For more details on webhook types, see User Verification, Transaction Monitoring, Case management, and Fraud Network Detection webhooks. |
| Receiver | The delivery channel the webhook was sent to — HTTP, Slack, Telegram, or Email. |
| Status | Indicates whether the webhook was successfully sent or if an error occurred. |
| HTTP code | Shows the response code from the receiving server — for example, 200 if the webhook was successfully delivered, or 400/500 if an error occurred. |
| First sent | The date and time of the first attempt to send the webhook for this applicant. |
| Last sent | The date and time of the most recent attempt to send the webhook for this applicant, if a resend was needed. |
| Next Scheduled | The date and time of the next retry attempt, if the webhook was not delivered. |
Note that webhook logs are not limited to HTTP deliveries. Email, Slack, and Telegram deliveries appear in the logs the same way, with the same statuses, timestamps, failure count, payload, and error message.
Test webhooksWebhooks sent manually via Test webhook in the Webhook manager appear in the log list like any other webhook and carry
"testMode": truein their payload (visible in the Details popup).The Resend action is not available for them. Resend only applies to production webhooks.
View webhook logs
You can access webhook logs from two places in the Dashboard:
- Dev space → Webhooks → Webhook logs.
- Applicants page → select an applicant → Events block → Webhooks tab.
From either location, you can perform the following actions:
- Use the following filters to narrow results:
- Status — filter by delivery result (for example, Sent for successful deliveries).
- Webhook type — filter by webhook type (for example,
applicantReviewed). - Receiver — filter by delivery channel (HTTP, Slack, Telegram, or Email).
- Webhook name — filter by one or more specific webhook names. Available in:
- Dev space → Webhooks → Webhook logs.
- Applicants page → Events tab → Webhooks.
- Click the Details icon on a webhook log entry to view more information about the event, including the receiver, the number of failures, and the full webhook payload. The error message body is also shown and can be copied for debugging.
- Click Resend in the webhook log entry or the Details popup to retry a failed or undelivered webhook. Resend works for all receiver types — HTTP, Slack, Telegram, and Email.
This option is not available for test webhooks.
Updated 3 days ago