When it fires
The API could not check your rate limit for this request because the rate-limiting system was briefly unavailable. Rather than serve the request without enforcing your tier’s limit, the API refuses it with a retryable error. This is short-lived by design. If the rate limiter stays unavailable, the API stops returning this code and serves requests without limit enforcement until it recovers.Why it happens
- A momentary infrastructure blip, usually cleared within a fraction of a second.
- Contention during a very large burst of traffic.
How to fix
- Honour
Retry-After. The TypeScript SDK retries 5xx responses with exponential backoff by default, so most occurrences never reach your code. If you disabled SDK retries (maxRetries: 0), add your own backoff. - Don’t treat it as quota exhaustion.
RATE_LIMIT_EXCEEDED(429) means you are over your limit;RATE_LIMIT_UNAVAILABLEmeans the limit could not be checked. Don’t show it to users as a quota event. - If you see these steadily for several minutes, contact ZeroID support with a
requestId.
Response headers
Retry-AfterX-RateLimit-*headers are not sent on this response, because there is no quota answer to report.
Related codes
RATE_LIMIT_EXCEEDED— 429, you are over your limitDEPENDENCY_UNAVAILABLE— 503, another dependency is unavailable