Recipe

Replay and recover missed webhooks

If your endpoint was down, you have options. Automatic retries cover a 72-hour window, you can manually redeliver specific events, and for anything past the window you reconcile by re-reading current state from the API.

2 min read

72 hAuto-retry window
Manual redeliveryPer event
Re-fetchPast the window

Lean on automatic retries

Brief outages need no action — deliveries retry on exponential backoff for 72 hours. Once your endpoint returns 2xx, queued events flow through.

Redeliver specific events

For a known-missed event, trigger a manual redelivery from the partner dashboard. It is re-signed with a fresh timestamp, so verification passes normally.

Reconcile past the window

Events older than 72 hours are gone from the queue. Recover by re-reading the affected resources from the API and computing the delta against your own records. Your idempotent handler makes re-applying safe.

Frequently asked questions

How long do I have to recover automatically?

72 hours from the event. Within that window, fixing your endpoint is enough — retries do the rest.

How do I catch up after a long outage?

Re-fetch current state from the read endpoints and reconcile. Do not rely on the retry queue for outages longer than three days.

Funding for UK limited companies

Credicorp lends to your company, not to you personally — short-term working capital with no personal guarantee. See what your business could access.