Destination type

HTTP Destination Configuration

Use HTTP destinations for deployed services, staging APIs, public webhook consumers, internal API gateways, and any receiver that accepts ordinary HTTP requests. This destination configuration reference covers the fields and delivery behavior required to connect it to FastHook.

FastHook delivers each event to the configured HTTP endpoint.

HTTPHTTPS receiver URLPOST, PUT, PATCH, DELETEHTTP delivery
All destination typesDestinations docs
HTTP destination delivery flowFastHook routes accepted events through a connection to a HTTP destination and stores delivery attempt evidence.AcceptedRequestsource verifiedConnectionRoute branchfilters and transformsretry policyHTTPHTTPHTTPS receiver URLPOST, PUT, PATCH, DELETEAttemptEvidencestatus + bodyDestination config owns target, auth, method, rate limit, disabled state, and delivery attempt evidence.

HTTP dashboard fields

Endpoint URL

The deployed receiver URL, such as https://api.example.com/webhooks/fasthook.

HTTP method

The method the receiver expects for delivery attempts.

Destination auth

How FastHook authenticates to the receiver.

Max delivery rate

Optional pacing control for protecting a slow or rate-limited receiver.

HTTP API config

config.url

Absolute HTTPS receiver URL that receives routed deliveries.

config.http_method

Outbound method used for each delivery: POST, PUT, PATCH, or DELETE.

config.auth_type

Outbound authentication mode for the receiver.

config.auth

Authentication settings for custom headers, OAuth2, Google OAuth, or FastHook signatures.

config.rate_limit

Optional maximum number of deliveries in the selected period.

config.rate_limit_period

Rate-limit period: second, minute, or hour.

HTTP destination config
{
  "name": "orders-api",
  "type": "HTTP",
  "config": {
    "url": "https://api.example.com/webhooks/fasthook",
    "http_method": "POST",
    "auth_type": "FASTHOOK_SIGNATURE",
    "auth": {},
    "rate_limit": 10,
    "rate_limit_period": "second"
  }
}

HTTP authentication

  • No auth
  • FastHook signature
  • Custom header
  • OAuth2 client credentials
  • OAuth2 authorization code
  • Google OAuth for Google APIs

HTTP delivery method and limit

POSTPUTPATCHDELETE

Rate limit: Optional. Configure a max delivery rate per second, minute, or hour.

HTTP delivery behavior

  • FastHook sends the routed event payload to the configured URL and stores the response status, body, latency, and attempt evidence.
  • FastHook signature auth adds outbound verification headers so the receiver can prove the request came through FastHook.
  • OAuth2 modes fetch or use access tokens before delivery; custom header mode sends the exact configured header and value.
  • Receiver 4xx, 5xx, timeout, or network errors are visible on events and attempts and can be retried according to connection rules.

HTTP setup checklist

  1. Create a destination and choose HTTP as the destination type.
  2. Enter the receiver URL and the HTTP method your receiver expects.
  3. Choose destination auth. Use FastHook signature when your receiver should verify FastHook deliveries.
  4. Set a max delivery rate when the receiver has limited throughput or expensive side effects.
  5. Connect one or more sources to this destination through connections.

HTTP troubleshooting

Attempts fail with 401 or 403.

Check destination auth, custom header values, OAuth2 token settings, or FastHook signature verification code on the receiver.

Attempts fail with 404 or 405.

Confirm the endpoint path and HTTP method. FastHook only sends the method configured on the destination.

The receiver is overloaded.

Set config.rate_limit and config.rate_limit_period, then retry or replay only the failed event window.

Related docs