Jmopel

That sounds an awful lot like spam.

Yes, steam-client is obsolete with v4. It's built into steam-user now. And user.setHttpProxy isn't going to work. You should use:
let user = new SteamUser({ debug: true, singleSentryfile: false, autoRelogin: true, dataDirectory: '/files/clients', httpProxy: proxyUrl });

This is normal. When a trade is completed, the Steam backend makes two HTTP requests to the item server per item, and those requests aren't quick (something in the ballpark of 500ms per item I think). So if you're doing a really big trade, the request in which it's completed (if the offer recipient is only receiving items, the request to accept the offer, otherwise, the request to confirm it) will timeout after 30 seconds, but the trade will keep committing on the server. And it seems that while a trade is committing the rest of the API gets cranky for your account, probably because it doesn't feel like playing ball while a trade is in progress.

Yes, because ignorant coders will almost definitely start passing API keys that don't belong to the account they're signed into, and start posting GitHub issues asking what's going on.
 
If you know what you're doing, you can set the apiKey property directly with the correct key, but please make sure you actually know what you're doing.

Hi, thanks for reply, yes I ended up doing it directly:
 
user.on('webSession', function(sessionID, cookies) { console.log(data.login+': Got webSession'); manager.apiKey = data.api_key; manager.setCookies(cookies, function(err) {}); community.setCookies(cookies); }); Yes, I manually generate the API KEY (Because I use same KEY for LOGIN) just less request and hassle because I know the API KEY.
 
Thank you.

Added BBCode parsing to new Steam chat messages Added ability to interact with a GC  
View on GitHub