Cloudinary

Install corsair and @corsair-dev/cloudinary, add the Cloudinary plugin, and connect with your credentials. Then call methods like corsair.cloudinary.api.adaptive.getAdaptiveStreamingProfiles() from your app. Corsair verifies webhooks, and syncs data per tenant.

Yes. Cloudinary supports your credentials. Use credentials or OAuth scopes that match what you automate. Create them in the Cloudinary developer console, then paste into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Cloudinary, GitHub, Notion, Stripe, and the rest. Trigger Cloudinary from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for media management api for uploading, transforming, optimizing, and delivering images and video. Common builds include sync jobs, admin tooling, and agents that call Cloudinary APIs from your backend. Webhook handlers react to Cloudinary events and fan out to Slack, email, or other plugins in the same tenant. Local DB entities let you query synced Cloudinary records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Cloudinary API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/cloudinary in the open repo. When Cloudinary ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Cloudinary data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Cloudinary data on your behalf.