Dr. McKay

Correct.

steam-user communicates directly with the Steam backend using the same protocol as the Steam client, which is not HTTP. Some Steam endpoints are available both via the Steam client and the WebAPI, but this particular one isn't. ICommunityService/GetAppRichPresenceLocalization would be the URL if this one was available via WebAPI, but it's not.

Use getExchangeDetails.

Those are the asset IDs before the exchange happened, not after.

It works for one-sided trades as well. An exchange is still an exchange, even if one side is empty. Extracts the ID how?

Either use getExchangeDetails or use your access token to access the WebAPI.

Yes, Node is very different from C#.

Enable the useAccessToken option.

This was an intentional change by Valve.

https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/TradeOffer#getexchangedetailsgetdetailsiffailed-callback

Garbage is only collected periodically. If you want to fetch that much data in Node, you're going to need more than 200 MB of RAM.

Not possible without calling additional methods, no.

https://github.com/DoctorMcKay/node-steam-user#getownedappsfilter Don't call getOwnedApps until after the ownershipCached event is emitted. Also, it doesn't take a callback argument.

You can't. This is a Node.js module only.

Gotcha.

https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/TradeOfferManager#getofferid-callback

You're treating the symptom, not the cause. There's no scenario where this.partner should be undefined or otherwise invalid unless you're doing something wrong.

steam-session is a Node.js module, not a browser module.

?? What does this have to do with steam-session?

Show how you're creating a trade offer (new TradeOffer(...))

If you don't have the user's SteamID at all in any form, no.

GetTradeHistory does appear to accept an access token to retrieve all trades.

You need to report that you're in CS2 by calling user.gamesPlayed(730), then complete the GC handshaking process before sending any other GC messages. For CS, this is sending ClientHello (4006) with the proper version number and waiting for ClientWelcome (4004) in response. You can check node-globaloffensive for reference.

Contact your proxy provider.

Sounds like someone with control of your network is trying to modify traffic.