My API key leaked. What should I do?

Act in this order:

1. Revoke the key in Console › API keys. Requests with it fail at once.
2. Create a new key and update your app.
3. Check Console › Logs and Usage for calls you don't recognise.
4. Remove the key from wherever it leaked (git history, CI logs, a shared doc). Removing a commit doesn't undo the leak, which is why revoking comes first.

Also remember that someone using a leaked key with your Account ID sends text on your account's behalf. If anything looks wrong, write to support@clatterlabs.com with your Account ID and the times involved.

Good to know#

• Each key has its own limit: 10, 30 (default), 60 or 120 requests per minute. Rate limits
• If calls fail unexpectedly, check status.clatterlabs.com before debugging further.
• New accounts get $5 of free credit; top up from $1 to $800 per purchase in Console › Billing › Credits. Billing

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.