Queuey docs — reliable webhook delivery
Queuey is the async queue for your API — in front of it for what comes in, behind it for what goes out. You POST webhooks and events to a queue over HTTP; Queuey verifies and stores them, answers at once, and delivers them to your target at the pace you set — with retries by failure type, a dead-letter queue, idempotency, HMAC & OAuth2 signing, and per-key ordering — then gives you the tooling to diagnose and replay anything that fails.
What Queuey gives you
Failed webhook deliveries retry with exponential backoff and jitter, classified by failure type, then land in a DLQ you can inspect and replay.
Inbound dedup on the Idempotency-Key, outbound key threading, and Hold-on-timeout so a non-idempotent receiver never gets duplicate side effects.
Sign outbound requests with HMAC, or authenticate to the target with OAuth2 client credentials — including private_key_jwt with a P12 certificate.
Process events for each key in strict order, in independent lanes, without head-of-line blocking across keys.
API-key or HMAC signed-request auth, a source-IP allowlist, idempotency, and loop prevention on every event you POST.
Diagnose failing targets, see incident and after-action reports, and replay events — Queuey is built to operate delivery, not just attempt it.
Where to go next
- Quickstart — send your first event with curl, TypeScript, or C#.
- Core concepts — tenants, queues, the policy cascade, and the event lifecycle.
- Reliable delivery — retries, idempotency, Hold-on-timeout, and the dead-letter queue.
- OAuth2 & private_key_jwt — certificate-based delivery auth for regulated targets.
- API reference — ingress, auth, queues, events, and metrics endpoints (in the console).