Managing Endpoints

Creating Endpoints

Each endpoint gives you a unique public URL for receiving webhooks. Create endpoints from the dashboard by clicking "Create Endpoint" or via the API.

The free tier allows 1 endpoint. The Pro tier allows up to 10 endpoints. Using multiple endpoints helps organize your webhook development — one for Stripe, one for GitHub, one for your staging environment, etc.

Each endpoint URL follows the pattern https://[unique-id].reqpour.com. The URL is permanent and does not change between sessions or CLI restarts. This stability means you configure it once in your webhook provider and it keeps working.

Endpoint Configuration

Each endpoint has configurable settings:

Name: A human-readable label for identification. Choose descriptive names like "stripe-dev" or "github-prod-mirror" so you can quickly identify endpoints in the dashboard and CLI.

Response Status: The default HTTP status code returned when a request arrives and no relay is active. Defaults to 200. Some providers require specific response codes — configure this to match your provider's requirements.

Response Body: Optional default response body returned when no relay is active. Useful for providers that require specific response formats for verification (like Slack's URL verification challenge).

Webhook requests arrive at the root of your endpoint URL. If you need to distinguish between providers on a single endpoint, use different paths: https://abc123.reqpour.com/stripe and https://abc123.reqpour.com/github. The path is preserved and visible in the dashboard.

Multi-Endpoint Strategies

For professional webhook development, use separate endpoints for different purposes:

Provider separation: One endpoint per webhook provider (Stripe, GitHub, Shopify). This keeps your dashboard organized and makes it easy to filter requests by provider.

Environment separation: Different endpoints for development, staging, and testing. Point each environment's webhook provider configuration at the corresponding endpoint.

Feature separation: When building a new feature that involves webhooks, create a dedicated endpoint. This keeps your development traffic separate from your main endpoint and avoids cluttering the request history.

On the Pro plan with 10 endpoints, a typical setup might be: 3 for active development (Stripe, GitHub, general testing), 2 for staging environments, and 5 reserved for project-specific or temporary use.

Endpoint Security

ReqPour endpoints accept all incoming HTTP requests by default. Security is handled at the application level through signature verification in your webhook handler, not at the endpoint level.

However, there are best practices for endpoint security. Do not share your endpoint URL publicly — treat it like a semi-secret. While ReqPour endpoints are designed to receive unsolicited requests (that is what webhooks are), sharing the URL unnecessarily increases the chance of receiving spam or test requests that clutter your dashboard.

If you suspect an endpoint URL has been compromised (receiving unexpected traffic), delete the endpoint and create a new one. Update the URL in your webhook provider's configuration. This is a quick process since endpoints are cheap to create.

For production mirroring (forwarding production webhooks through ReqPour for debugging), use a separate endpoint and configure server-side relay so requests are forwarded to your production server automatically, with the dashboard serving as a monitoring and debugging tool.