Webhooks
Replay A Webhook Delivery
Re-queue a dead-lettered webhook delivery for a fresh attempt.
POST
Permission Required
This endpoint requires thewebhooks.manage permission (the { kind: "webhook" } scope) on your API key, plus the webhooks feature. Webhooks are gated to api_pro or higher plans: a key on a free plan receives 403 error_api_feature_required.
Access / Membership Rules
Webhooks are owner-scoped. The{id} must resolve to an endpoint in your key’s own derived scope (user, game, or league, depending on your key type), and {deliveryId} must be one of that endpoint’s delivery-log rows. A scope mismatch or an unknown delivery is reported as 404 error_webhook_not_found. Only dead-lettered deliveries can be replayed: a delivered, in-flight, or still-retrying (failed) row returns 409 error_webhook_replay_not_allowed. This route also consumes the per-endpoint token bucket; when it is exhausted you receive 429 error_api_rate_limited with X-RateLimit headers.
What’s Returned
Returns{ "ok": true } once the delivery is re-queued at attempt 1. The new attempt is delivered with the current signing secret and logged against the same idempotencyId.
A still-
failed delivery already has a live scheduled retry, so only terminal dead_lettered
rows are replayable. Find a delivery’s status and id via
List A Webhook Endpoint’s Deliveries. For the
signature scheme and event catalog, see the Webhooks guide.