Categories

← View All Tools

Webhook Debugger & Relay

Generate a unique webhook capture URL, inspect incoming requests, validate signatures, and replay payloads to a target endpoint

Example Results

2 examples

Capture Stripe test webhooks before forwarding

Create a unique request bin, validate HMAC signatures, and replay selected payloads to a local API only after inspection

Webhook dashboard with a unique capture URL, signature validation, and replay controls.
View input parameters
{ "relayTargetUrl": "https://api.example.com/webhooks/stripe", "signatureSecret": "whsec_test_123", "signatureHeader": "stripe-signature", "autoReplay": false, "methodFilter": "POST", "bodyMustContain": "\"type\":\"invoice.paid\"", "storedRequestLimit": 50 }

Debug GitHub webhook payloads with conditional relay

Only auto-forward matching push events while keeping a full request log for replay and export

Webhook dashboard configured for conditional relay, replay, and export.
View input parameters
{ "relayTargetUrl": "https://api.example.com/webhooks/github", "signatureSecret": "github_secret_value", "signatureHeader": "x-hub-signature-256", "autoReplay": true, "methodFilter": "POST", "bodyMustContain": "\"ref\":\"refs/heads/main\"", "storedRequestLimit": 100 }

Key Facts

Category
Network
Input Types
text, checkbox, select, number
Output Type
html
Sample Coverage
4
API Ready
Yes

Overview

The Webhook Debugger & Relay tool provides a unique capture URL to inspect, validate, and forward incoming HTTP requests. It allows developers to view payload details, verify HMAC signatures, and selectively replay webhooks to local or remote endpoints, making API integration testing seamless and secure.

When to Use

  • •Testing third-party API integrations like Stripe or GitHub before deploying to production.
  • •Troubleshooting failed webhook deliveries by inspecting raw headers, payloads, and signatures.
  • •Forwarding specific webhook events to a local development environment using conditional auto-replay.

How It Works

  • •Generate a unique capture URL to receive incoming webhook requests.
  • •Configure optional HMAC signature validation by providing your secret and header name.
  • •Set method filters or body text requirements to isolate specific events.
  • •Inspect captured payloads in the dashboard and manually or automatically relay them to your target URL.

Use Cases

Isolating and debugging specific payment events from Stripe or PayPal.
Validating GitHub push event signatures and forwarding them to a CI/CD pipeline.
Creating a temporary request bin to inspect undocumented API callbacks.

Examples

1. Debugging Stripe Payment Webhooks

Backend Developer
Background
Integrating Stripe subscriptions requires handling various webhook events, but testing them directly against a local server is difficult without exposing a public URL.
Problem
Need to capture invoice payment events, verify their Stripe signatures, and manually replay them to a local development server.
How to Use
Set the Relay Target URL to your local endpoint, enter your Stripe webhook secret, set the Signature Header to stripe-signature, and filter for bodies containing the invoice.paid event type.
Example Config
Relay Target URL: https://api.example.com/webhooks/stripe
Signature Secret: whsec_test_123
Signature Header: stripe-signature
Method Filter: POST
Body Must Contain: "type":"invoice.paid"
Outcome
The dashboard captures only paid invoice events, verifies the Stripe signature, and allows manual replay to the local API for safe testing.

2. Auto-Relaying GitHub Push Events

DevOps Engineer
Background
A CI/CD pipeline needs to trigger builds only when code is pushed to the main branch, but GitHub sends webhooks for all branch pushes.
Problem
Filter incoming GitHub webhooks to only forward main branch push events to the build server automatically.
How to Use
Configure the Relay Target URL to the build server, enable Auto Replay, and set the body filter to require the main branch reference.
Example Config
Relay Target URL: https://api.example.com/webhooks/github
Auto Replay: true
Method Filter: POST
Body Must Contain: "ref":"refs/heads/main"
Outcome
All GitHub webhooks are logged, but only pushes to the main branch are automatically forwarded to the CI/CD pipeline.

Try with Samples

network
PDF Samples
Generated PDF samples from tools dated 2026-02-01 to 2026-02-10
task generate
sample
NATS Message System Samples
NATS messaging system examples including pub/sub, request-reply, queue groups, and JetStream for modern cloud-native applications
keywords request
sample
Mock Service Worker Samples
Comprehensive MSW (Mock Service Worker) examples for API mocking, GraphQL, WebSocket mocking, and advanced request handling patterns
keywords request
sample
Contentful Cloud-based CMS Samples
Comprehensive Contentful examples covering content modeling, API integration, webhooks, migrations, and frontend integration patterns
keywords webhook
sample

Related Hubs

Network Convert Tools
Explore 7 network tools for convert workflows and compare closely related utilities quickly.
Json Convert Tools
Explore 100 json tools for convert workflows and compare closely related utilities quickly.
Image Convert Tools
Explore 100 image tools for convert workflows and compare closely related utilities quickly.
Audio Convert Tools
Explore 100 audio tools for convert workflows and compare closely related utilities quickly.

FAQ

What is a webhook capture URL?

It is a temporary, unique endpoint generated by the tool to receive and log incoming HTTP requests from third-party services.

How does signature validation work?

By entering your signature secret and header name, the tool calculates the expected HMAC hash and compares it against the incoming request to verify authenticity.

Can I automatically forward requests to my local server?

Yes, by enabling the Auto Replay feature and setting a Relay Target URL, incoming requests that match your filters will be forwarded automatically.

How many requests can I store?

You can configure the stored request limit between 10 and 200 requests. Older requests are overwritten once the limit is reached.

Can I filter which webhooks are captured or replayed?

Yes, you can filter incoming requests by HTTP method (like POST or PUT) and specify text that must be present in the payload body.

API Documentation

Request Endpoint

POST /en/api/tools/webhook-debugger-relay

Request Parameters

Parameter Name Type Required Description
relayTargetUrl text No -
signatureSecret text No -
signatureHeader text No -
autoReplay checkbox No -
methodFilter select No -
bodyMustContain text No -
storedRequestLimit number No -

Response Format

{
  "result": "
Processed HTML content
",
  "error": "Error message (optional)",
  "message": "Notification message (optional)",
  "metadata": {
    "key": "value"
  }
}
HTML: HTML

AI MCP Documentation

Add this tool to your MCP server configuration: 

{
  "mcpServers": {
    "elysiatools-webhook-debugger-relay": {
      "name": "webhook-debugger-relay",
      "description": "Generate a unique webhook capture URL, inspect incoming requests, validate signatures, and replay payloads to a target endpoint",
      "baseUrl": "https://elysiatools.com/mcp/sse?toolId=webhook-debugger-relay",
      "command": "",
      "args": [],
      "env": {},
      "isActive": true,
      "type": "sse"
    }
  }
}

You can chain multiple tools, e.g.: `https://elysiatools.com/mcp/sse?toolId=png-to-webp,jpg-to-webp,gif-to-webp`, max 20 tools.

If you encounter any issues, please contact us at [email protected]