Avoid Error 429 Too Many Requests when loading large inventory
See original GitHub issueSteamCommunity.prototype.getUserInventory:
https://github.com/DoctorMcKay/node-steamcommunity/blob/2bbdbf36adf71d89c1f3144031821463face092c/components/users.js#L384
maybe it is worth adding a delay? I don’t know the exact rate limit to avoid 429
setTimeout(get, DELAY, inventory, currency, body.more_start);
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
How to Fix 429 Too Many Requests Error - Kinsta
1. Change Your WordPress Default Login URL ... Brute-force login attempts are one of the leading causes of the 429 error on WordPress...
Read more >How to Fix 429 Too Many Requests Error Code - Hostinger
Don't know how to deal with the 429 too many requests error? We'll share the six effective solutions to diagnose and resolve it!...
Read more >429 Too Many Requests - Clover Developer Docs
A 429 error is returned when your app has made too many requests and exceeded the server's rate limit.
Read more >429 Too Many Requests - HTTP - MDN Web Docs
The HTTP 429 Too Many Requests response status code indicates the user has sent too many requests in a given amount of time...
Read more >I'm getting 429 error working with SteamWebApi (CSGO ...
The cause are too many of your requests in too short a time. The Steam servers accept 200 request in five minutes or...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Parts of Steam break all the time. getUserInventoryContents is more stable than getUserInventory since it’s not rate-limiting you when you try to load a large inventory. If the GC goes down, then naturally getUserInventoryContents isn’t going to work when it tries to contact that GC. The old endpoint is likely just serving up its stale cache when it can’t contact the GC, which means it’s giving you outdated information without any indication that it’s outdated.
If you can tell me exactly what delay prevents you from getting rate-limited, and if it’s a reasonable length of time, then I’ll consider adding it. I’m not going to spend any of my personal time updating a deprecated, unstable endpoint though.
Steam changed once again rate-limits, see existing PR on node-steam-tradeoffer-manager
https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/pull/330