-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does anyone have problems with the API method GetTradeOffers #382
Comments
me too... |
+1 maybe this is the steam problem? |
Yes, this is steam problem, but mb someone know how to fix it? |
I saw that Steam released a new update that affected scam projects and other skin exchange sites like market csgo |
Maybe it doesn't work anymore. |
This solution can temporarily serve as a substitute, looking forward to other's solution.
|
ty for code, do you have any idea how to parse the description of an item? |
I've done it completely, I can share it with anyone who needs it. |
please,need it. |
using profile or api ? |
Here he is)
|
Redo my code for yourself, because I only need partner items, and only skins from CS2 |
in the trade dictionary, you can see what my code can get from the trade |
market_hash_name = data['result'][str(item)]['market_hash_name'] data['result'] |
well, then there is no skin with such a class in the game with id 730, is everything written in error?) |
use web access token can get tradeoffer info at this time:
for webapi token
more details for web access token, see https://github.com/DoctorMcKay/node-steam-tradeoffer-manager/wiki/Access-Tokens |
thks bro! |
working good, thank you very much! |
could you create a pull request instead of having these snippets of code copy-pasted around? I don't think pasting the code in comments is the solution considering that people are starting to refer to comments instead of referring to tangible commits |
Indeed, please create pr so I can fix the issue |
{"response":{"next_cursor":0}}
I get empty messages when I try to request all trade offers
The text was updated successfully, but these errors were encountered: