# Webhook Logs

Monitor webhook logs in real-time to track and resolve issues.

<figure><img src="https://835503362-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZxKMBw1IB53ZJ2sltFPC%2Fuploads%2F7kuqoaWOpcOwXJO8TRnP%2Fwebhook-logs.png?alt=media&#x26;token=6249f4b2-105a-478e-b70d-befcc95f1af7" alt=""><figcaption></figcaption></figure>

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

In the YPF SaaS platform, open the **Webhooks** and go to **Webhook Logs** section to view the logs.

You can use the **Status** and **Webhook type** filters to specify what type of webhook you want to find.

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

| Field                | Description                                                                                                                                                                                       |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Triggered Source** | The **Triggered Source** column displays the account ID, user name, and the user email whose triggered the webhook. It can be a hyphen to represent `null`.                                       |
| **Webhook**          | In the **Webhook** column, you can see a name and type of the webhooks that was triggered.                                                                                                        |
| **Status**           | The **Status** column indicates the status of the webhook, whether it was successfully sent or if an error occurred.                                                                              |
| **HTTP Code**        | In the **HTTP Code** column, you get information about 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 (UTC)** | The **First Sent** column provides the date and time of the first attempt to send the webhook for this account.                                                                                   |
| **Last Sent (UTC)**  | The **Last Sent** column provides the date and time of the most recent attempt to send the webhook for this account.                                                                              |

## View & Resend Webhook

Click the **Details** button in the specific webhook log to learn more about this event.

<figure><img src="https://835503362-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZxKMBw1IB53ZJ2sltFPC%2Fuploads%2F58kLGNkCxuCAsAN6sYaf%2Fwebhook-logs%20(sheet%20showed%20-%20success%20event).png?alt=media&#x26;token=ec7fb909-0018-48e5-aac7-0a9779c6716b" alt=""><figcaption></figcaption></figure>

In the popup window, you can view the payload (body of the webhook message) with all the details of the webhook event.

<figure><img src="https://835503362-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZxKMBw1IB53ZJ2sltFPC%2Fuploads%2FJAE59nN6k1JYZCyJiXcU%2Fwebhook-logs%20(sheet%20showed%20-%20failed%20event).png?alt=media&#x26;token=0e7bb3fc-dcb5-49be-b794-894207f395ef" alt=""><figcaption></figcaption></figure>

Additionally, the system provides the body of the error message of maximum 500 characters, allowing you to copy it and investigate the error on your side.

Click **Resend** in the **Details** popup if needed, for instance, if the webhook was not delivered.