---
title: "Replay a webhook delivery"
method: POST
path: "/webhooks/deliveries/{id}/replay"
tags: ["Webhooks"]
---

# Replay a webhook delivery

`POST /webhooks/deliveries/{id}/replay`

## Request

- Base URL: `https://api.rizamo.com/v1`
- URL: `https://api.rizamo.com/v1/webhooks/deliveries/{id}/replay`
- Auth: HTTP bearer

Sends a delivery again, once and now, through the queue: the body it sent before (made from its event when it never went), signed anew, with the same `webhook-id` (the event's id), so a receiver that has it already can skip it. One more attempt, to the endpoint's `url` as it is now, never retried; it shows among the delivery's attempts. The endpoint must still take the event (its types and profiles now) and be enabled. A delivery still waiting for a retry is refused: it goes on its own. A team replays up to 5,000 deliveries an hour, one at a time and by range together; more answer 429.

## Path parameters

- `id` string, required: The webhook delivery's id (`whd_`).

## Headers

- `Idempotency-Key` string

## Response `200`

OK

- WebhookDelivery
  - `id` string, required
  - `endpointId` string, required
  - `eventId` string, nullable, required: The event it carries, as `List events` gives it and as `webhook-id` names it. Null for a test.
  - `event` union, required: The event's type, or webhook.test for a test.
    - 'post.created' | 'post.updated' | 'post.scheduled' | 'post.unscheduled' | 'post.published' | 'post.failed' | 'post.deleted' | 'post.restored' | 'post.target.published' | 'post.target.failed' | 'post.target.updated' | 'post.target.deleted' | 'comment.received' | 'message.received' | 'message.sent' | 'comment_automation.sent' | 'comment_automation.failed' | 'comment_automation.paused' | 'account.connected' | 'account.disconnected' | 'account.updated' | 'account.removed'
    - 'webhook.test'
  - `status` 'pending' | 'retrying' | 'delivered' | 'failed', required: pending: not tried yet. retrying: tried, and tried again at `nextAttemptAt`. delivered: an attempt got a 2xx. failed: Rizamo stopped trying (all retries used, a 410, an address it does not send to, the endpoint disabled or no longer taking the event, or a delivery it could not prepare).
  - `attempts` WebhookAttempt[], required: Oldest first.
    - `number` integer, required: 1 for the first try.
    - `at` string, date-time, required
    - `responseCode` integer, nullable, required: The endpoint's HTTP status. Null when it did not answer.
    - `durationMs` integer, required
    - `error` 'timeout' | 'unreachable' | 'unsafe_address' | 'redirect' | 'status' | 'endpoint_disabled' | 'endpoint_changed' | 'internal', nullable, required: Null when delivered. timeout: no answer in time. unreachable: the address could not be reached (DNS, connection, TLS). unsafe_address: Rizamo does not send to it (not https, a private or local address, rizamo.com or workers.dev), so it does not retry. redirect: the endpoint answered a redirect, which Rizamo does not follow. status: it answered anything but 2xx. Not sent, and not tried again: endpoint_disabled, the endpoint was disabled meanwhile; endpoint_changed, it no longer takes this event's type or profile (its own, or its person's access, changed); internal, Rizamo could not prepare the delivery.
  - `nextAttemptAt` string, date-time, nullable, required
  - `held` boolean, required: Waiting for its endpoint to answer again (`breaker` open), with no time set: it goes once an attempt to the endpoint is delivered, or as the breaker's next try.
  - `deliveredAt` string, date-time, nullable, required
  - `createdAt` string, date-time, required
  - `payload` string, nullable, required: The body as sent, JSON: the event as `List events` gives it. Null until the first attempt.

## Other responses

- `400`: `invalid_request`: A field is missing or wrong, or the request cannot be done as asked: the message names the field or says what to change.
- `401`: `unauthorized`: No API key or sign-in, or the key does not work: it was deleted, or it expired.
- `403`: `forbidden`: The caller may not do this: the key or agent lacks the scope (the message names it), or the action needs another role or a fresh sign-in.
- `404`: `not_found`: No such object, or it is outside your team or the profiles your key reaches.
- `409`: `conflict`: The object's state does not allow it now, such as an account that needs a new login. `queue_empty`: A post with `queue: true` whose profile has no posting times: set them, or give a `scheduledAt`. `queue_full`: No posting time free for the post's accounts in the next 90 days: add times, or give a `scheduledAt`. `idempotency_key_in_use`: A request with this `Idempotency-Key` is still running: try again in a moment.
- `413`: `payload_too_large`: The body is over 1 MB: files go up through the upload links of `POST /v1/media`.
- `415`: `unsupported_media_type`: The body is not JSON: send it with `Content-Type: application/json`.
- `422`: `capability_missing`: The account cannot do this: see its `capabilities`. `idempotency_key_reused`: This `Idempotency-Key` was used for a different request in the last 24 hours: send a new key.
- `429`: `rate_limited`: Over one of Rizamo's limits, or a network asked Rizamo to slow down: wait for `Retry-After` seconds, or as long as the message says.
- `500`: `internal`: Our side failed: retry, and send the `requestId` if it keeps failing.
- `503`: `timeout`: The request took too long to work out, most often a report: try again in a moment, or ask a report for a shorter period or one profile.

---

[API](https://skmtc.dev/rizamo/apis/rizamo-api.md) - [All operations](https://skmtc.dev/rizamo/apis/rizamo-api/llms.txt) - [OpenAPI document](https://skmtc.dev/rizamo/apis/rizamo-api/revisions/31b0c1b1ffb5?raw)
