Cloudinary API Documentation

This is the complete API documentation for connecting to the Cloudinary API using MindCloud's Universal API. If you are new to MindCloud, start with the Introduction to see how one API can sit in front of many different apps.

MindCloud is an integration company that offers one normalized API to access 3,100+ apps from a single place. It cleans up provider-specific quirks, keeps requests and responses consistent, and centralizes authentication so you do not need to manage separate flows for every app. Browse other apps.

Meet Cloudinary: Upload, manage, search, and transform media assets. Keep reading to get started.

Quickstart

Before you run your first Cloudinary request, you need three things:

1. A MindCloud account — sign in or create an account at MindCloud.
2. A MindCloud API Key — create one in API Keys. Keep it on your server.
3. At least one Cloudinary connection — create or choose one in Connections. Note its connectionId.

Every Cloudinary action uses the same URL pattern:

https://connect.mindcloud.co/v1/universal/cloudinary/latest/actions/{actionSlug}

You need a MindCloud API Key and a Cloudinary connection. Then call an action such as Get Resource by Asset ID:

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/cloudinary/latest/actions/get-resource-by-asset-id" \
  --header "Authorization: Bearer $MINDCLOUD_API_KEY" \
  --get \
  --data-urlencode "connectionId=$CONNECTION_ID"

Every response comes back in the same envelope, with your rows in a data array:

{
  "success": true,
  "data": [
    { "id": "1042", "name": "Ava" }
  ],
  "meta": {}
}

After your first request works, use Shape your requests to control arguments, pagination, filtering, fields, and errors.

Authentication

Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected Cloudinary account that should run the action. MindCloud stores and refreshes the Cloudinary credentials behind that connection, so you never send provider tokens with your requests.

Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions. Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs.

Cloudinary actions

All 26 published actions for this Cloudinary version. Each page documents the endpoint, arguments, and response controls.

• PUTApply Explicit Asset Actions
• POSTCreate Folder
• POSTCreate Upload Preset
• DELETEDelete Asset
• DELETEDelete Folder
• DELETEDelete Resources by Asset IDs
• DELETEDelete Resources by Public IDs
• DELETEDelete Upload Preset
• GETGet Resource by Asset ID
• GETGet Resource by Public ID
• GETGet Upload Preset
• GETGet Usage
• GETList Folders
• GETList Resources
• GETList Resources by Asset Folder
• GETList Resources by Tag
• GETList Subfolders
• GETList Tags
• GETList Upload Presets
• GETPing
• PUTRename Asset
• GETSearch Folders
• GETSearch Resources
• PUTUpdate Resource Details
• PUTUpdate Upload Preset
• POSTUpload Asset

Related apps

More Content & Files apps on the Universal API, behind the same REST shape. Or browse all apps.

Google DriveAirtableGoogle DocsDropboxGoogle SlidesWorkflowyZoho SheetSnowflake