Dr. McKay

It's in the tags property of the item object.

I believe the only way to do that is to use the WebAPI.

I don't believe it's currently possible with new Steam chat.

Is your account limited?

This sounds a lot like spam.

Plain trading sites are generally okay.

People generally use the request module to make HTTP requests.

There's a separate secret that's used for confirmations; it's not the same as the one you use to login.

If you called login without providing an account name or password, then you've logged into an anonymous account. You can do a few things from anonymous accounts, but not all that much. If you want to login to a Steam account, you need to enter the account's name and password. It doesn't matter what account you use, but it needs to be one that exists. If you're creating a bot, most people create a separate, dedicated Steam account for it.

If you try to use two different devices to accept confirmations, you tend to miss confirmations on one device or another. It's not a good idea at all. That said, the error you're getting isn't due to this. It's because your app is either using the wrong secret, or the clock is wrong.

Can you try calling manager.doPoll() yourself?

node-steamcommunity is a Node.js module. It does not work in the browser, even if you use something like browserify.

steamcommunity.com/gid/

Attach a callback to setCookies and see if you get an error back.

Can you add this code and provide the output? manager.on('debug', console.log);

Added, sorry it took a while.

Automating reports/commendations is one thing I won't help with.

I don't believe it was ever officially supported, so I wouldn't be surprised if they removed the backend code for it.

It would be possible.

If it helps any, the amount of XP needed to reach the next level goes up by 100 every 10 levels. So the amount of XP you need to reach level X is 100 + (floor(X / 10) * 100).

That code looks right. You're probably being rate-limited by the GC. Valve is big on making it only possible to get data one way, then rate-limiting that one way to hell. What happens if you delay 10 seconds between items?

I can't reproduce this: const SteamUser = require('./index.js'); const SteamTotp = require('steam-totp'); const TradeOfferManager = require('steam-tradeoffer-manager'); const SHARED_SECRET = "redacted"; let user = new SteamUser(); let manager = new TradeOfferManager({ "domain": "doctormckay.com", "steam": user }); user.logOn({ "accountName": "redacted", "password": "redacted", "twoFactorCode": SteamTotp.generateAuthCode(SHARED_SECRET) }); user.on('loggedOn', () => { console.log("Logged on"); }); user.on('webSession', (sessionID, cookies) => { console.log("Web session id " + sessionID); console.log(cookies); manager.setCookies(cookies, (err) => { console.log(err); console.log(manager.apiKey); }); }); I don't think you ever needed it to send trades as long as steamLoginSecure has existed... if you're on a secure connection it ignored steamLogin. You don't need to run your website over HTTPS (although you really should); all connections to Steam have to be done over HTTPS (which my modules have done as long as they could).

steamLogin probably went away because Steam can only be accessed over HTTPS now. browserid is unnecessary.

How are you calling the function?

Seems like you're doing it right. Valve probably disabled it.