Webhook Endpoints

Webhook endpoints are unique URLs that capture incoming webhooks from external services.

Understanding Endpoints

Each endpoint gives you a unique URL that you can use as a webhook destination in services like Stripe, GitHub, Shopify, Twilio, and more. When a webhook is sent to this URL, HookReplay captures and stores it for inspection and replay.

Example Endpoint URL 
https://hookreplay.dev/hook/f8a3b2c1-4d5e-6f7a-8b9c-0d1e2f3a4b5c

This URL accepts all HTTP methods: GET, POST, PUT, PATCH, and DELETE.

Creating an Endpoint

Open your workspace

Navigate to the workspace where you want to create the endpoint.

Click "New Endpoint"

Click the "New Endpoint" button to open the creation form.

Configure the endpoint

Fill in the endpoint details:

  • Name: A descriptive name (e.g., "Stripe Webhooks", "GitHub Events")
  • Destination URL: (Optional) The URL to forward webhooks to for replay or streaming

Copy the webhook URL

After creation, copy the generated webhook URL and configure it in your external service.

Endpoint Settings

Name

A human-readable identifier for your endpoint. Use descriptive names that indicate the source or purpose.

Destination URL

The URL where webhooks should be replayed or streamed. This is typically your local development server (e.g., http://localhost:3000/api/webhooks) or a staging server.

Active/Inactive Status

Toggle the endpoint on or off. When inactive, webhooks sent to the endpoint will receive a 503 response and won't be captured.

Streaming PRO

When enabled, incoming webhooks are immediately forwarded to your destination URL in real-time, in addition to being captured. This is useful when you need live webhook forwarding during development.

Pro Feature

Real-time streaming requires a Pro subscription. Upgrade now

Plan Limits

Feature Free Pro
Endpoints per workspace 1 Unlimited
Requests per day 100 10,000
Request body size 64 KB 1 MB
Request history Last 10 Unlimited
Real-time streaming - Yes

Best Practices

  • Use descriptive names: Name endpoints after the service sending webhooks (e.g., "Stripe Payments", "GitHub PR Events")
  • One endpoint per webhook source: Create separate endpoints for different services to keep requests organized
  • Set a destination URL: Configure a destination URL upfront so you're ready to replay webhooks immediately
  • Disable unused endpoints: Toggle off endpoints you're not actively using to avoid confusion