Source type

Svix Source Configuration

Svix sources receive standard Svix-signed webhook traffic and are also useful for providers that expose Svix-compatible webhook signatures.

SVIXPOST, PUT, PATCH, DELETESigning SecretDeveloper tools
Svix verification documentationAll source types
Svix sends webhook traffic to a FastHook source, FastHook validates the provider contract, records the request, and routes accepted events through connections to destinations.SvixProviderPOST, PUT, PATCH, DELETESignedFastHookSource URLSVIXProvider 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.

Svix configuration

Create a Svix source, keep POST and PUT and PATCH and DELETE enabled, and provide the configured Signing Secret values for provider signature. FastHook uses these settings to validate each Svix delivery before it enters the routing workflow.

Source Type

SVIX

Allowed methods

POST, PUT, PATCH, DELETE

Authentication

Provider signature

Credential fields

Signing Secret

Svix source config
{
  "type": "SVIX",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "SVIX",
      "webhook_signing_secret": "provider-secret"
    },
    "allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
  }
}

Svix request contract

FastHook verifies the Svix signature over message-id + '.' + timestamp + '.' + raw body using the configured whsec secret.

POSTPUTPATCHDELETE

Svix headers

Preserve svix-id, svix-timestamp, svix-signature when sending Svix 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.

svix-id

Message id used in the signed payload.

svix-timestamp

Unix timestamp used in the signed payload.

svix-signature

One or more Svix signatures.

Svix setup

  1. Create a Svix endpoint that points to the FastHook Source URL.
  2. Copy the endpoint signing secret into FastHook.
  3. Keep the raw payload unchanged if you also verify again in your destination.

Svix routing hints

  • Svix-compatible payloads usually include a message id, timestamp, and signature headers.
  • Use svix-id as a delivery id when receivers need idempotency or support lookup.

Continue with Svix