Check webhook logs

On this page, you can learn how to read and analyze webhook logs to monitor delivery and resolve issues.

The following table describes each column in the Webhook logs section.

Field	Description
Triggered Source	Displays a reference link to the Application whose status change initiated the Webhook event.
Webhook	Shows the name and type of the Webhook that was triggered.
Status	Indicates the current delivery status of the Webhook, reflecting whether the event was successfully delivered or if a delivery error was encountered.
HTTP Code	Displays the HTTP response code returned by the receiving server. A code of `200` confirms successful delivery, while codes such as `400` or `500` indicate that an error occurred on the client or server side respectively.
First Sent	Records the date and timestamp of the initial delivery attempt for the Webhook event associated with the Application.
Last Sent	Records the date and timestamp of the most recent delivery attempt, applicable when one or more resend attempts have been made following an initial delivery failure.

View webhook logs

You can view the Webhook logs by navigating to Developer Hub → Webhooks → Webhook Logs.

Click on the corresponding Webhook entry to view further details about the event.
If required — for instance, in the event that a Webhook was not successfully delivered — click "Resend" within the Webhook event row or the details pop-up window to manually trigger redelivery.

Specify what type of webhook you want to find. To do so, use the following filters:

Status — filter by delivery result (for instance, Sent or Permanent Failure).
Webhook type — use this filter to narrow the list by Event type (for instance, APPLICATION_PENDING).

Click on the corresponding Webhook entry to access further details and in-depth information about the event.

If necessary — for example, in the event that a Webhook failed to be delivered — click "Resend" in the Webhook event row or within the details pop-up window to manually initiate redelivery.