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 (default), polyflight, or explicitly labelled all
• 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, payload preview, 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 sent delivery with HTTP 200 is replayed, the dashboard shows this warning:

This will resend the same callback object, ensure your system is idempotent to avoid duplicated events

Receiver code must dedupe by event_id.

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.