As of around a month ago, various Steam endpoints, including /ISteamUser/GetPlayerSummaries/v2/, will randomly return 429 rate limit errors. From crowdsourcing information from various Steam service providers, such as marketplace maintainers, the common consensus is that these rate limits are completely random and are not based on any actual rate limit logic.
From our observations, a 429 error can be returned from the first API call or randomly throughout many requests.
Since this issue has not been resolved by Valve for many weeks, it may be something that continues to exist for the foreseeable future. As a result of the randomness of these 429 errors, the common consensus is to build in retry behavior, which falls back if 429s are consistently being served to avoid escalating the issue needlessly.
Ideally, it would be good to add retry and backoff behavior to this package. If needed, I can try to push a fix myself.
Thank you in advance for maintaining @Nekonyx :)
As of around a month ago, various Steam endpoints, including
/ISteamUser/GetPlayerSummaries/v2/, will randomly return 429 rate limit errors. From crowdsourcing information from various Steam service providers, such as marketplace maintainers, the common consensus is that these rate limits are completely random and are not based on any actual rate limit logic.From our observations, a 429 error can be returned from the first API call or randomly throughout many requests.
Since this issue has not been resolved by Valve for many weeks, it may be something that continues to exist for the foreseeable future. As a result of the randomness of these 429 errors, the common consensus is to build in retry behavior, which falls back if 429s are consistently being served to avoid escalating the issue needlessly.
Ideally, it would be good to add retry and backoff behavior to this package. If needed, I can try to push a fix myself.
Thank you in advance for maintaining @Nekonyx :)