Generic Webhook Testing Endpoint

Generic webhook request example endpoint for testing custom providers and local integrations.

Accepts arbitrary webhook events for endpoint validation, header inspection, and payload debugging.

Endpoint URL

Use this endpoint when configuring the webhook sender:

https://hook-xxxxxx.fasthook.io/

Example request (curl)

curl -X POST "https://hook-xxxxxx.fasthook.io/" \
  -H "Content-Type: application/json" \
  -H "X-Event-Type: test.run" \
  -d '{"id":"evt_test_42","type":"test.run","data":{"ok":true}}'

Example headers

{
  "content-type": "application/json",
  "x-event-type": "test.run",
  "x-request-id": "req_4f9d"
}

Example payload (JSON)

{
  "id": "evt_test_42",
  "type": "test.run",
  "timestamp": "2026-04-21T09:00:00Z",
  "data": {
    "ok": true,
    "source": "custom-provider"
  }
}

How this webhook works

1. Provider sends a POST request to the endpoint URL.
2. FastHook stores the request headers, body, path, query, and source verification result.
3. Matching connections create outbound events for configured destinations.
4. Delivery attempts record destination response status, body, latency, and retry context.
5. Failed events can be retried after the destination or route is fixed.

Common debugging checks

• Confirm provider sends JSON and content-type header correctly.
• Inspect stored FastHook headers and request body when debugging auth failures.
• Retry failed requests or events after route and destination fixes.

Integration context

This page targets generic webhook flows and is optimized for debugging and testing scenarios developers face in production.

Last updated: Apr 21, 2026

Owner tools

Need full request, event, and attempt records? Use the private dashboard for retries, filters, transformations, and source or destination controls.

Open private request logs