Replay events to a webhook subscription
Re-delivers historical events to the subscription's endpoint. Useful for recovering from outages or backfilling a new subscription.
BEHAVIOR: - Events are delivered in chronological order. - Each delivery is tracked as a new WebhookDelivery with source "replay". - Replay respects the subscription's retry policy. - Concurrent replays to the same subscription are NOT allowed.
LIMITS: - Maximum 1000 events per replay request. - Use from/to to control the replay window.
Authorizations
Administrative API key with full system access. Also accepted as an alternative to ApiKeyAuth on an explicit per-operation allowlist — the authoritative list is the union of operations whose security: block declares AdminKeyAuth (consult per-operation security blocks rather than this prose, which has historically drifted as the dual-auth surface expanded). When using AdminKeyAuth on list or fund endpoints, a tenant scoping parameter (typically tenant or tenant_id) is required for scoping (400 if missing) — the per-operation description specifies which. Lookup-style endpoints that uniquely identify a resource by non-tenant key (e.g. GET /v1/admin/budgets/lookup, where the (scope, unit) pair is unique) do NOT require a tenant parameter. Allowlisting is per-operation (exact method:path matching — no prefix matching, no wildcards) so new endpoints do not accidentally inherit admin-accessible status.
Parameters
Path Parameters
Request Body
Responses
Replay accepted (processing asynchronously)