Source type

Custom Webhook Source Configuration

Use a custom webhook source when the producer is an internal service, a provider FastHook does not have a preset for yet, a publish endpoint for outbound webhook messages, or a test client that can send ordinary HTTP requests.

WEBHOOKPOST, PUT, PATCH, DELETEOptional Basic Auth, API key, or HMAC fieldsCustom
FastHook Sources docsAll source types
FastHook sends webhook traffic to a FastHook source, FastHook validates the provider contract, records the request, and routes accepted events through connections to destinations.FastHookProviderPOST, PUT, PATCH, DELETESignedFastHookSource URLWEBHOOKProvider credentialsignatureVerify before queue401 on auth failure405 on wrong methodAcceptedRequestverified: trueConnections route the accepted request to destinationsFilters, transformations, retries, replay, and destination signatures stay downstream from source verification.

Custom Webhook configuration

Create a Custom Webhook source, keep POST and PUT and PATCH and DELETE enabled, and provide the configured Optional Basic Auth, API key, or HMAC fields values for optional source auth. FastHook uses these settings to validate each FastHook delivery before it enters the routing workflow.

Source Type

WEBHOOK

Allowed methods

POST, PUT, PATCH, DELETE

Authentication

Optional source auth

Credential fields

Optional Basic Auth, API key, or HMAC fields

Custom Webhook source config
{
  "type": "WEBHOOK",
  "config": {
    "auth_type": "HMAC",
    "auth": {
      "signature_header": "x-signature",
      "secret": "shared-secret"
    },
    "allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
  }
}

Custom Webhook request contract

FastHook can verify a generic HMAC-SHA256 signature over the raw request body, or use Basic Auth/API key checks before queueing.

POSTPUTPATCHDELETE

FastHook headers

Preserve Authorization, Configured API key header, Configured signature header when sending FastHook test deliveries. FastHook evaluates this request context before accepting the payload, so missing or modified values remain visible as rejected requests instead of routed events.

Authorization

Used when Basic Auth is enabled.

Configured API key header

Used when API key auth is enabled.

Configured signature header

Used when generic HMAC auth is enabled.

FastHook setup

  1. Create a source, copy the generated Source URL, and point your sender at that URL.
  2. Keep the default methods for service-to-service traffic, or narrow them to the exact methods your sender uses.
  3. Choose Basic Auth, API key, or HMAC when the sender can attach a stable credential.
  4. For outbound webhook sending, let your application POST messages to this Source URL and route them to signed HTTP destinations through connections.

Continue with Custom Webhook