How should my app back off on 429?
- On
429 rate_limited, readRetry-Afterand wait that many seconds. - Retry once; if it fails again, wait again (don't loop instantly).
- Better: avoid the 429. Track
X-RateLimit-Remainingand slow down near zero, or cap concurrency (for example with a semaphore or a queue).
OpenAI SDKs retry 429s automatically with backoff, but tight loops of your own on top can make things worse.
Good to know#
- If calls fail unexpectedly, check status.clatterlabs.com before debugging further.
- Keep keys on your server, never in a browser or mobile app. Why
- Every call shows in Console › Logs and Usage as Model API, with its price. See what you spent
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.
Related articles
Still need help?
Tried the steps above and still stuck? Email us. We usually reply within the first hour, and always within 24 hours. A full support team is with you.
Infrastructure questions, or permanent deletion of your data
infrastructure@clatterlabs.xyzFor deleting your whole account or the data of one service.