Receive your first webhook
- Create a hook.
Sign in, name your hook, and copy the generated URL beginning with
https://hook.tryhookwise.xyz/hook/. - Send it a request.
curl -X POST \ https://hook.tryhookwise.xyz/hook/YOUR_TOKEN \ -H "content-type: application/json" \ -d '{"event":"payment.succeeded"}' - Inspect the result.
Open the hook to see its method, headers, query parameters, body, source, delivery status, and timing.
Your webhook workspace
Hooks
Each hook has a stable public URL and a private request history. Use separate hooks for different applications or providers.
Request inspector
Select any request to inspect its payload and forwarding outcome. Incoming requests appear in real time.
Replay
Resend a captured request to a forwarding target without asking the original provider to emit it again.
Reliability
Track status, latency, retries, failures, and recovery for every configured destination.
Forward hooks to localhost
The CLI opens an outbound authenticated WebSocket to Hookwise. You do not need to expose a local port or change your firewall.
Install
npm install -g @hookwise/cliAuthenticate this device
hookwise loginHookwise opens a browser authorization page. Approve the device, then return to the terminal. The credential is stored in ~/.hookwise/config.json.
Start listening
hookwise listenSelect an existing hook, select or create a Local Agent target, and enter your local forwarding URL. For example:
http://localhost:3002/api/webhooks✓ Listening
Hook https://hook.tryhookwise.xyz/hook/…
Forward http://localhost:3002/api/webhooks
Target 465cee61-fa66-…Start an HTTP tunnel
hookwise http [port]Expose a local HTTP server with a temporary public URL:
hookwise http 3000Running hookwise http without a port prompts for one. Hookwise allocates a random *.tunnel.tryhookwise.xyz URL and forwards requests until the command is stopped.
✓ Tunnel online
Public https://hw-f93b8a1b.tunnel.tryhookwise.xyz
Forward http://localhost:3000Other commands
hookwise whoamiShow the currently authenticated account.hookwise logoutRemove the locally stored CLI credential.Choose the right target
Remote destination
Forward captured requests to an HTTPS endpoint hosted elsewhere. Hookwise manages delivery attempts and retries.
Your development machine
Forward synchronously through the connected CLI and return your local application's status, headers, and body.
hookwise login, then use hookwise listen to choose the hook, target, and local URL. Target IDs and agent tokens are not accepted as user-facing CLI flags.What happens after a request arrives
The original request waits for the Local Agent response. Keep local handlers fast and avoid long-running work in the request path.
Manage authenticated devices
Open Account & devices from your dashboard profile menu to review every authorized CLI device. You can see when it was authorized, when it was last used, and revoke it immediately.
~/.hookwise/config.json, agent tokens, or hook secrets to source control.Common issues
The CLI keeps disconnecting with code 4000
Another CLI is connected to the same target. Stop the older process or choose a different Local Agent target. Only one active connection owns a target at a time.
My local application returns 404
Confirm the forwarding URL includes the exact local route that handles the webhook, including any path prefix.
Can Hookwise expose an entire frontend app?
The current Local Agent forwards hook traffic to the local URL you select. General-purpose wildcard public forwarding URLs for full applications are coming next.