How Cloudinary handles this workflow
Calls Cloudinary's API directly for operations beyond prebuilt actions -- Cloudinary actually exposes several distinct APIs (Upload API, Admin API) with different authentication requirements rather than one unified endpoint.
Implementation details
Admin API calls generally need a signed request using the API secret, while Upload API calls can sometimes use unsigned uploads through a pre-configured upload preset instead.
Operational considerations
Picking the wrong API family for a given operation -- trying an Admin-only action through the Upload API, for instance -- is a common source of authentication errors.
Use cases
Direct API calls open flexible automation opportunities within Cloudinary ecosystems.
- Trigger custom transformations based on external events.
- Integrate Cloudinary actions with external workflow tools.
- Automate metadata enrichment via external services.
- Coordinate asset tagging with other systems during ingestion.