Skip to Content

Rate Limits

How the RIXL API signals throttling and how your client should respond.

The API may answer 429 Too Many Requests when it needs you to slow down, and 503 Service Unavailable when a backend is overloaded. A 503 from the API carries a Retry-After header with the number of seconds to wait. A 429 carries one only when a retry can succeed soon; without it, the limit is a long cooldown and retrying won't help.

What Your Client Should Do

  • Honour Retry-After when present, then retry as described in Retries.
  • Cap concurrency, and batch or cache reads where you can.