Source type
LaunchDarkly Source Configuration
LaunchDarkly sources receive feature flag, environment, project, and account activity webhooks with signed payload verification.
LaunchDarkly configuration
Create a LaunchDarkly 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 LaunchDarkly delivery before it enters the routing workflow.
Source TypeLAUNCHDARKLY
Allowed methodsPOST, PUT, PATCH, DELETE
AuthenticationProvider signature
Credential fieldsWebhook Signing Secret
{
"type": "LAUNCHDARKLY",
"config": {
"auth_type": "PROVIDER_SIGNATURE",
"auth": {
"provider": "LAUNCHDARKLY",
"webhook_signing_secret": "provider-secret"
},
"allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
}
}LaunchDarkly request contract
FastHook computes HMAC-SHA256 hex over the raw body and compares it with x-ld-signature.
LaunchDarkly headers
Preserve x-ld-signature when sending LaunchDarkly 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-ld-signatureHMAC-SHA256 hex signature over the raw body.
LaunchDarkly setup
- Create a LaunchDarkly webhook and enable signing.
- Use the LaunchDarkly webhook secret in FastHook.
- Route flag and environment events to audit or deployment systems.