Source type
Cloudinary Source Configuration
Cloudinary sources receive upload, moderation, transformation, and other notification webhooks with timestamped Cloudinary signatures.
Cloudinary configuration
Create a Cloudinary source, keep POST and PUT and PATCH and DELETE enabled, and provide the configured API Secret values for provider signature. FastHook uses these settings to validate each Cloudinary delivery before it enters the routing workflow.
Source TypeCLOUDINARY
Allowed methodsPOST, PUT, PATCH, DELETE
AuthenticationProvider signature
Credential fieldsAPI Secret
{
"type": "CLOUDINARY",
"config": {
"auth_type": "PROVIDER_SIGNATURE",
"auth": {
"provider": "CLOUDINARY",
"webhook_signing_secret": "api-secret"
},
"allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
}
}Cloudinary request contract
FastHook validates x-cld-timestamp, signs raw body + timestamp + API secret, and accepts Cloudinary SHA-1 or SHA-256 signature digests.
Cloudinary headers
Preserve x-cld-signature, x-cld-timestamp when sending Cloudinary 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-cld-signatureCloudinary signature generated from the notification payload.
x-cld-timestampUnix timestamp included in the signed payload.
Cloudinary setup
- Configure the notification URL in Cloudinary with the generated FastHook Source URL.
- Copy the Cloudinary API secret into FastHook.
- Route by notification_type or asset metadata when media workflows branch by event.