HTTP error 429: Rate limits

[Sharp]

It appears Steam has introduced new dynamic rate limits which change during time of day and affect getTradeOffers and similar endpoints. The rate limits start up at around 9AM and they last till like 6PM UTC+0. It's still fine though, most requests (90%) appear to go through and overall is not a massive problem.

But I've noticed a new more persistent rate limit on the TradeOffer.getUserDetails endpoint. This appears to happen - (perhaps) after trying to fetch a non-working Trade URL - and then persistently for a long time you're getting 429s (hour/s). I'm not sure if the wrong trade URL fetch is the cause as that seems silly, but that's what I've heard from others -> perhaps someone has experimented with this and is willing provide more details?

[Devx09]

I'm having the exact same issue.
Polling randomly starts getting 429 from time to time and getUserDetails gets heavily rate-limited out of nowhere on some of my accounts.
Currently I only have 2 bad solutions:
1) Skip the getuserdetails (tradehold) check if 429 appears.
2) Rotate proxies. (This gets your account locked by steams support though)

They also started rate-limiting/banning a lot of residential proxies heavily. I can't even access inventories/market from some IPs for days.

edit: Actually this is possibly related to having a "bad ip" (an IP that Steam doesn't like) because I just tried using a proxy with an IP from my bot that is getting 429 on getUserDetails and I can't even access https://steamcommunity.com/market/, it says too many requests, try later. Sending offers & getting trade offers thru the bot works tho.

Edited yesterday at 11:27 PM by Devx09

[TheMaster]

the main problem is with this endpoint how can we fix this ?

https://steamcommunity.com/profiles/steamid/tradeoffers/privacy

@Dr. McKay

[Dr. McKay]

Why would you need to hit the /tradeoffers/privacy endpoint ever?

[TheMaster]

1 hour ago, Dr. McKay said:

Why would you need to hit the /tradeoffers/privacy endpoint ever?

we dont hit that when we call the method it calls that thats where the tradeurl is stored no?

    async function getTradeURL() {

        return new Promise((resolve, reject) => {

            community.getTradeURL((err, url, token) => {

                if (err) {

                    reject(err);

                } else {

                    tradeurl = url;

                    tradetoken = token;

                    resolve(url);

                }

            });

        });

    }

 

[achies]

Hi everyone. This is common issue right now, not only for node-steam users.

We are facing this problem within /market/* endpoints.
Nature of bans is not defined yet but proxy could be a reason

[Dr. McKay]

Just request the trade URL once and then cache it somewhere? It doesn't change after the first time you fetch it.