Step 01
Generate a URL
One click mints a 12-character session with its own ingestion endpoint. No form, no email, no password.
Free forever · no account · 2-hour purge
SnapHook gives you a disposable HTTPS endpoint that captures every request sent to it — method, headers, query string and body — and streams it to your browser the moment it lands.
Quickstart
Generate a URL, paste it into the provider you are debugging — Stripe, GitHub, Shopify, Twilio, your own cron job — and requests appear in the inspector instantly.
Example request
# send a test payload to your own SnapHook endpoint curl -X POST https://snaphook.site/w/YOUR_SESSION_ID/orders/created \ -H "Content-Type: application/json" \ -d '{"order_id": 4021, "status": "paid"}'
Step 01
Generate a URL
One click mints a 12-character session with its own ingestion endpoint. No form, no email, no password.
Step 02
Send requests
Any method, any sub-path, any content type. Query strings and headers are captured exactly as sent.
Step 03
Inspect live
Captures land in the dashboard as they happen, with JSON bodies pretty-printed. You never have to refresh.
Built for debugging
You get the whole request, not a tidied-up version of it. The method and path, the protocol, where it came from, every header, the parsed query string, and the raw body — with JSON formatting offered on top, never in place of it.
Privacy by construction
Captures are never saved and never copied anywhere. Two hours after your last request and your last open tab, the session and everything in it is gone — no backups, no archive, no way to get it back.
What you get
No signup
No email, no OAuth, no trial timer. Click once and you have an endpoint.
2-hour purge
Sessions self-destruct 2 hours after the last request and the last open tab.
Zero logging
What you send is never saved and never forwarded on to anybody.
100% free
No paid tier gating the features that make it useful. There is no paid tier.
Questions
No. There are no accounts at all. Generating a URL gives you an anonymous session named by 12 random characters, and knowing those characters is the only thing that gets you in.
It stays alive as long as it is being used. A session is purged 2 hours after the last of two things: the last request it received, and the last dashboard disconnecting from it. An open tab keeps a session alive indefinitely.
Any method. GET, POST, PUT, PATCH, DELETE, HEAD and anything else are all captured, along with any sub-path you append to the URL — useful for verifying that a provider is calling the route you expect.
Bodies are captured up to 256 KB. Anything larger is stored truncated and clearly flagged in the inspector, so you still see the beginning of the payload rather than losing the request entirely.
No — and that is true of every webhook testing service, not just this one. Anyone who learns your session URL can read what was sent to it. Use test-mode credentials and synthetic data. Never point a live payment, auth or PII webhook at a public inspection endpoint.
No setup, no install, no card. Your endpoint is one click away.