Dashboard Guide

Dashboard Overview

The ReqPour dashboard at reqpour.com/dashboard is your command center for webhook development. It shows all your endpoints, incoming requests in real time, and tools for inspecting and replaying requests.

The main view shows your endpoints on the left sidebar. Select an endpoint to see its request feed — a chronological list of all captured requests. New requests appear at the top in real time as they arrive, with a subtle animation so you notice them.

Each request in the feed shows a summary: the HTTP method (color-coded: POST in blue, PUT in yellow, DELETE in red), the URL path, a timestamp, and the response status code. Click any request to expand its details.

Request Inspector

The request inspector shows the complete details of a captured request. It is organized into tabs: Headers, Body, and Response.

The Headers tab displays all HTTP headers in a key-value format. Provider-specific headers (like Stripe-Signature or X-GitHub-Event) are highlighted for easy identification. You can copy any header value with a single click.

The Body tab shows the request body with intelligent formatting. JSON bodies are displayed with syntax highlighting, collapsible sections, and line numbers. Large nested objects can be expanded and collapsed to navigate complex payloads. Form-encoded data is shown as a parsed key-value table. Raw text and XML are displayed with appropriate formatting.

The Response tab shows what your server returned (if a relay was active): the status code, response headers, and response body. This is useful for verifying that your handler returns the correct response to the webhook provider.

Search and Filtering

Use the search bar at the top of the request feed to filter requests. The search looks across headers, body content, and metadata. Common searches include:

- Event type: search for "payment_intent.succeeded" to find specific Stripe events - Email address: search for "user@example.com" to find requests related to a specific user - HTTP method: filter by "PUT" or "DELETE" to find non-POST requests - Error codes: search for "500" to find requests that resulted in server errors

The search is instant — results update as you type. Clear the search to return to the full request feed.

You can also filter by time range using the date picker. This is useful for finding requests from a specific testing session or investigating issues that occurred at a particular time.

Replay and Testing

The replay button on any captured request re-sends it to your endpoint. This is the most powerful feature for iterative webhook development. The workflow is:

1. Trigger a real webhook event (make a payment, push code, etc.) 2. Inspect the captured request in the dashboard to understand the payload 3. Start your relay and write your handler code 4. Replay the captured request to test your handler 5. Check the response in the dashboard 6. Refine your handler and replay again

Each replay creates a new entry in the request feed, so you can compare how your handler responded to different replays. This is invaluable for debugging — you can see exactly how your handler's response changed as you modified your code.

Replays use the exact same headers, body, and metadata as the original request. This means signature verification works if you are using the same endpoint and secret.

Team Features and Settings

On the Pro plan, you can share endpoints with team members. Go to Endpoint Settings and add collaborators by email address. Shared endpoints appear in each team member's dashboard, and all team members can see the same request feed.

This is useful for collaborative debugging — when a teammate encounters a webhook issue, they can share the endpoint and the exact request that caused the problem. Other team members can inspect the request and replay it against their own local server.

Endpoint settings also include options for request retention (how long captured requests are stored) and notifications (get alerted when specific events arrive or when errors exceed a threshold).

Account settings let you manage your API tokens, view usage statistics, and manage your subscription. The usage view shows your request count over time, helping you decide if you need to upgrade from the free tier.