How to Get Cloudinary API Credentials

Univaultport connects to Cloudinary using three credentials: your cloud name, an API key, and an API secret. This guide shows where to find each one and what permissions your account needs for read-only versus full migration.

Step 1 — Open your Cloudinary console

Sign in at console.cloudinary.com. If your team has multiple Cloudinary accounts, switch to the correct one using the product selector at the top-left of the dashboard.

Step 2 — Locate your account credentials

From the dashboard sidebar, choose Settings → API Keys (in newer console layouts) or look for the Account Details card on the dashboard home (older layouts).

You'll see three fields:

Cloud name:   acme-co
API Key:      123456789012345
API Secret:   ••••••••••••••••••••••••••  [Reveal]

Step 3 — Reveal and copy the API secret

Click the Reveal link next to the secret. Cloudinary will ask you to confirm — this prevents accidental exposure on screen-shares.

Copy each value into the corresponding field in the Univaultport connector wizard:

1. 1

   Cloud Name

   Paste your cloud name (the short string, e.g. acme-co). No URL, no quotes.
2. 2

   API Key

   Paste the numeric key.
3. 3

   API Secret

   Paste the secret you just revealed.
4. 4

   Root Folder (optional)

   If you only want to migrate a sub-folder of your Cloudinary library, enter its path (e.g. marketing/2026). Leave blank to scope to the whole library.

Step 4 — Test the connection

Click Save & test. Univaultport will perform a read-only API call to confirm credentials are valid. You'll see one of three outcomes:

Permission checklist for migrations

The role attached to your API key determines what Univaultport can do:

• Read-only migration (Cloudinary → another platform): any role with the Resources: List permission is enough.
• Write migration (→ Cloudinary): the role needs Resources: Upload plus Folders: Create if you want auto-folder creation on the destination.
• Cleanup after migration: add Resources: Delete.

The Master Admin key has all of these. Most teams generate a dedicated key per environment via Settings → Security → Restricted Access Profiles.

What about rate limits?

Cloudinary's Admin API allows 500 requests per hour per cloud on the free tier and 2,000+/hour on paid plans. Univaultport's worker paginates listings and uses exponential back-off — typical migrations of a few thousand assets stay well under these caps.

For larger libraries (50k+ assets), consider:

1. Upgrading to a paid Cloudinary plan
2. Splitting the migration into folder-scoped jobs
3. Running migrations during off-peak hours

Troubleshooting

If your Cloudinary cloud uses signed delivery URLs with custom CNAMEs, the secure_distribution field will not affect API credentials — those credentials still work with the default res.cloudinary.com endpoint.

Next steps

You're ready to run your first migration. Choose Cloudinary as either source or destination in Jobs → New migration, point it at another connector (S3, Google Drive, GCS, WordPress, …), and click run.

If you hit issues, the worker log on the job detail page surfaces the raw Cloudinary error code — that's the fastest path to a fix.