Destination type

HTTP Destination

Use HTTP destinations for deployed services, staging APIs, public webhook consumers, internal API gateways, and any receiver that accepts ordinary HTTP requests.

HTTPHTTP or HTTPS 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 policyHTTPHTTPHTTP or HTTPS receiver URLPOST, PUT, PATCH, DELETEAttemptEvidencestatus + bodyDestination config owns target, auth, method, rate limit, disabled state, and delivery attempt evidence.
For HTTP destinations, FastHook sends the configured method to the receiver URL and stores response status, body, latency, and retry evidence.

When to use this destination type

Choose HTTP when the receiver target is HTTP or HTTPS receiver URL. Destinations are outbound delivery targets: they do not decide whether a source request should be accepted, and they do not own connection filters or transformations. They own where the final delivery goes and how FastHook should authenticate, pace, disable, and inspect that delivery.

A destination can be reused by multiple connections when several source branches should feed the same receiver. Reuse keeps receiver capacity, credentials, and attempt evidence attached to one destination id.

FastHook dashboard fields

In the dashboard, create a destination, set Destination Type to HTTP, then fill the fields below.

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.

API config fields

The REST API stores destination-specific behavior under config. Use PATCH for focused edits and PUT only when your request contains the full config you want to keep.

config.url

Absolute HTTP or 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"
  }
}
Create HTTP destination with cURL
curl -X POST "https://api.fasthook.io/v1/destinations" \
  -H "Authorization: Bearer $FASTHOOK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "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"
  }
}'

Authentication

Destination authentication is outbound. It helps the receiver trust or accept FastHook delivery, and it is separate from source authentication that verifies the original webhook producer.

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

HTTP methods and rate limit

This destination type uses the methods below for delivery attempts. Rate limits apply at the destination boundary, so every connection that targets the same destination shares that capacity.

POSTPUTPATCHDELETE

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

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.

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.

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