instant urls
generates a unique, temporary endpoint instantly. no accounts or configuration required.
catch and inspect webhooks without deploying code.
httpwut provides a temporary URL that logs everything sent to it. it shows headers, query parameters, and raw body payloads in real time.
httpwut is an http request inspector and webhook debugger. it gives you a unique, temporary url. anything POSTed to that url is parsed and displayed on your screen, complete with headers, body content, and timing metrics.
debugging third-party webhooks by logging to your production console is a terrible workflow. setting up a local tunnel like ngrok is sometimes overkill just to see the shape of a json payload. httpwut gives you instant visibility with zero configuration.
if you are integrating Stripe, GitHub, or any service that pushes data to your servers, you need to know exactly what they are sending. httpwut sits in the middle and records the raw truth.
generates a unique, temporary endpoint instantly. no accounts or configuration required.
displays the exact payload sent by the client. supports json, form-data, and plain text.
lists every http header included in the request. useful for debugging authentication signatures.
records the exact timestamp and latency of incoming requests. helps identify slow webhooks.
pipe incoming requests directly to your terminal. watch webhooks arrive in real time.
start a local session to catch incoming webhooks.
// input
httpwut listen
// output
listening on https://httpwut.com/x/9f8a2b
[14:02:11] POST /x/9f8a2b
headers: { 'content-type': 'application/json' }
body: { "status": "paid" }
the command generates a unique url and streams incoming requests directly to your terminal.
debugging webhooks from third-party payment providers used to involve deploying a temporary logging endpoint to staging. it was a massive waste of time just to see the exact structure of a json payload.
we built this because existing tools either require you to create an account or they rate-limit you immediately. httpwut is just a dumb pipe that prints whatever you throw at it.
endpoints expire after 24 hours of inactivity. we do not store your payload data permanently.
yes. you can configure the endpoint to return a 400 or 500 status code to test how the third party handles retries.
no. it does not forward traffic to your localhost. it just catches the request and displays it in the interface.
yes, but it will display as a hex dump. it is mostly designed for text-based payloads like json and xml.
// see exactly what the webhook actually sent.