Devx09

Yes, I do. Using trade offer manager which uses steamcommunity with the new headers defined. Endpoints like offerslist however don't seem to be returning 429's, only the confirmations endpoints do. Are you not receiving any 429's yourself when trying to confirm offers?

Yes, didn't have these 429's yesterday with the same Proxy setup. All proxies are residential.

This seems to be a part of the solution. The confirmations are working like 60-70% of the time now but for the other 30-40% error 429 is still getting returned. Thank you for sharing though.

I'm having the same issues with my bots. I can also see that a lot of sites are struggling with trading bots while some have already adapted, likely need an update to steamcommunity package.

I noticed that many people are complaining about not getting their items at all after today's rollback, so it might be an issue on Steam side after all.

Hello, I have noticed that sometimes TF2 trades are being rollbacked by Steam and even though they have "tradeID", are rollbacked (can't be resent with identical same IDs, returns 26 when trying) and got state "6" (canceled) don't have any rollback information when I call getExchangeDetails. Is this a known issue or something new that needs fixing? My guess is that the v12.2.2 update that fixed corrupt data on normal trade offers doesn't consider rollback data and when it's corrupt - no data gets returned. (Just a guess at this moment)

Got the exact same issue, is there any other way to track the item?

Can I somehow get the trade hold in these 2 cases where I don't know the trade-link? 1) If someone sends my bot an offer. (I got the offer object and their steamid64 but not the token) 2) If my bot wants to send an offer to a person in the friend list. (I got their steamid64 but not the token)

Thank you lots.

Hello, I was wondering is there any other way to check if an user has trade hold without calling getUserDetails on the offer object? getUserDetails has new rate-limit settings which are to aggresive.

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.

Yup, same thing here, also running 2.11.3

I see, is it safe to assume that the item is marketable if "market_tradable_restriction" is above 0?

I believe this github issue was talking about this exact thing too, it's not all items, but I can provide more examples like this if needed. https://github.com/DoctorMcKay/node-steamcommunity/issues/329

Hello, I have noticed that when I get items from: getExchangeDetails() as ReceivedItems, when I iterate them and simply console.log them, I see this: It says "Tradable: false", but I just traded it and can trade it again. It says "Marketable: false", but I can sell it on SCM. This was not happening in the past. SCM link for the item: https://steamcommunity.com/market/listings/440/Unusual Taunt%3A Mourning Mercs Unusualifier