▤ req.is
See exactly what hits your endpoint. Spin up a readable slug URL, point any webhook or API call at it, and read the raw request as it lands — headers, body, timing — then replay it or forward it safely with signed delivery.
the problem
Webhooks fail where you can't see them
"It works on my machine" doesn't help when the payload is the mystery.
When a third-party webhook misbehaves, you need to see exactly what it sent — not what the docs say it sends. req.is gives you a slug URL that stores every byte as it arrived, so you can debug the payload, not guess at it.
POST /b/my-webhook-bin 200 · 8ms
content-type: application/json
stripe-signature: t=1699,v1=5a2f…
{ "event": "payment.succeeded",
"amount": 4200, "currency": "usd" }
› stored · ready to replay
features
What it does
From capture to reproducible code, in one place.
// slug
Readable slug URLs
Pick a slug like /b/my-webhook-bin or let req.is generate one — it takes a suffix if the name's already used.
// capture
Raw capture
Method, path, query, headers, IP, content type and body — stored exactly as they arrived, binary-safe.
// realtime
Live tail
The dashboard tails new requests over SSE, with search, method filters and per-request detail tabs.
// forward
Signed forwarding
Forwarding runs after capture, blocks internal destinations, doesn't follow redirects, and signs every delivery.
// replay
Replay from history
Use any saved request as a reproducible test case against your development or staging endpoint.
// codegen
Code & curl
Turn a captured request into ready-to-run cURL, JavaScript, Python or Go — copy, paste, reproduce.
spec
At a glance
captures
Any method · headers, query, body, IP · stored exactly as sent
live tail
SSE stream · search · method filters · detail tabs
forwarding
After capture · signed delivery blocks internal destinations · no redirects
replay
Any saved request as a reproducible test case
codegen
cURL · JavaScript · Python · Go
version
v2 — faster capture, slug URLs, signed forwarding
operated by
OPERACK — same team, same on-call
Debug the payload, not your patience.
Grab a bin URL, point your webhook at it, and see exactly what's arriving in real time.