429
Too Many Requests
rate_limited — Rate limited
Message
What causes it
- More than 60 requests per minute to `/api/v1` from one IP, more than 600 per hour for one API key, or more than 300 requests per 5 minutes to the whole app from one IP.
- Fifteen or more unknown bearer tokens from one IP within five minutes — a 15-minute ban with the message "Too many failed authentication attempts. Retry later."
How to fix it
- Honour the `Retry-After` header (seconds) before resending; back off exponentially on repeated 429s.
- Poll executions no faster than every few seconds, or subscribe to webhooks instead of polling.
- Stop and fix credentials on the first 401 rather than retrying with variants — the failed-auth ban counts unknown tokens, not expired ones.
Operations that return it
Any operation can return this code.
See the API reference for the full list of operations.
Example response
HTTP/1.1 429 Too Many Requests
· Content-Type: application/json
· Retry-After: 60
429 Too Many Requests
{
"error": {
"code": "rate_limited",
"message": "Rate limit exceeded. Retry later.",
"details": [],
"request_id": "6f1c2a3e-8d4b-4c5e-9f0a-1b2c3d4e5f60",
"doc_url": "https://cascades.crscreditapi.com/docs/api/errors/rate_limited"
}
}