Run one command, paste the URL into Stripe, GitHub or anything else that sends webhooks, and watch them arrive. Add --to 3000 and each one is delivered to your local server too. Missed one while your server was down? Replay it.
$ hook --to 3000
https://k3m9xq2a.hook.stoff.dev → localhost:3000
Requests appear below. Watch in a browser: https://hook.stoff.dev/k3m9xq2a#5Yc0…
POST 200 /stripe 31ms
POST - /stripe nothing answered on localhost:3000- One command.
hookgives you a URL that records every request and repliesok. - Delivered to localhost.
hook --to 3000sends each request to your server as it arrives, with its method, path, headers and body. - Replay anything. Send a recorded request again, signature headers and all, even if it arrived while your server was down.
- Watch in a browser. Each hook has a link that shows requests live, with headers and bodies.
- Scriptable. Create a hook and read what arrived with plain curl, so scripts and AI agents can use it too.
- Picks up where it left off. Laptop sleeps, Wi-Fi drops, hook reconnects and delivers what it missed.
brew install stoffbergie/tap/hookFor direct Linux downloads, the GNU x86_64 and ARM64 archives require glibc 2.38 or newer. The hook-x86_64-unknown-linux-musl.tar.gz archive does not depend on glibc. No ARM64 musl archive is published.
| Do this | With |
|---|---|
| Get a URL and watch it | hook |
| Also deliver to localhost:3000 | hook --to 3000 |
| Replay the latest request | hook replay stripe --to 3000 |
| Pick up a hook created earlier | hook watch stripe --to 3000 |
| Keep the same URL every time | hook --name stripe |
| List and delete hooks | hook ls, hook rm stripe |
Fixed names need the owner token, set once with hook config --token <token>.
Catch webhooks with curl, for scripts and AI agents
Create a URL. The response has the URL, an X-Hook-Key header and an X-Hook-Watch link:
curl -i -X POST https://hook.stoff.devSend it anything. It records the request and replies ok:
curl https://<name>.hook.stoff.dev/stripe -d '{"paid":true}'Read what arrived, as JSON:
curl -H 'Authorization: Bearer <key>' https://hook.stoff.dev/<name>
curl -H 'Authorization: Bearer <key>' https://hook.stoff.dev/<name>/requests/<id>Delete it:
curl -X DELETE -H 'Authorization: Bearer <key>' https://hook.stoff.dev/<name>Add -H 'Accept: application/json' when creating to get JSON back. Errors are plain text: 401 missing key, 403 owner only, 404 unknown hook, 429 too many requests. curl https://hook.stoff.dev prints the full usage.
Hook URLs only ever reply ok, so anyone can create one and nothing can be served from the domain. Reading a hook's requests needs its key, which stays in the # part of the watch link and never appears in server logs. Delivery to localhost happens on your machine, not on the server. Hooks and everything they recorded are deleted 7 days after their last request.
| Item | Limit |
|---|---|
| Lifetime | 7 days after last use |
| Requests kept | Latest 100 per hook |
| Body kept | 1 MB per request |
| New hooks | 30 per minute per IP |
sequenceDiagram
participant Sender as "Stripe, GitHub, …"
participant Hook as "Worker + Durable Object"
participant CLI as "hook CLI"
participant App as "localhost:3000"
CLI->>Hook: "watch over WebSocket"
Sender->>Hook: "POST https://k3m9xq2a.hook.stoff.dev/stripe"
Hook->>Hook: "record request"
Hook-->>Sender: "ok"
Hook->>CLI: "new request"
CLI->>Hook: "fetch headers and body"
CLI->>App: "POST /stripe"
One Cloudflare Worker serves the website, the API and every *.hook.stoff.dev URL. Each hook is a Durable Object that stores its latest requests in SQLite and tells anyone watching when a new one arrives. The CLI is a small Rust binary that prints each request and, with --to, sends it on to your local server.
Requires Vite+ and Rust.
vp install
vp dev
cargo run --manifest-path cli/Cargo.toml -- --help| Command | What it does |
|---|---|
vp dev |
Run the Worker locally |
vp run check |
Format, lint and type-check both halves, then run the end-to-end tests |
vp test |
End-to-end tests with the real Worker, the real CLI and local servers |
vp build |
Build the Worker for deployment |
Pushing to main runs the checks, deploys to Cloudflare and smoke-tests production. Pushing a v* tag builds the CLI for macOS, Linux and Windows, and the Homebrew tap picks up the new release within the hour.
MIT © Dirk Beukes