---
title: "Retry a webhook delivery"
method: POST
path: "/v1/webhook-deliveries/{delivery}/retry"
tags: ["Webhook Deliveries"]
---

# Retry a webhook delivery

`POST /v1/webhook-deliveries/{delivery}/retry`

## Request

- Base URL: `https://api.subscriby.net`
- URL: `https://api.subscriby.net/v1/webhook-deliveries/{delivery}/retry`
- Auth: HTTP bearer

```bash
curl -X POST https://api.subscriby.net/v1/webhook-deliveries/$DELIVERY_ID/retry \
  -H "Authorization: Bearer $SUBSCRIBY_TOKEN" \
  -H "Idempotency-Key: $(uuidgen)"
```

Answers `200` with the row **pending again**: `attempts` back to `0`, `response_status`, `response_excerpt` and `dead_lettered_at` cleared, and the worker queued. The delivery log then shows the replay's own outcome rather than the original failure's. A retry re-posts the **original** event to its endpoint; nothing new is raised about the replay itself.

> **Only `failed` and `dead` rows can be retried.** Resetting a delivered row would post the event to your server a second time. The dashboard hides its retry button behind the same rule, but a row can be delivered between a render and a click, and the API has no button at all.

## Path parameters

- `delivery` string, uuid, required

## Headers

- `Idempotency-Key` string, uuid, required

## Response `200`

The delivery, pending again.

- object
  - `data` WebhookDeliveryResource, required: One row of the webhook delivery log: one endpoint, one event, the signed envelope that was posted, what the target answered and where the row is on the retry ladder.
    - `id` string, required: The delivery's id, the value the retry endpoint takes.
    - `endpoint_id` string, required: The webhook endpoint the event was posted to.
    - `event` string, required: The event name, as the catalog lists it.
    - `event_id` string, required: The 26-character ULID the envelope's `id` carries without its `evt_` prefix; also the `SB-Event-Id` header the handler received.
    - `status` string, required: `pending` (born, or reset by a retry), `failed` (a non-2xx or transport error while retries remain), `delivered` (the first 2xx) or `dead` (the ladder ran out or the endpoint vanished). `delivered` and `dead` are final until a retry.
    - `attempts` integer, required: Posts made so far. Reset to 0 by a retry.
    - `response_status` integer, nullable, required: The HTTP status the endpoint returned on the last attempt; null before the first post or after a transport failure.
    - `response_excerpt` string, nullable, required: The start of the response body, or the transport error; null before the first post.
    - `payload` unknown[], required: The full event envelope that was, or would have been, posted, so a consumer can be debugged against it exactly.
      - unknown
    - `next_attempt_at` string, nullable, required: When the worker will post a `failed` row again, ISO 8601; null otherwise.
    - `delivered_at` string, nullable, required: Stamped on the first 2xx, ISO 8601; null until then.
    - `dead_lettered_at` string, nullable, required: Stamped when the ladder ran out, ISO 8601; null otherwise.
    - `created_at` string, required: When the row was born, ISO 8601.

## Other responses

- `400`: `IDEMPOTENCY_KEY_MISSING`: every write needs an `Idempotency-Key` header. Send a fresh UUID per distinct operation.
- `401`: `AUTHENTICATION_REQUIRED`: the request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an `sbt_test_` token on production).
- `403`: `TOKEN_MISSING_ABILITY`: the token is valid but does not carry the ability this endpoint requires; `error.context.required_ability` names the one to grant. An endpoint that also checks who owns a row or which tier the account is on answers `FORBIDDEN`, `TEAM_TIER_REQUIRED` or `CONNECTOR_TIER_REQUIRED` with the same status, and says so in its own description.
- `404`: `RESOURCE_NOT_FOUND`: an id in the path names nothing the token can see. `TENANT_MISMATCH`: the project sits outside the token's `scope:project:` allow-list, or the token carries no team scope. Both answer 404 rather than 403 so that existence outside the token's scope cannot be inferred.
- `409`: `IDEMPOTENCY_KEY_REUSED`: the key was already used in the last 24 hours with a different request body.
- `422`: `VALIDATION_FAILED`: for a `pending` or `delivered` row, with the message *Only failed or dead-lettered deliveries can be retried.*
- `425`: `IDEMPOTENCY_REPLAY_IN_PROGRESS`: the first request with this key is still running; retry in a few seconds and the original response is replayed.
- `429`: `RATE_LIMITED`: the token has spent its 300 requests a minute or 10,000 an hour; `Retry-After` says when the next one is accepted.

---

[API](https://skmtc.dev/memberpass/apis/subscriby-rest-api.md) · [All operations](https://skmtc.dev/memberpass/apis/subscriby-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/memberpass/apis/subscriby-rest-api/revisions/59c4df91d764?raw)