Source type

Cloudinary Source Configuration

Cloudinary sources receive upload, moderation, transformation, and other notification webhooks with timestamped Cloudinary signatures.

CLOUDINARYPOST, PUT, PATCH, DELETEAPI SecretContent and data
Cloudinary sends webhook traffic to a FastHook source, FastHook validates the provider contract, records the request, and routes accepted events through connections to destinations.CloudinaryProviderPOST, PUT, PATCH, DELETESignedFastHookSource URLCLOUDINARYProvider 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.

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 Type

CLOUDINARY

Allowed methods

POST, PUT, PATCH, DELETE

Authentication

Provider signature

Credential fields

API Secret

Cloudinary source config
{
  "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.

POSTPUTPATCHDELETE

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-signature

Cloudinary signature generated from the notification payload.

x-cld-timestamp

Unix timestamp included in the signed payload.

Cloudinary setup

  1. Configure the notification URL in Cloudinary with the generated FastHook Source URL.
  2. Copy the Cloudinary API secret into FastHook.
  3. Route by notification_type or asset metadata when media workflows branch by event.

Continue with Cloudinary