Live, no reload.
Every request appears in the list as soon as it's received. If the connection drops, the page reconnects on its own and catches up on anything it missed.
A single URL receives all your HTTP requests — method, headers, query, body — and shows them the instant they arrive. No account. Every request is encrypted, then erased after 24 h without activity.
No sign-up
curl -X POST https://tracehook.dev/h/<your-id> -H 'Content-Type: application/json' -d '{"hello":"world"}'Interface preview: a list of received requests on the left, the detail of the selected request on the right with the Overview, Headers, Query, Body and Raw tabs.
Every request appears in the list as soon as it's received. If the connection drops, the page reconnects on its own and catches up on anything it missed.
Headers in the order received, query, formatted and colored JSON body, forms, binary as hex. You see what the provider actually sent, not what its docs promise.
No account, so nothing ties you to your data. Access hinges on a random identifier. Every request is encrypted before storage and everything is erased 24 h after the last activity. You can also delete it all in one click.
Illustration: the session interface rotates to show the request list, then the detail panel, then the lock and countdown.
GET, POST, PUT, PATCH, DELETE, OPTIONS… and any sub-path.
Replay the exact request from your terminal.
Download a request for a test or a ticket.
By method or by text.
The oldest are dropped automatically.
Headers and body included.
The interface follows your OS.
↑ / ↓ to move through requests.
Lock a session: the link alone is no longer enough to read it.
Per-IP rate limits, so the service stays available for everyone.
Send requests from the browser: the capture route accepts cross-origin calls.
RateLimit-Limit/Remaining/Reset and Retry-After on every throttled response.
Encrypted at rest. Every request is encrypted (AES-256-GCM) before being stored.
Ephemeral. Erased 24 h after the last activity. Deletable immediately.
Nothing is executed. Received content is displayed as text, never interpreted by the browser.
No reflection. The capture URL never returns what it received.
Lockable. Add a password if the link might get forwarded: only an encrypted verifier is kept, never the password. Capture keeps working, only reading is blocked.
Illustration: an encrypted request whose content is only readable under a magnifying glass, then erased after 24 h.
No. Your session's URL is your only access: keep it to yourself.
Up to 24 h after the last activity on the session. After that, everything is deleted.
The last 50. Older ones are deleted automatically.
1 MiB per request, headers included. Beyond that, the request is refused (HTTP 413).
A 200 JSON { "ok": true, "id": "…" }.
Yes, to protect the service. If you hit them, you get a 429 with Retry-After.
Yes, with an optional password. Without it, nobody — even with the link — can read the content. It's never stored in plain text and can't be recovered if you forget it.
Three steps. No setup.
Create a URL.
One click. You get a unique address, for example
https://tracehook.dev/h/3f2c….Send it requests.
Paste the URL into your provider's webhook config, or test it right away: .
Read everything, live.
Method, path, headers, formatted query, body. Copy the request as cURL to replay it. .