Dr. McKay

https://www.google.com/search?q=node.js+screenshot&ie=utf-8&oe=utf-8

All you have to do is call startConfirmationChecker first. You can do it synchronously.

You don't want to use instanceid to identify a type of item. See here: https://dev.doctormckay.com/topic/332-identifying-steam-items/

It does take the cookies, but calling manager.setCookies is still important as that's when it grabs the API key.

I'm not sure I 100% understand. Let me clarify a couple things. SteamTrades is what you get back from require('steam-tradeoffer-manager'), yes? Are you calling manager.setCookies anywhere? What's your console output?

There isn't.

You'll have to ask them how they do things.

You can't get the new item IDs for sent items, no.

It's unfortunately not possible. getUserDetails just loads the offer UI page, which is inaccessible once you're unable to act on the offer (e.g. you send it [outgoing] or you accept it [incoming]).

Most people use the steamcommunity.com JSON inventory endpoint: https://steamcommunity.com/profiles/STEAMID/inventory/json/730/2/node-steamcommunity has a method for this. Example: community.getUserInventory("[U:1:46143802]", 730, 2, false, function(err, inventory) { console.log(inventory); });

I believe this is caused by your calling checkConfirmations without having started the confirmation checker first. This isn't supported behavior. Do you want it to be?

It's the "region code" assigned to you by Steam. Changing it is useless.

I want to know what you're using node-csgo for.

Please update to steam-user v3.10.0 and this should be fixed.

Sure thing.

That looks fine to me.

It was, he's probably still on v1 for whatever reason.

Sounds like it's neither failing nor going into status "sent". As you're sending items, the offer requires confirmation and so the status will be "pending".

Can I ask what you're trying to do with it?

Yes, it's because you're friends. The trade URL is wrong.

You need to do it yourself.

You're treating the symptom and not the problem if you do that. The problem, as given by the HTTP status code, is that you're making too many requests. Slow down.

I'm pretty sure it means that you've made too many requests in a short time, and consequently your IP has been temporarily blocked.

They should.

You... recheck it again later.