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

# Resend a webhook

> Send an event again from the dashboard or the API, and know which id your server will receive.

Resend an event when your server missed it: your endpoint was down, your handler failed, or you fixed a bug and want the event again.

There are two ways to do it, and they behave differently.

| | Retry from the dashboard | Resend from the API |
| - | - | - |
| What is sent | The same event, unchanged | A new event about the same transaction |
| Event `id` | The same `evt_` id as before | A new UUID on every resend |
| Field names | snake\_case | camelCase |
| `data` | The full transaction | A summary |
| Use it when | A delivery failed and you fixed the cause | You need an event for a finished transaction |

## Retry from the dashboard

**1. Open the event log**

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

**2. Find the event**

Filter by **Failed** or **Dead**, then find the event by type and date.

**3. Send it again**

Select **Retry** on the row. The dashboard confirms with **Retry queued**.

**4. Check the result**

Refresh the list. The event reads **Delivered** when your server answers `2xx`, and the attempt
count goes up by one.

**Retry** appears on events that are **Failed** or **Dead**. To send again from the delivery itself, select **View** and then **Resend** in the dialog, next to the request and response.

An event that is already **Delivered** cannot be retried. Your server has it. If you need it once more, use the API resend below.

> [!NOTE]
>
> A retry re-sends the same event with the same `id`, signed with a fresh timestamp. If your handler
> records event ids, it will recognise a duplicate and skip it, which is what you want.

## Resend from the API

Ask Payve to send a fresh event for a finished transaction. Use the numeric transaction `id` in the URL.

```bash Payout
curl -X POST "$PAYVE_API_URL/v1/payouts/1842/resend-webhook" \
  -H "x-api-key: $PAYVE_API_KEY"
```

```bash Pay-in
curl -X POST "$PAYVE_API_URL/v1/payins/2107/resend-webhook" \
  -H "x-api-key: $PAYVE_API_KEY"
```

```bash Conversion
curl -X POST "$PAYVE_API_URL/v1/conversions/1990/resend-webhook" \
  -H "x-api-key: $PAYVE_API_KEY"
```

| Request | Scope needed |
| - | - |
| `POST /v1/payouts/{id}/resend-webhook` | `payouts:write` |
| `POST /v1/payins/{id}/resend-webhook` | |
| `POST /v1/conversions/{id}/resend-webhook` | `conversions:write` |

> [!WARNING]
>
> A resend from the API is a **new event** with a new `id`. A check on the event id will not
> recognise it as a duplicate. Before you act on it, check the transaction's own state in your
> system. See [Resent events](/webhooks/event-samples.md#resent-events) for the payloads.

## After your endpoint was down

1. Fix the endpoint and confirm it answers `2xx`.
2. In the event log, filter by **Failed**, then by **Dead**.
3. Select **Retry** on each event you still need.
4. For anything you cannot find, fetch the transaction with a `GET` and reconcile from its status.

## Make resends safe

A resend must never pay someone twice or credit an order twice. Two rules cover it:

* Record each event `id` you process, and skip one you have seen.
* Before you act on any event, check whether your own record of that transaction is already final.

[Handle events safely](/webhooks/handling-events.md) has working code for both.
