Source type
Chargebee Retention Source Configuration
Chargebee Retention sources receive cancel experience, offer, survey, and retention workflow webhooks with shared-secret signing.
Chargebee Retention configuration
Create a Chargebee Retention source, keep POST and PUT and PATCH and DELETE enabled, and provide the configured Shared Secret values for provider signature. FastHook uses these settings to validate each Chargebee Retention delivery before it enters the routing workflow.
Source TypeCHARGEBEE_RETENTION
Allowed methodsPOST, PUT, PATCH, DELETE
AuthenticationProvider signature
Credential fieldsShared Secret
{
"type": "CHARGEBEE_RETENTION",
"config": {
"auth_type": "PROVIDER_SIGNATURE",
"auth": {
"provider": "CHARGEBEE_RETENTION",
"webhook_signing_secret": "shared-secret"
},
"allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
}
}Chargebee Retention request contract
FastHook computes HMAC-SHA1 hex over the raw request body and accepts either the raw digest or sha1= digest form in x-hub-signature.
Chargebee Retention headers
Preserve x-hub-signature when sending Chargebee Retention 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-hub-signatureHMAC-SHA1 hex signature over the raw request body.
Chargebee Retention setup
- Create a Chargebee Retention webhook subscription with the generated FastHook Source URL.
- Copy the shared secret from the webhook details into FastHook.
- Route by retention trigger, offer action, or survey response fields.