Why We Built ReqPour

Every developer who has worked with webhooks knows the pain. You are building an integration with Stripe, GitHub, or Shopify, and you need to receive HTTP callbacks on your local machine. The existing solutions either cost too much, require complex setup, or disappear when you close your terminal.

We built ReqPour because we wanted something simpler.

The Problem

Webhooks are the backbone of modern integrations. Payment processors, version control platforms, e-commerce systems, and communication tools all rely on them. But testing webhooks during development has always been awkward.

Your local server is invisible to the internet. Services like Stripe cannot reach localhost:3000. So you need a tunnel — a public URL that forwards requests to your machine.

The existing tools work, but they come with trade-offs. Some are expensive. Some give you a new URL every session. Some require you to install heavyweight CLI tools. Some are just flaky.

What ReqPour Does Differently

ReqPour gives you a permanent public endpoint that catches every incoming webhook. You can inspect the full request — headers, body, query parameters — in a real-time dashboard. When you are ready to develop, the CLI relay forwards those requests to your local server.

The key differences:

• Permanent URLs — your endpoint slug stays the same across sessions. No updating webhook configs every time you restart.
• Visual inspector — see every request in real time with syntax-highlighted JSON, searchable history, and one-click replay.
• Affordable — the Pro plan is $3/month. We think webhook tooling should not cost $20+/month.
• Lightweight CLI — npx reqpour relay and you are connected. No background daemons, no account creation wizards.

How It Works

1. Create an endpoint in the dashboard or CLI
2. Point your webhook provider at your ReqPour URL
3. Requests are caught and stored for inspection
4. Run npx reqpour relay --to http://localhost:3000/webhooks to forward them locally

The relay uses WebSockets for real-time forwarding with automatic reconnection. Your local server receives the exact same request that hit the public endpoint — same method, headers, and body.

What's Next

We are just getting started. On the roadmap: team workspaces, request filtering rules, custom response templates, and a VS Code extension. If you have ideas, we would love to hear them.

Try ReqPour free at reqpour.com.