Source type

Twilio Source Configuration

Twilio sources receive voice, messaging, status callback, and other Twilio webhook requests with Twilio's URL-aware signature model.

Direct answer

Twilio sends X-Twilio-Signature as a Base64 HMAC-SHA1 value. Verification depends on the exact public URL plus form fields, or bodySHA256 for supported JSON requests.

TWILIOPOST, PUT, PATCH, DELETEAuth TokenCommunication
Twilio webhook security documentationAll source types
Twilio sends webhook traffic to a FastHook source, FastHook validates the provider contract, records the request, and routes accepted events through connections to destinations.TwilioProviderPOST, PUT, PATCH, DELETESignedFastHookSource URLTWILIOProvider 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.

Twilio configuration

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

Source Type

TWILIO

Allowed methods

POST, PUT, PATCH, DELETE

Authentication

Provider signature

Credential fields

Auth Token

Twilio source config
{
  "type": "TWILIO",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "TWILIO",
      "webhook_signing_secret": "auth-token"
    },
    "allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
  }
}

Twilio request contract

FastHook verifies x-twilio-signature using the public request URL, form parameters when applicable, and bodySHA256 when Twilio sends it.

POSTPUTPATCHDELETE

Twilio headers

Preserve x-twilio-signature when sending Twilio 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.

x-twilio-signature

Base64 HMAC-SHA1 signature calculated by Twilio.

Twilio setup

  1. Paste the exact generated FastHook Source URL into the Twilio callback setting.
  2. Use the Twilio Auth Token in FastHook.
  3. Avoid changing query parameters after Twilio is configured because the URL is part of the signature input.

Twilio routing hints

  • Messaging, voice, and status callback requests often use form fields and URL-aware signatures.
  • Keep the public callback URL stable because Twilio includes URL data in its signature model.

Continue with Twilio