Delivery History & Retries

AuthSetu logs every webhook delivery attempt with detailed latency metrics, HTTP status codes, and response bodies, making it easy to debug failed webhooks and inspect delivery state.

Inspecting Delivery Logs via API

Endpoint

GET /v1/webhooks/deliveries?limit=50

Response Schema

{
  "success": true,
  "data": [
    {
      "id": "del_0192837465aa",
      "endpoint_id": "wh_019283746501",
      "event": "verification.completed",
      "target_url": "https://api.merchant.com/webhooks/authsetu",
      "http_status": 200,
      "success": true,
      "attempt": 1,
      "max_attempts": 5,
      "duration_ms": 142,
      "response_body": "{\"received\": true}",
      "error": null,
      "created_at": "2026-10-13T13:30:00Z"
    }
  ]
}

Automatic Retry Policy

When your endpoint returns a non-2xx status code or times out (after 10 seconds), AuthSetu automatically reschedules delivery using exponential backoff with jitter:

| Attempt | Delay | Total Elapsed |

| :--- | :--- | :--- |

| Attempt 1 | Immediate | 0s |

| Attempt 2 | ~15 seconds | ~15s |

| Attempt 3 | ~1 minute | ~1m 15s |

| Attempt 4 | ~5 minutes | ~6m 15s |

| Attempt 5 | ~30 minutes | ~36m 15s |

After 5 failed attempts, the delivery is marked as `failed` and moves to the dead-letter queue. You can manually redeliver any failed webhook at any time from the AuthSetu Console.