Configure a Cloudinary upload to run eager transformations asynchronously and notify a backend webhook when each one finishes
domain: cloudinary.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Pass an `eager` parameter on the upload call listing the transformation(s) to pre-generate as derived assets
Set `eager_async: true` so the upload call returns immediately after storing the original, while the listed eager transformations process in the background
Set `eager_notification_url` to an HTTPS endpoint you control; Cloudinary POSTs a JSON payload there when each eager transformation completes, separate from any general `notification_url`
On the receiving endpoint, verify the request is genuinely from Cloudinary by validating the `X-Cld-Signature` and `X-Cld-Timestamp` headers against the payload and your API secret before trusting the derived-asset URLs
Persist the derived asset URLs from the notification payload rather than assuming eager transformations are ready immediately after the initial upload response
Known gotchas
Without `eager_async: true`, eager transformations run synchronously and can make the initial upload call slow or time out for expensive video/image processing
Notification payloads must be signature-verified — treat an unverified POST to your webhook URL as untrusted input, since the endpoint is otherwise a public target
`eager_notification_url` only fires for eager transformation completions; it is independent of the general-purpose `notification_url` used for the base upload event
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?