Skip to main content
When webhook.co forwards an event to a destination, each attempt is a delivery with a state. Here’s what each means and what to do.

​
Delivery states

You may also see forwarded — that’s the record of replaying an event to your own machine with the CLI (wbhk listen / wbhk replay), where the CLI made the request. It’s not a delivery to a destination, and it doesn’t count as usage.

​
How retries work

A failed delivery retries on a fixed exponential schedule — up to 8 attempts over roughly 32 hours — then becomes dead. A receiver being briefly down never costs you the event, and retries don’t count against your usage (a delivery counts once, when first dispatched). See handle delivery failures for the full schedule.
After 20 consecutive dead deliveries, a destination is automatically disabled and the organization’s owner is emailed. Fix the receiver, re-enable the destination, and owed deliveries resume on the next drain.

​
Diagnosing one delivery

Open the delivery to read its error and the destination’s response. Then fix the receiver and replay the affected events — rather than asking the provider to send them again.

Duplicates, ordering & retries

How order and idempotency work.

Delivery, retries & signing

The engineering detail.