Skip to content

Recover failed webhook deliveries with retries and DLQ

Never lose completed AI outputs when your receiver restarts—automatically retry with exponential backoff and inspect dead-letter queues.

Copy the prompt and paste it into the AI assistant you already use.

Steps to make webhook delivery outage-proof

  1. 01

    Distinguish 5xx from 4xx responses

    Retry 429, 502, 503, and network timeouts while surfacing permanent 400 payload bugs quickly.

  2. 02

    Configure jittered exponential backoff

    Spread retry waves with random jitter so a recovering receiver is not hammered simultaneously.

  3. 03

    Monitor dead-letter threshold alerts

    Send an alert whenever callbacks enter the dead-letter queue so engineers spot downstream outages fast.

  4. 04

    Verify idempotent receiver handling

    Ensure your receiver checks job_id before writing DB rows in case a slow response triggers a retry.

Common questions

What happens when our receiver server is down during a deployment?

APIkit detects the 502 or connection error and reschedules callback delivery using exponential backoff until your service recovers.

Can we inspect and replay dead-lettered events later?

Yes. Failed deliveries remain in the dead-letter queue with full headers and error responses for selective or bulk replay.

Will 404 or 401 errors waste retries for days?

You can configure retry rules to stop quickly on permanent client errors like 404 while retrying transient 5xx outages.