The cloro API uses Bearer token authentication. Create and manage your keys in the dashboard.
Using your API key
The Bearer token in the Authorization header is your API key — there’s no separate token exchange or OAuth flow. Copy the key from the dashboard and pass it directly with the Bearer prefix on every request:
Never expose your API key in client-side code or public repositories, and
never share it with unauthorized users. Keep it in a secrets manager or an
environment variable, not your source tree.
Authentication errors
If authentication fails, you’ll receive a 401 Unauthorized response:
Common causes:
- Missing Bearer prefix: include
Bearer before your API key
- Invalid API key: check that you’re using the correct key
- Expired API key: some API keys have expiration dates
- Rate limit exceeded: you’ve exceeded your plan’s rate limit
Environment variables
API key management
If you suspect a key has been compromised, revoke it and generate a new one in the dashboard.
You can also create multiple keys for different purposes: one for your live application, one for local development and testing, one for automated testing and deployment pipelines, and individual keys for team members.
Need help?
- Check our API Reference
- Get help: paid plans via the in-dashboard support widget, free tier via the Ask Assistant button in these docs