Cloudinary (Admin API): 8 reads, 1 write and 1 destructive call, one client

Media library management via the Admin REST API. Every call below is available over HTTP, through the SDK and as a tool for a coding agent, with the same arguments and the same meter.

What Cloudinary (Admin API) can do here

The integration exposes 8 reads, 1 write and 1 destructive call, each with a declared input and output schema rather than a page of documentation you would have to translate. Media library management via the Admin REST API.

How it authenticates

Cloudinary (Admin API) authenticates with a apiSecret, supplied per request or stored once against your account and sealed at rest. On our side the same value is read from apiKey, apiSecret and cloudName when we broker the call for you.

Capabilities it fulfils

Cloudinary (Admin API) answers storage.object.list in the vendor-neutral form, which means code asking for that capability can be pointed at Cloudinary (Admin API) without naming it. If it goes down, or you would rather use somebody else, that is a preference change and not a rewrite.

• usage — read: Account usage report.
• listImages — read: List image resources.
• deleteResource — destructive: Delete by public id(s).
• search — read: Query the media library in Cloudinary’s own search language — the only way to filter by tag, dimension, format and upload date at once.
• resourceDetails — read: Everything about one asset, including the blocks the list endpoints omit.
• listByTag — read: Every image carrying one tag.
• listTags — read: Every tag in use on images — the vocabulary listByTag takes.
• listFolders — read: Top-level folders in the media library.
• listTransformations — read: Named and used transformations on the account.
• tagResources — write: Add, remove or replace a tag across one or more assets.

Questions

Do I have to bring my own API keys?

You can, and that lane is free for ever — pass your key on the request or store it against your account, and we are one proxy hop. The paid lane is the other direction: we call 226 providers with our credentials so you never register anywhere. Both go through the same client and the same operation names.

What happens to a key I store here?

It is sealed with AES-256-GCM before it reaches the database and is only ever opened to make the call you asked for. It is scoped to your account, it is never logged, and deleting the connection deletes it. For an OAuth provider we hold a refresh token instead, and revoking the link at the provider stops the calls here immediately.

What happens when a provider changes its API?

The operation contract is declared, so a response that no longer matches is a refusal rather than a silently wrong answer. The contract does not coerce types — a field declared a number that arrives as a string is rejected at the edge, on the way in and on the way out.