Cloudinary
Introduction
The Cloudinary destination lets you connect to your Cloudinary account using API credentials.
At this time, the destination connector is in development: credentials can be validated, but loading data into Cloudinary is not yet supported.
Setup
Before configuring the connector, gather the following from your Cloudinary account:
- Cloud name
- API key
- API secret
You can find these in the Cloudinary Console under Settings → Access Keys (wording may vary by Cloudinary UI version).
Authentication
This connector authenticates to Cloudinary using Basic Auth with:
- Username: API key
- Password: API secret
During connection testing, the connector validates credentials by calling Cloudinary’s usage endpoint:
GET https://api.cloudinary.com/v1_1/{cloud_name}/usage
Configuration fields
| Field | Type | Required | Description |
|---|---|---|---|
cloud_name | string | ✅ | Your Cloudinary cloud name. Must be a valid DNS label: lowercase letters (a-z), digits (0-9), and hyphens (-) only; 1–63 characters; cannot start or end with -. |
api_key | string | ✅ | Cloudinary API key. |
api_secret | string | ✅ | Cloudinary API secret. |
Streams
This is a destination connector. Stream support (what objects can be written to Cloudinary and how records map to Cloudinary resources) is not yet available.
Limitations
- Loading is not supported yet. Runs will fail if they attempt to write data to Cloudinary.
- Connection testing only validates that the provided credentials can authenticate and access the account usage endpoint.
Hashing and normalization
This destination does not currently expose field-level hashing options.
Data contract
A destination data contract is not yet available because Cloudinary loading/mapping is still in development.