All Activity

It means you need to have an established connection to a CM (the same servers the Steam client logs into) in order to refresh the token. You can use steam-user to do this if you want. What do you mean by "log in using the refresh token"?

If you're trading CS2 items, you'll need to enable the useAccessToken option in the TradeOfferManager constructor.

It wouldn't hurt to clusterize things, but either way things should generally work fine without need for much hardware.

Seems like event newOffer is not working at all

Hi everyone. Please, could you help me or just explain why am i facing with the next problem. Explanation: 1) I've installed all of the requirements npm install steam-user steamcommunity steam-totp steam-tradeoffer-manager npm WARN deprecated [email protected]: This package is deprecated. Use destructuring assignment syntax instead. npm WARN deprecated [email protected]: this library is no longer supported npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142 added 145 packages, and audited 146 packages in 9s 3 packages are looking for funding run `npm fund` for details 8 vulnerabilities (3 moderate, 5 high) Some issues need review, and may require choosing 2) right after copied examples/storehouse-steam.js from the official git, filled the authorization data Login Password And sharedsecret 3) Started the code. 4) Then i saw 5) After that i've sent tradeoffer from my second account to the bot's account, waited 10 minutes, and nothing happened. Example code didn't accept my tradeoffer or even didn't write about trade offer, litteraly nothing happened. I tried to switch on examples/storehouse-steamcommunity.js to try, but the same result. I even tried to add this code in the example client.on('webSession', function(sessionID, cookies) { manager.setCookies(cookies, function(err) { if (err) { console.log(err); process.exit(1); // Fatal error return; } console.log("Cookies set"); }); community.setCookies(cookies); manager.getOffers(1, function(err, sent, received) { if (err) { console.log('getOffers error:', err); return; } console.log(`Found ${received.length} received offers`); received.forEach(offer => { console.log(`Offer from ${offer.partner.getSteamID64()}, state: ${offer.state}`); }); }); }); and after i reloaded the code without cancelling existing tradeoffer. And the bot sees the active tradeoffer and printing in the cosole offer from [steamid] state: Active. May be it is known problem and im not the first one?

help me please

According to the docs the CM must be authenticated. What does this mean? Does it mean only a valid Steam client (Steam Desktop Client) can be used? Can it be spoofed? I also tried to use k_EAuthTokenPlatformType_MobileApp but for some reason I get EResult 5 (k_EResultInvalidPassword) when I try to log in using the refresh token. Works when I switch back to SteamClient but then I can't refresh the token

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)

Yes, I use node-steamcommunity. Requests will be frequent on all bots. Thanks, so I need to provide a proxy server for each account. What about the cluster? Will it be redundant? The problem is that I don't understand what kind of power I need. I've had a couple of bots for a long time now, and everything was fine on a cheap vps, but now I want to make more bots, but I'm afraid to run into the limitations of single-threaded of node.js

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

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

Thank you lots.

It depends on what you're doing and how you're doing it. If you're using node-steamcommunity for all those accounts, you're going to hit rate limits unless you're performing actions infrequently. And if you're logging in that many accounts from one IP, that'll rate limit you as well.

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); } }); }); }

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

https://steamapi.xpaw.me/#IEconService/GetTradeHoldDurations

I've noticed that for some Dota2 items I have to wait 7 days to list on the community market while some are immediately marketable. Is there a way to check if a Dota2 item not in my inventory will have a market restriction or not?

the main problem is with this endpoint how can we fix this ? https://steamcommunity.com/profiles/steamid/tradeoffers/privacy @Dr. McKay

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 writing a farm and I have about 50 steam accounts. At the moment, it looks like this: I made a store where I put each logged-in account, then I use the steamid to access the desired one and perform an action. const BotInstance = new Bot('login', 'password', 'shared_secret', 'identity_secret', 'steamid'); const newBot = await accountsStore.add('steamId', BotInstance); newBot.login(); const getBot = await accountsStore.get('steamId'); getBot.addFriend('friendSteamId'); How would it be more efficient to leave it as it is or implement it all through a cluster? what kind of power is needed to support such a large number of accounts? and won't I have a problem if they're all on the same ip?

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.

Having similar issue when logging in my accounts with refreshtokens, sometimes it stucks and i dont get any response in any possible events like "error" "disconnected", "loggedOn" debug after stuck looks like (could be wrong lines but anyway) [W189861] WebSocket closed by remote with code 1000 and reason "" [W189861] Handling connection close Disconnecting Sending message: ClientLogOff Disconnecting without sending logoff [W189861] We wanted to end connection, but it's not connected or connecting Disconnecting [W189859] We wanted to end connection, but it's not connected or connecting [W189859] We wanted to end connection, but it's not connected or connecting Disconnecting [W189860] We wanted to end connection, but it's not connected or connecting [W189860] We wanted to end connection, but it's not connected or connecting Disconnecting [W189861] We wanted to end connection, but it's not connected or connecting [W189861] We wanted to end connection, but it's not connected or connecting webCompatibilityMode is true, with false is the same

I need a function for quickly selecting passwords for family sharing

mea culpa, I've forgotten to thank you for this advice, thank you, it helped

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?