The CLI reads configuration from three sources. When the same setting appears in multiple sources, the highest-priority source wins.
The CLI looks for a config file at ~/.uploadcare/config.yaml. Here is a full example:
Environment variables are the recommended way to authenticate in CI/CD and containerized environments.
The CLI uses three authentication modes depending on the operation:
project info uses the REST API when called without arguments, or the Project API when
a project argument is given.
Project API tokens are not yet available in the dashboard. To get one, contact support at help@uploadcare.com.
Never commit API keys to version control. Use environment variables or a config file outside your repository. In CI/CD, store keys in your platform’s secret management system.
Get your API keys from the API keys page in the dashboard.
Manage multiple Uploadcare projects from one machine by defining named projects in your config file.
List available projects (requires a Project API token):
Add a project to your config and set it as default:
This creates a new API secret for the project, saves credentials to ~/.uploadcare/config.yaml,
and sets it as the default.
Switch between projects per command:
Example: staging vs. production workflow:
These flags are available on every command.