Cloudinary

Connect Cloudinary with your cloud name, API key, and API secret.

What you'll need

From your Cloudinary console dashboard:

• Cloud name
• API key
• API secret

These three values appear together in your Cloudinary account details. The API secret is a credential — treat it like a password.

Connect

1. In the Inverity dashboard, open Connectors and choose Cloudinary.
2. Enter the cloud name, API key, and API secret.
3. Select the folders or asset prefixes you want watched.

How write-back works

Cloudinary is the one DAM where Inverity replaces in place: the optimized file replaces the same public ID, and Cloudinary keeps the version history.

That means your existing delivery URLs continue to resolve unchanged — nothing in your site or app has to be updated. Your previous version remains available through Cloudinary's own version controls. See How write-back works.

Good to know

• Cloudinary transformations still apply on top of the optimized source. Your existing transformation URLs keep working.
• Cached derivatives. Cloudinary caches generated derivatives; they refresh on Cloudinary's own schedule after the source changes. See Delivery and caching.
• Cloudinary has its own optimization features. If you already deliver with f_auto,q_auto, much of your delivery is already optimized at the edge and your savings from source-side optimization will be correspondingly smaller — with a higher skip rate. The saving that remains is on storage and on the source bytes themselves.
• Existing assets need a run. Watching covers new uploads.

Disconnecting

Remove the connector in Inverity, then rotate your API secret in Cloudinary if you want the credential fully retired.

Troubleshooting

• Authentication fails — re-copy all three values; a truncated API secret is the usual cause.
• Delivery looks unchanged — check whether cached derivatives have refreshed.

See Connector errors.