How should I name my API keys?

Names are only for you, but good names save time when you need to rotate or revoke something fast. A name can be up to 64 characters.

Good patterns#

• What + where: "Backend (production)", "Backend (staging)"
• Job: "CI uploads to Code Buckets", "Nightly report"
• Person + purpose for experiments: "Sara · local testing"
• Date for rotations: "Backend (2026-11)"

Avoid#

• Vague names like "test" or "key 2".
• Putting secrets or passwords in the name.

Good to know#

• Each key has its own rate limit: 10, 30 (default), 60 or 120 requests per minute.
• Keys can expire after 30 days, 90 days (default), 1 year, or never.
• Every API request sends your key and your Account ID (X-Clatter-Account: CL-…); a key alone is refused.

Learn more#

• API keys guide
• Rate limits
• Console › API keys

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.