[ hook bin ]
see exactly what they sent · payloads stay sealed in an attested enclave
A BIN FOR YOUR WEBHOOKS
create a capture URL, point any webhook or HTTP client at it, and watch every request arrive — live, in full, and nowhere else.
- every request to the capture URL is held for inspection: method, target, headers, body — byte for byte
- webhook payloads carry secrets — Stripe events, tokens, PII. public request bins can read them all; this one runs in a hardware-attested TEE, so the operator can't peek
- captures live in enclave RAM only — never a disk, gone on delete or after 24h idle
- each bin answers its callers with a status, content-type and body you configure
YOUR BINS
remembered by this browser only — the server has no idea whose bin is whose.
CAPTURE URL
connecting…
response sent to callers — status · content-type · body
REQUESTS
waiting for the first request… point a webhook at the URL above. try:
BIN NOT FOUND
no bin answers to — it expired, was deleted, or never existed. bins are client-named, so you can claim this token right here.