Webhook Deliveries

Webhook Deliveries is the delivery-level audit surface for callback events.

Dashboard path

Operator Dashboard → Integrations → Webhook Deliveries

Required scope: webhooks:read

Replay scope: webhooks:write

Viewing Polyflight deliveries additionally requires polyflight:read.

What operators can do

• select opinion, polyflight, or explicitly labelled all; the dashboard starts on mixed products when authorized, while the API default remains Opinion
• filter deliveries by status and exact event type
• correlate Polyflight by purchase request, ticket, or external user ID
• inspect endpoint URL and endpoint status
• inspect outbox event ID, aggregate, reconstructed callback envelope/data preview (not the byte-identical signed request), exact minor-unit amounts, delivery attempts, next retry, delivered time, and response sample
• replay an existing delivery after fixing the receiver

Replay behavior

Replay sends the same callback object again. It does not create a new business event.

If a previously accepted delivery with any 2xx is resent, dedupe by its original event_id before applying any downstream effect. A pending Polyflight payout/refund is an obligation, not a confirmed wallet credit. Its fee is included in the stake debit; a full refund/compensation is not another fee.

Polyflight replay can redeliver an event envelope, but it never authorizes or repeats its wallet mutation. A receiver still deduplicates by event_id.

Source API

The page reads GET /api/operator/webhooks/deliveries and replays through:

POST /api/operator/webhooks/deliveries/{id}/replay

The API scopes both the endpoint owner and outbox event owner to the authenticated operator before showing or replaying a delivery.