Errors and limits
Distinguish access denials, rate limits, and service outages.
| Status | Integration action |
|---|---|
400 | Correct the input to match the operation's schema |
401 | Check the secret, expiration, and environment; do not retry automatically |
403 | Check the key's scope and the user's current permissions |
404 | The resource does not exist or is not visible; do not treat this as confirmation that it exists |
429 | Wait for the duration specified by Retry-After before retrying |
5xx | The service is unavailable; show an error state and retry reads cautiously |
The initial limit is 120 requests per key in a 60-second window starting with the first accepted request. Later requests do not extend the window. All auth replicas share the same Redis counter. If the counter is unavailable, authentication returns 503 instead of bypassing the limit. Operation-specific limits still apply. Do not bypass them by creating additional keys.
Do not turn a failed data fetch into an empty list. Keep the last result marked as stale, or show that data is unavailable. For writes, losing the response does not prove that the operation failed.