Use case · Local Development
Webhooks on localhost, without the tunnel dance.
Stop redeploying just to test a webhook handler. Capture real production payloads, replay them at will, and forward to your dev server in one command.
What's painful today
- Ngrok tunnels expire, leak, and need re-configuring on every provider dashboard.
- Triggering real events (charge succeeded, PR opened) just to test a code path wastes Stripe test data and clutters logs.
- Most webhook tools show payloads in a polling UI — your handler hits a 5-second feedback loop.
How HookSense solves it
One command, no tunnel config
`npx hooksense listen -p 3000` connects to your endpoint and pipes incoming requests to your local server. No DNS, no port forwarding, no provider dashboard updates.
Replay any captured request
Trigger the event once in your provider's sandbox, then replay it 50 times against localhost while you iterate on the handler — edit headers and body inline before each send.
Sub-50ms delivery
WebSocket streaming means the payload hits your local server while the upstream provider is still finishing its response. No polling lag, no refresh.
See it in code
Forward production webhooks to localhost:3000
npm install -g hooksense
hooksense login
hooksense listen --slug your-endpoint --port 3000
# every captured webhook is now POSTed to http://localhost:3000FAQ
Do I still need ngrok?
No. The HookSense CLI replaces ngrok for webhook use cases. Your endpoint stays at hooksense.com (no DNS work) and the CLI forwards captured requests to localhost over a persistent WebSocket.
Can I forward to a port other than 3000?
Yes — pass `--port 8080` (or any port). The CLI works with any HTTP server: Next.js, Express, Rails, FastAPI, Hono, you name it.
What happens when my laptop sleeps?
Webhooks keep being captured on the cloud endpoint. When you reconnect, you can replay everything that arrived while you were offline.