---
title: "Queue a signed replay of a stored webhook delivery"
method: POST
path: "/webhooks/deliveries/{deliveryId}/replay"
tags: ["Webhooks"]
---

# Queue a signed replay of a stored webhook delivery

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

## Request

- Base URL: `https://api.domscout.io`
- URL: `https://api.domscout.io/webhooks/deliveries/{deliveryId}/replay`
- Auth: API key in header `x-api-key`

The original persisted payload and configured signing secret are used. This does not run a browser capture.

## Headers

- `Idempotency-Key` string

## Response `202`

Replay delivery accepted.

- WebhookReplayAccepted
  - `status` 'accepted' | 'pending', required
  - `deliveryId` string, uuid, required
  - `attemptId` string, uuid, required
  - `scheduledAt` string, date-time
  - `replayed` boolean: true when an identical Idempotency-Key request returned an already queued replay attempt.
  - `accepted` boolean
  - `reason` string
  - `message` string

## Other responses

- `400`: The request failed validation.
- `403`: The request was refused. Returned when the x-api-key header is missing, revoked, or invalid, and when a valid key is blocked by a plan entitlement, the trusted-JavaScript account entitlement, a global product pause, or a security policy. A plan-only restriction returns code PLAN_FEATURE_UNAVAILABLE and can include upgrade_url. FEATURE_NOT_ENABLED identifies either the global product emergency pause or an eligible Business account without trusted-JavaScript permission; it carries no upgrade_url, so upgrading or retrying cannot clear it. Browser capture can return BROWSER_ISOLATION_REQUIRED or BROWSER_EXECUTION_DENIED with reason public_capture_not_enabled when browser work is unavailable for your account. These platform restrictions carry no upgrade_url and are not resolved by changing plan or key. Check GET /credits for current account capabilities. The API does not use 401: it authenticates with an API key header rather than an HTTP authentication scheme, so there is no WWW-Authenticate challenge to issue.
- `404`: The resource does not exist, has expired, or is not owned by this API key.
- `409`: The Idempotency-Key was already used with a different request body.
- `503`: A dependency this request needs is unavailable or not configured for this deployment. Codes: SUPABASE_TIMEOUT and SUPABASE_INVALID_RESPONSE (a storage operation did not answer, or answered unreadably — the write may have committed, so any retry must be idempotent), CAPTURE_ARTIFACT_UNAVAILABLE and CAPTURE_ARTIFACT_CORRUPT (a stored artifact could not be read or parsed), ASYNC_JOBS_NOT_CONFIGURED and CAPTURE_RETRIEVAL_NOT_CONFIGURED (the capability is not configured here, on any plan). Retryable unless the code names a deployment configuration.

---

[API](https://skmtc.dev/domscout/apis/domscout-api.md) · [All operations](https://skmtc.dev/domscout/apis/domscout-api/llms.txt) · [OpenAPI document](https://skmtc.dev/domscout/apis/domscout-api/revisions/20562d5b5d94?raw)