webhookbins CLI

Test webhooks against your real local code — without deploying. The CLI creates a tunnel between webhookbins.com and your machine, so every incoming webhook is forwarded directly to your server.

How it works

Webhook arrives

Stripe, GitHub, or any service sends a POST to your webhookbins.com URL.

CLI forwards it

The CLI receives the request via WebSocket and replays it to your localhost.

Real response returned

Your local server's response (status, headers, body) is sent back to the original sender.

Your local server must be running before starting the tunnel. The CLI will return a 502 error to the webhook sender if nothing is listening on the specified port.

Quick start

# 1. Install
curl -fsSL https://webhookbins.com/install.sh | sh

# 2. Start your local server (example: node, python, etc.)
node server.js

# 3. Start the tunnel (use the endpoint ID from the inspector)
webhookbins <endpoint-id> --port 3000

# Tunnel is active — webhooks now forward to your machine:
  ✓ Tunnel active
  Forwarding → http://localhost:3000
  Inspect   → https://webhookbins.com/<id>

# Incoming webhooks are logged as they arrive:
  POST /webhook/orders → 200
  POST /webhook/orders → 422

Install

$curl -fsSL https://webhookbins.com/install.sh | sh

or download directly

webhookbins-darwin-arm64

All platforms ↓

macOS (Apple Silicon)macOS (Intel)Linux Windows

Ready to test your webhooks?

Create a free endpoint, point your service at it, run the CLI — done.

Create webhook URL