Rate Limiting 2023

Hello!

I'm developing a small app for a user to explore information about their games. My current understanding is to request each monthly archive to get all games for a user. To this end, I would like to make concurrent requests.

I am curious if there is additional information on rate limiting than what is provided in the docs. I see this thread from 2019 with some discussion-- There's mention of a concurrent request limit of three that may be changing to five. Is one of these concurrent request limits up to date?

I'd be grateful if anyone could share some information or their experiences on best practices for limiting async requests.

Thanks!

Rate Limiting

Your serial access rate is unlimited. If you always wait to receive the response to your previous request before making your next request, then you should never encounter rate limiting.

However, if you make requests in parallel (for example, in a threaded application or a webserver handling multiple simultaneous requests), then some requests may be blocked depending on how much work it takes to fulfill your previous request. You should be prepared to accept a "429 Too Many Requests" response from our server for any non-serial request that you make.

Hi Omed! Thanks for the reply. From the 2019 thread I linked above, it appears some provisions exist for parallel requests that the excerpt from the documentation you pasted does not cover. I am trying to understand what is allowed.

For example, if I were to receive a 429 response for one request, how long should I expect to wait before making the same request again?

I am trying to learn without stress testing the system because that would take away resources I don't need (but I do need the information the stress test would gleam!). So I would appreciate the knowledge if you know of any documentation of expectations or examples for dealing with a 429. Thanks!