How do I receive a webhook on localhost?

Run `npx useburrow http 3000` to get a public HTTPS URL, then register that URL (plus your route path) as the webhook endpoint in your provider. Deliveries forward to your local server over an outbound WebSocket, so it works behind any firewall or NAT.

Can I replay a webhook without re-triggering it?

Yes. The local inspector keeps every delivery and replays any of them with one click against your local route — the fastest way to iterate on a handler without firing new events from the provider.

Will signature verification still work?

Yes. Burrow forwards the raw request body untouched, so signature checks (Stripe’s signing secret, GitHub’s HMAC, etc.) verify exactly as they would in production.

Can I keep a stable webhook URL?

On the Pro plan you can reserve a subdomain or attach a custom domain, so your webhook endpoint stays the same across restarts.

Test webhooks on localhost

Test webhooks on localhost | BurrowTest webhooks locally: give your dev server a public HTTPS URL in one command, register it as the webhook endpoint, then inspect and replay every delivery. EU-hosted, DSGVO-first, with a local inspector.Burrow gives any local service a public, TLS-secured HTTPS URL with one command - npx useburrow http 3000 - hosted entirely in the EU. Webhook signatures are verified at the edge, every request is visible in the local inspector, and a first-class MCP server lets AI agents open and inspect tunnels. Home · Features · MCP for AI agents · Pricing · ngrok & other alternatives · Framework guides · Blog · About & EU data residency