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

# Redeliver an event

> Queue the same integration webhook event again for one endpoint, with the same event id. Works on succeeded, exhausted or cancelled deliveries under 30 days.

Queues the same event again for this endpoint, with the same event `id`. The
delivery must be `SUCCEEDED`, `EXHAUSTED` or `CANCELLED` and less than 30 days
old, and the endpoint must be enabled. Because the event `id` does not change,
your receiver should [deduplicate on it](https://docs.qwairy.co/developers/integration-webhooks/overview.md#delivery-guarantees).

Integration webhooks require an active Business, Agency Business or Enterprise plan. Changing an endpoint also requires an API token with write access enabled by an Owner or Manager. See [Integration webhooks](https://docs.qwairy.co/developers/integration-webhooks/overview.md) and [Writing data](https://docs.qwairy.co/developers/writing-data.md).

**Authorization** `string` *required*

Bearer token for your team.

**Idempotency-Key** `string` *required*

Unique key for this operation, at most 255 characters. Completed responses replay for 24 hours.

**webhookId** `string` *required*

Endpoint identifier.

**deliveryId** `string` *required*

Delivery identifier from [List deliveries](https://docs.qwairy.co/developers/endpoints/webhooks/deliveries.md).

## Response

Returns `202` with the queued delivery. The fields are described in
[List deliveries](https://docs.qwairy.co/developers/endpoints/webhooks/deliveries.md).

## Synthetic request and response

```bash theme={null}
curl -X POST "https://www.qwairy.co/api/v1/webhooks/$WEBHOOK_ID/deliveries/$DELIVERY_ID/redeliver" \
  -H "Authorization: Bearer $QWAIRY_API_TOKEN" \
  -H "Idempotency-Key: webhook-redeliver-001"
```

```json theme={null}
{
  "id": "ffffffff-0000-4000-8000-000000000000",
  "eventId": "evt_3f2a9c1e-5b7d-4e08-8a41-0c9d6e2b7f10",
  "event": "run.completed",
  "status": "PENDING",
  "attempts": 0,
  "nextAttemptAt": "2026-10-12T09:00:00.000Z",
  "lastAttemptAt": null,
  "lastStatusCode": null,
  "lastError": null,
  "deliveredAt": null,
  "createdAt": "2026-10-12T09:00:00.000Z"
}
```

## Errors

| Status | Code | Cause |
| - | - | - |
| `404` | `RESOURCE_NOT_FOUND` | The endpoint or delivery is missing or belongs to another team |
| `409` | `CONFLICT` | The delivery cannot be redelivered in its state, or the endpoint is disabled |
| `409` | `IDEMPOTENCY_CONFLICT` | The key was reused with a different request |

See [Error codes](https://docs.qwairy.co/developers/errors.md) for authentication, plan, idempotency and server errors. A token without write access returns `403 API_KEY_READ_ONLY`. On `429`, honor `Retry-After`. If the write limiter is unavailable or writes are suspended, the request returns `503 SERVICE_UNAVAILABLE` and nothing changes.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.