Requeue

Client-only · talks to your core API

Dead-letter inbox

Connect this browser to the hosted API at api.getrequeue.com — or a core you run yourself. Create an ingest endpoint, copy an existing ingest or relay URL from Your endpoints (edit a target, set an alert URL, or retire one anytime), then inspect and replay failures — edit the payload for that delivery only if you need to. Dismiss one event, or several, when you will not replay them. Credentials stay in this browser's localStorage. This page has no backend.

Connect

Leave the base URL as https://api.getrequeue.com unless you self-host. Paste the API key you were given — never a sample or committed secret. The key is sent only to that API as Authorization: Bearer. After Connect, mint or revoke extra keys in API keys below.

No key yet? Join the waitlist or write [email protected] first.

API keys

Not connected

Management keys for this project. The list shows id, name, and created time — never a hash or raw token. Create another key, copy the token once, then revoke one if it leaks.

Connect to load your API keys.

Connect to api.getrequeue.com (or your own core) to list management keys for this project.

Create endpoint

Connect first, then mint an ingest URL on that API. Point a worker at the ingest URL, or paste the relay URL shown on the endpoint as a Stripe or Clerk webhook URL. Failures land in the inbox; Replay sends the stored payload to your target URL now, or Edit payload and replay a JSON override for that delivery only. Queue replay marks pending_replay for the outbox cron. Optional alert URL is an absolute https:// address — after ingest stores a failed event, Requeue fire-and-forgets one small JSON POST (no payload or headers), and a missed alert never fails ingest. No curl required.

Your endpoints

Not connected

Endpoints already minted on this API key. Each ingest URL is the connected base URL plus ingest_path (typically /v1/ingest/…). Each relay URL is that base plus /v1/relay/ and the endpoint key — paste it as a Stripe or Clerk webhook URL. Edit name, target URL, alert URL, or HMAC secret. Leave the alert URL empty to clear it. Alerts are fire-and-forget: a missed alert never fails ingest. Retire soft-deletes the destination — ingest and relay then return 410. The ingest key is not rotated.

Connect to load your endpoints.

Connect to api.getrequeue.com (or your own core) to list your ingest endpoints.

events
Not connected

Connect first, then wait for a failure.

Paste a hosted key, create an endpoint, and point a webhook or the JS SDK at the ingest URL. When a delivery 500s or a worker gives up, the corpse lands here so you can inspect and replay it. SDK replay() can override payload or headers for that delivery only — the stored event stays put.

Inspect

Select an event

Headers, payload, and replay attempts land here. Replay re-delivers now. Edit payload to send a JSON override for that delivery only — the stored event stays put. JS SDK replay() can pass the same payload or headers override. Queue replay marks pending_replay for the outbox cron. Replay selected queues every checked row the same way, so a large batch does not time out in the browser. Dismiss marks a failed, replay-failed, or replayed event resolved without delivering it. Dismiss selected does that for every checked row.