How do I use an API key safely in CI/CD?

1. Create a dedicated key (e.g. "CI uploads") with only what the pipeline needs.
2. Save the key and your Account ID as secrets in the CI system.
3. Read them as environment variables in the job; never print them.
4. Don't expose secrets to builds from untrusted forks or pull requests.
5. Set an expiry and rotate on schedule.

Good to know#

• Never put a key in front-end code, a mobile app, a public repo or a screenshot.
• Give each integration its own key with only the permissions it needs.
• If a key may have leaked, revoke it first, then replace it.

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.