Dr. McKay

DuplicateRequest
 
You can't enable 2FA if you already have 2FA enabled.

^ You need to either use node-steam-user or call the GetFriendList WebAPI method.

var CMClient = require('steam-client').CMClient; var SteamUser = require('steam-user');   var client = new CMClient(); client.bind('192.168.0.2');   var user = new SteamUser(client);

You can use getPersonas to get persona data. Off the top of my head (this might not work), getting an avatar URL would go something like this:
user.getPersonas(["76561198006409530"], (personas) => {     var hash = personas["76561198006409530"].avatar_hash.toString('hex');     var url = "https://steamcdn-a.akamaihd.net/steamcommunity/public/images/avatars/" + hash.substring(0, 2) + "/" + hash + "_full.jpg"; });

You need to wait until the loggedOn event is emitted.

Show your code. If your code is right, then your secret or your clock is wrong, or you're trying to reuse a code.

I've made a new pinned post detailing this: https://dev.doctormckay.com/topic/289-trading-and-escrow-mobile-trade-confirmations/

Officially there's a 100,000 request-per-day limit, but besides that there's no IP/key rate-limit or throttling.

SteamCommunity doesn't save anything to disk on its own. One of the examples might, but you can change it easily.

Check the appid property of all the items in the offer.

If you're using the mobile authenticator then logging in from a new device doesn't have any trade cooldowns.

Set a language and the objects in the arrays of items (itemsToGive and itemsToReceive) will have names in them.

Use update. That will update the offer from the API.
 
 
offer.update(function(err) {     if (err) {         console.log(err);     } else {         // now the offer is fresh from the WebAPI     } });

The only way I was able to reproduce this was by trying to log off without first being logged on. Please make sure you aren't doing that.

You can use steam-totp along with your shared_secret.

The documentation suggests that you don't go lower than 10 seconds.

Yes. Offer data is stored in poll data, so as long as you're saving and restoring poll data, then the offer's data should be available forever.

Using the Steam client is the fastest way to get notifications, but you still need polling to make sure you get everything (Steam doesn't send notifications when offers you send in which you receive no items are accepted, for example). Polling every second is overkill, but is possible.

Your own account? Or someone else's account?
 
If you want games someone else owns, there's a WebAPI method for that.

1. Calling login() again with your username and password is guaranteed to renew your session (unless Steam is having problems). The oAuthLogin method is supposed to do this, but I believe it doesn't work 100% as expected.
2. There isn't any event. Currently you just have to check loggedIn every so often. The next update will most likely add such an event.

Just pass true for that argument, and in the callback the items will have an actions array defined and populated with the inspect link (and any other applicable actions).

Yes, that will work fine.
 
Note that on Windows, the sentry (ssfn) file that the client uses is hidden. The visible one is a decoy.
 
The sentry file used by the client is named in config/config.vdf (if I remember correctly).