Source type

Resend Source Configuration

Resend sources receive email delivery, bounce, complaint, open, and click events with Svix-compatible signatures.

RESENDPOST, PUT, PATCH, DELETEWebhook Signing SecretEmail and messaging
Resend webhooks documentationAll source types
Resend sends webhook traffic to a FastHook source, FastHook validates the provider contract, records the request, and routes accepted events through connections to destinations.ResendProviderPOST, PUT, PATCH, DELETESignedFastHookSource URLRESENDProvider 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.

Resend configuration

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

Source Type

RESEND

Allowed methods

POST, PUT, PATCH, DELETE

Authentication

Provider signature

Credential fields

Webhook Signing Secret

Resend source config
{
  "type": "RESEND",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "RESEND",
      "webhook_signing_secret": "whsec_..."
    },
    "allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
  }
}

Resend request contract

FastHook uses Svix verification over message id, timestamp, and raw body with the configured whsec secret.

POSTPUTPATCHDELETE

Resend headers

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

Svix signature header.

Resend setup

  1. Create a Resend webhook endpoint using the FastHook Source URL.
  2. Copy the whsec signing secret into FastHook.
  3. Use email id and event type fields for routing or deduplication.

Resend routing hints

  • Resend delivery traffic can branch into sent, delivered, bounced, complained, opened, and clicked workflows without mixing success and suppression handling.
  • Keep the email identifier with each delivery event so support and analytics workflows can correlate status changes across the message lifecycle.

Continue with Resend