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

# Replay delivery

> Enqueue a fresh delivery from the same source row

Enqueues a fresh delivery with the same payload + subscription. Worker picks it up within \~2 s; new delivery gets its own `Teel-Delivery-Id`.

Use this for:

* Debugging your verifier — drop a row, fix the bug, replay, watch it land.
* Recovering from a long outage on your side — walk the `permanently_failed` deliveries and replay them once your endpoint is healthy.

<Info>**Scope** `webhooks:write` · rate-limited</Info>

## Headers

<ParamField header="Authorization" type="string" required>
  API key.
</ParamField>

## Path parameters

<ParamField path="id" type="string" required>
  Source delivery UUID.
</ParamField>

## Response

<ResponseField name="id" type="string">
  UUID of the new delivery row.
</ResponseField>

<ResponseField name="subscriptionId" type="string">
  Inherited from the source delivery.
</ResponseField>

<ResponseField name="eventType" type="string">
  Inherited from the source delivery.
</ResponseField>

<ResponseField name="status" type="string">
  Always `pending` on a freshly enqueued replay.
</ResponseField>

<ResponseField name="attemptCount" type="integer">
  Always `0` — this is a brand-new delivery row, not a retry of the source.
</ResponseField>

<ResponseField name="nextAttemptAt" type="string">
  ISO 8601 timestamp of the first attempt (≈ now).
</ResponseField>

<ResponseField name="createdAt" type="string">
  ISO 8601 timestamp.
</ResponseField>

<ResponseExample>
  ```json 200 theme={null}
  {
    "id": "deabb47c-b3c4-4777-867c-cc32c434957c",
    "subscriptionId": "1c84203c-b4e3-40de-83a9-51bc0d9c991f",
    "eventType": "payout.status.updated",
    "status": "pending",
    "attemptCount": 0,
    "nextAttemptAt": "2026-05-27T09:34:50Z",
    "createdAt": "2026-05-27T09:34:50Z"
  }
  ```
</ResponseExample>

## Rate limit

To prevent self-inflicted DoS, replays are capped per account: **5 per minute, burst 5**. Over the limit returns `429 Too Many Requests` with a `Retry-After` header (seconds).