JVz

there is always risk of getting banned with steam

do you have 100% success rate? it's still gives me rate limit from time to time

receiving ofc. Trying to find the way to minimize it

do you call other api endpoints on same proxies? inventories, offerslist and so on

do you use 1 account per 1 proxy?

here is easy fix: const request = require('request'); const SteamCommunity = require('steamcommunity'); let community = new SteamCommunity({ request: request.defaults({ headers: { 'Accept-Encoding': 'gzip, deflate, br' } }) }); if you use proxy: request: request.defaults({ proxy: proxyUrl, headers: { 'Accept-Encoding': 'gzip, deflate, br' } }) This is not rate limiting. Steam's WAF now fingerprints the Accept-Encoding request header. The legacy request package (which node-steamcommunity uses internally with gzip: true) sends exactly Accept-Encoding: gzip, deflate — real browsers always include br as well. Steam now rejects the bot-like values outright: Accept-Encoding sent Response gzip, deflate (request lib default) 429 gzip 429 gzip, deflate, br 200 gzip, deflate, br, zstd 200 Same IP, same endpoint, seconds apart — only the header changes the outcome. api.steampowered.com is not affected.

any ideas where we can get new_assetid?

its based on trades that were made more than a week ago so they are not on hold anymore

new_assetid should be present after trade hold ends

looks like steam changed something for cs trades. Still works fine for dota2

When using EAuthTokenPlatformType.SteamClient I'm trying to call webLogOn to obtain new access token for already logged in account, but webSession event gives same steamLoginSecure cookie as before with different sessionid and clientsessionid; and after around 24 hours it becomes invalid an webLogOn starts to throw 403 error

my bad, I've changed log level of newOffer to debug, and didn't check debug logs

After cs2 trade hold update my bot stopped receiving "newOffer" event for counteroffers

Am I trippin or steam added new fields to GetTradeOffer API? eresult: 1 delay_settlement: true

yep, if you will find other endpoint that will give info about trades on hold let us all know. GetTradeHistory isn't convenient for our use case