> ## Documentation Index
> Fetch the complete documentation index at: /llms.txt
> Use this file to discover all available pages before exploring further.

# Track events

> Use the event log to see every webhook Payve sent, its delivery status, the exact request and your server response.

The event log lists every webhook Payve created for your account in the current environment. Use it to confirm an event arrived, or to find out why it did not.

## Open the event log

Go to **Settings → Webhooks** and select the **Event log** tab.

Each row shows:

| On the row | Meaning |
| - | - |
| Event type | For example `payout.successful`. |
| Status | **Delivered**, **Pending**, **Failed** or **Dead**. See below. |
| Event id | The `evt_` id your server also receives as `id`. |
| Attempts | How many times Payve has tried to deliver it. |
| Last response | The HTTP status your server gave on the last attempt. |
| Date | When the event was created. |

## Read the status

| Status | What it means | What to do |
| - | - | - |
| **Delivered** | Your server answered `2xx`. | Nothing. |
| **Pending** | Created. The first attempt is in progress. | Wait a moment and refresh. |
| **Failed** | The last attempt failed. Payve retries on its own schedule. | Fix your endpoint, or [resend](/dashboard/resend-webhooks.md). |
| **Dead** | Every attempt failed. Payve has stopped trying. | Fix your endpoint, then [resend](/dashboard/resend-webhooks.md). |

Use the filter buttons above the list to show one status at a time. Start with **Failed** and **Dead** when something is missing on your side.

The retry schedule is in [Delivery and retries](/webhooks/delivery-and-retries.md).

## Inspect one delivery

Select **View** on a row. The dialog shows:

* **Status** and **Attempts** for this event.
* **What we sent**: the exact request body Payve posted to your URL.
* **What your endpoint returned**: the HTTP status and the start of the response body your server gave.
* **Error**, when Payve could not reach your server at all.

Compare **What we sent** with what your server logged. If the bodies match and your signature check still fails, you are almost always signing parsed JSON, not the raw body. See [Verify signatures](/webhooks/verify-signatures.md#common-mistakes).

> [!NOTE]
>
> Payve keeps the first 2,000 characters of your server's response. Do not put secrets in webhook
> responses.

## Common results and their causes

| You see | Likely cause |
| - | - |
| Last response `401` or `403` | Your signature check rejected the delivery, or the secret is wrong. |
| Last response `301` or `302` | Your URL redirects. Payve does not follow redirects. |
| Last response `500` | Your handler threw an error. Check your own logs for that time. |
| `Webhook delivery timed out` | No answer within 30 seconds. Answer first, then do slow work. |
| `Delivery failed: the endpoint could not be reached` | A connection, DNS or TLS problem. |
| `blocked_destination` | The URL is not `https`, or it points at a private address. |
| No row at all | No endpoint was enabled in this environment when the event happened, or the endpoint does not include that event type. |

## Find the event for one transaction

Every event carries the transaction in `data`. To match a row to a payment, compare `data.public_id` (for example `pyt_9c2e41b7a05d3f68`) in **What we sent** with the reference shown on the transaction's own page.

## Track events from your code

The same log is available through the API, so you can reconcile without opening the dashboard.

```bash List failed deliveries
curl "$PAYVE_API_URL/v1/webhooks/events?status=failed&limit=25" \
  -H "x-api-key: $PAYVE_API_KEY"
```

```bash Inspect one delivery
curl "$PAYVE_API_URL/v1/webhooks/events/90211" \
  -H "x-api-key: $PAYVE_API_KEY"
```

`GET /v1/webhooks/events/{id}` takes the numeric `id` from the list, not the `evt_` id. Try both requests in the [API reference](/api-reference/overview.md).
