How should I set up keys for development, staging and production?

1. Production — "Backend (production)", only the permissions it needs, a rate limit that fits real traffic, expiry 1 year with a rotation reminder.
2. Staging — "Backend (staging)", same permissions, lower rate limit.
3. Development — one per developer ("Sara · local"), short expiry (30 days).
4. CI — its own key, often just Code Buckets permissions.

On a team, developers can create their own keys under their own accounts; their usage still runs on the team's credits and shows their name in Logs.

Good to know#

• Keys can expire after 30 days, 90 days (default), 1 year, or never.
• Revoking is immediate and permanent: requests fail with 401 invalid_api_key.

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.