Webhook Guides

RequestCatcher

RequestCatcher is a familiar developer pattern: create a public URL, send HTTP or webhook requests to it, and watch the raw request arrive in a live browser view.

That workflow is excellent for payload discovery and quick sender checks. FastHook covers the same capture and inspection need, then adds the operational layer teams need when the webhook stream should be routed, retried, replayed, transformed, or delivered to real destinations.

What RequestCatcher is used for

  • Creating a temporary public URL for HTTP and webhook tests.
  • Checking whether a provider dashboard is sending requests at all.
  • Inspecting request headers, method, path, query string, and body.
  • Debugging cURL, SDK, or custom HTTP client behavior.
  • Sharing a simple reproduction when a webhook sender is misconfigured.

RequestCatcher-style test

The simplest test sends a payload to a public capture URL. In FastHook, use a request bin or source URL for the same first step, then decide whether the traffic should become a durable route.

Send RequestCatcher-style webhook
curl -X POST "https://hook-xxxxxx.fasthook.io/requestcatcher" \
  -H "Content-Type: application/json" \
  -H "X-Test-Source: requestcatcher" \
  -d '{
    "id": "evt_requestcatcher_001",
    "type": "test.webhook",
    "message": "capture this request"
  }'

When RequestCatcher is enough

A lightweight live request viewer is enough when the request is disposable and the only question is whether the sender posted the expected data.

  • You need a temporary URL for a quick local or provider test.
  • You do not need downstream delivery to another service.
  • You do not need team-owned retention, routing, retries, or replay.
  • You are inspecting request shape before building a receiver.

When to use FastHook instead

Move beyond a simple request catcher when captured webhook traffic needs an operational path after it arrives. FastHook separates request capture from routed events and destination attempts, so a test can become a production webhook flow without losing evidence.

NeedFastHook path
Capture and inspect one requestWebhook receiver online
Inspect headers and payloadsWebhook inspector
Use a disposable inboxWebhook request bin
Compare alternativesRequestCatcher alternative
Operate production deliveryWebhook gateway

Migration checklist

  1. List the RequestCatcher URLs that are temporary tests versus real integration paths.
  2. Create FastHook request bins for disposable tests and sources for durable webhook streams.
  3. Add source authentication or provider signature checks before production traffic.
  4. Connect accepted requests to HTTP, Slack, Google Sheets, mock API, or local CLI destinations.
  5. Use event retry and request replay only after receiver idempotency is clear.

Related guides