Getting Started with ReqPour

Create Your Account

Getting started with ReqPour takes less than two minutes. Visit reqpour.com/register and create an account with your email address. You will receive a verification email — click the link to activate your account.

Once verified, you can log in to the dashboard at reqpour.com/dashboard. The dashboard is where you manage your endpoints, inspect incoming requests, and configure your relay settings.

The free tier gives you 1 endpoint, 100 requests per day, and 24 hours of request history. This is enough to get started with webhook development. When you need more, upgrade to Pro for $3/month.

Create Your First Endpoint

In the dashboard, click "Create Endpoint" to generate a new public URL. Each endpoint gets a unique subdomain like abc123.reqpour.com. This is the URL you will give to webhook providers.

Copy the endpoint URL and configure it in your webhook provider. For example, in Stripe's Dashboard, go to Developers > Webhooks > Add endpoint and paste your ReqPour URL. Select the events you want to receive and save.

Your endpoint is immediately active. Any HTTP request sent to the endpoint URL will be captured and displayed in the dashboard. You do not need to have the CLI running or a local server active — ReqPour captures everything.

Install the CLI

The ReqPour CLI relays captured webhook requests to your local development server. You do not need to install it globally — use npx to run it directly:

npx reqpour login

This opens your browser for authentication. Log in with your ReqPour account and the CLI will be authorized. Your login session persists across terminal sessions, so you only need to do this once.

To see your endpoints:

npx reqpour list

This displays all your endpoints with their URLs and current status.

Start the Relay

The relay forwards incoming webhook requests from your ReqPour endpoint to your local development server:

npx reqpour relay --to http://localhost:3000/api/webhooks

The --to flag specifies where to forward requests. This should match the URL of your webhook handler on your local server. The relay preserves the full request: method, headers, body, and path.

Once the relay is running, trigger a webhook event (make a test payment in Stripe, push to a GitHub repo, etc.). You will see the request appear in both the ReqPour dashboard and your terminal. Your local server processes it as if the provider sent it directly.

The CLI shows each relayed request with the HTTP method, path, response status, and latency. If your local server returns an error, you will see it immediately.

Inspect and Replay Requests

Open the ReqPour dashboard to see all captured requests. Click any request to inspect its full details: HTTP method, URL path, all headers, and the complete body with syntax highlighting.

Use the search bar to filter requests by content — search for an event type, an email address, or any text that appears in the headers or body. This is invaluable when you have many requests and need to find a specific one.

To replay a request, click the replay button on any captured request. ReqPour re-sends the exact same request to your endpoint, which then forwards it through the relay to your local server. This is perfect for iterative development — trigger a real webhook once, then replay it as many times as you need while building your handler.

Next Steps

Now that you have the basics working, explore these features to get the most out of ReqPour:

Check out the integration guides to see detailed setup instructions for specific providers like Stripe, GitHub, Shopify, and more. Each guide includes the webhook configuration, code examples, and tips specific to that provider.

Read the Dashboard Guide to learn about advanced inspection features, including JSON path filtering, header inspection, and request comparison.

Explore the CLI Reference for all available commands and options, including how to target specific endpoints and configure relay behavior.

If you are working with a team, the Pro plan includes endpoint sharing — multiple developers can receive webhooks from the same endpoint, which is useful for collaborative debugging.