Why should each service have its own API key?

Giving each service, environment or job its own key has three benefits:

1. Smaller blast radius. If the CI key leaks, you revoke it, and production keeps running.
2. Readable Logs. The Key column shows which service made each request, so you can see what costs what.
3. Separate rate limits. Each key has its own requests-per-minute limit, so a busy job can't starve another service.

Remember the limit of 25 keys per account, which is plenty for most setups.

Good to know#

• Never put a key in front-end code, a mobile app, a public repo or a screenshot.
• Every API request sends your key and your Account ID (X-Clatter-Account: CL-…); a key alone is refused.

Learn more#

• Limits and best practices
• API keys guide
• Abuse policy

Still need help?#

• General support: support@clatterlabs.com or team@clatterlabs.xyz
• Infrastructure questions, or permanent deletion of your data (your whole account or one service): infrastructure@clatterlabs.xyz

We usually reply within the first hour, and always within 24 hours. A full support team is with you.