FastHook Documentation for Webhook Delivery

FastHook documentation explains how to receive webhooks, route events, inspect delivery behavior, and recover failed webhook traffic before it reaches your application code.

Use this overview when you are planning webhook infrastructure, replacing a fragile endpoint, or adding visibility to event-driven workflows. The docs are organized around the same objects you use in the dashboard: sources, destinations, connections, filters, transformations, retries, and metrics.

Start Here

If you are new to FastHook, begin with the Quickstart. It walks through the first working route in the order the platform uses internally: create a source, create a destination, connect them, and send a test webhook with curl.

After the quickstart, read Core Concepts to understand the event model. A source receives inbound webhook traffic, FastHook creates a request and event, a connection chooses the destination, and delivery controls decide how the event should be handled.

What FastHook Helps You Build

FastHook is a webhook event gateway for teams that need reliable delivery between external providers and internal services. It gives every producer a stable ingress URL, keeps delivery logic out of application controllers, and provides operational tools for debugging, retries, replay, and routing.

Typical FastHook workflows include:

  • Receiving webhook traffic from Stripe, GitHub, Shopify, internal services, or custom event producers.
  • Routing one inbound webhook stream to one or more downstream destinations.
  • Filtering noisy events before they reach services that do not need them.
  • Transforming payloads so every destination receives the shape it expects.
  • Retrying failed deliveries after temporary receiver errors.
  • Inspecting request and event history when a webhook integration fails.

Core Documentation

Sources

Sources are public ingress endpoints for incoming HTTP requests. Use sources when a provider needs a stable webhook URL, when you want to inspect raw inbound requests, or when multiple consumers should share the same producer stream.

Destinations

Destinations are outbound endpoints that receive routed events. Use HTTP destinations for internal APIs, worker services, and staging receivers. Use CLI destinations when you want FastHook to forward webhook traffic to a localhost service through the FastHook CLI.

CLI & Tunneling

CLI & Tunneling explains how to install fasthook.exe, run FastHook API commands from the CLI, inspect local deliveries with fasthook-log, and use the default 8080 local tunnel flow.

Connections

Connections link sources to destinations. This is where webhook routing becomes operational: you can pause delivery, apply filters, transform payloads, deduplicate repeated events, delay traffic, and configure retries for failed attempts.

Filters

Filters match headers, body fields, query parameters, and paths so only relevant webhook events move forward. Use filters when a provider sends many event types but a destination only needs a specific subset.

Transformations

Transformations modify payloads before delivery. Use transformations when a downstream service expects normalized fields, a smaller body, or a different structure than the original provider payload.

Retries

Retries help recover delivery failures caused by temporary destination errors. Use retries with idempotent receivers so webhook delivery can recover without duplicating business side effects.

Metrics

Metrics show request volume, delivery status, failure patterns, and traffic trends. Use metrics to detect webhook outages, noisy integrations, retry spikes, and destination reliability problems.

API Reference

The API reference documents the REST endpoints for sources, destinations, connections, requests, events, retries, transformations, and project-level automation. The FastHook CLI mirrors these API operations with resource commands and a direct fasthook api <method> <path> fallback.

Common Use Cases

Receive Webhooks Reliably

Create a source, connect it to a destination, and follow the Quickstart to confirm the provider payload arrived. This is the baseline workflow for reliable webhook ingestion.

Test Webhooks Locally

Create a CLI destination, connect it to a source, and run fasthook tunnel to receive routed webhook traffic on http://localhost. On Windows, use the released fasthook.exe; source builds can run the same command with npx .. See CLI & Tunneling for the local modules and Test webhooks locally for the full workflow.

Route Third-Party Events

Use connections to route events from providers into internal services. Add filters when only some event types matter, and add transformations when each receiver needs a different payload shape.

Debug Failed Webhook Delivery

Inspect the request, event, destination response, and retry status before changing application code. FastHook keeps the operational history close to the route, which makes webhook debugging faster than searching across provider dashboards and service logs.

Recover From Downstream Outages

When a destination is slow, unavailable, or returning 5xx responses, use retries, replay workflows, and delivery history to recover events after the receiver is healthy again.

Recommended Reading Path

  1. Read the Quickstart to create a working webhook route.
  2. Review Core Concepts to understand sources, requests, events, connections, destinations, and attempts.
  3. Configure Sources and Destinations for your real provider and receiver.
  4. Use Connections to route traffic and add delivery controls.
  5. Add Filters, Transformations, Retries, Metrics, and the API Reference as your webhook workflow becomes production-critical.

Frequently Asked Questions

What is FastHook?

FastHook is a webhook routing and delivery platform. It receives webhook requests, routes events to destinations, records delivery history, and helps teams inspect, retry, and replay failed webhook traffic.

What should I read first?

Start with the Quickstart if you want to build immediately. Start with Core Concepts if you want to understand the platform model before creating sources, destinations, and connections.

Is FastHook only for third-party webhooks?

No. FastHook can receive webhook traffic from third-party providers, internal services, devices, workers, or any system that sends HTTP requests and needs reliable downstream delivery.

Where should webhook routing logic live?

Keep product-specific business logic in your application, but put operational routing behavior in FastHook when you need visibility, filters, transformations, retries, replay, and destination-specific delivery controls.