Source type

Mailgun Source Configuration

Mailgun sources receive event and tracking webhooks and verify the Mailgun timestamp, token, and signature fields.

MAILGUNPOST, PUT, PATCH, DELETEHTTP Signing KeyEmail and messaging
Mailgun sends webhook traffic to a FastHook source, FastHook validates the provider contract, records the request, and routes accepted events through connections to destinations.MailgunProviderPOST, PUT, PATCH, DELETESignedFastHookSource URLMAILGUNProvider 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.

Mailgun configuration

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

Source Type

MAILGUN

Allowed methods

POST, PUT, PATCH, DELETE

Authentication

Provider signature

Credential fields

HTTP Signing Key

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

Mailgun request contract

FastHook computes HMAC-SHA256 over timestamp + token and compares it with the Mailgun signature field.

POSTPUTPATCHDELETE

Mailgun headers

Preserve signature.timestamp, signature.token, signature.signature when sending Mailgun 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.

signature.timestamp

Timestamp field in JSON or form body.

signature.token

Mailgun token field in JSON or form body.

signature.signature

HMAC-SHA256 hex signature field.

Mailgun setup

  1. Point Mailgun event webhooks at the FastHook Source URL.
  2. Paste the Mailgun HTTP signing key into FastHook.
  3. Use connection filters if delivery, bounce, complaint, and open events should go to different destinations.

Continue with Mailgun