-
Notifications
You must be signed in to change notification settings - Fork 37
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
Steam Api Limit #20
Comments
I was confused while looking at the wiki: https://github.com/Revadike/InternalSteamWebAPI/wiki/Get-Market-Price-Overview ↗ Additionally, if we switch to using this API, we will lose the What are your thoughts on this? |
Based on my quick search, it appears that the Steam fee is fixed at 1.15. Therefore, the calculation for what you will receive after market fees is:
I found this information on the following page: https://www.tobyscs.com/calculate-steam-market-fees ↗ Considering this, it seems that the |
The |
And what about Currently we're using it to fetch the |
There is probably no alternative for The Also, you don't really have to check "every" item. It won't be that big of a deal if you miss some items since there are so many of them. |
Signed-off-by: hldh214 <hldh214@gmail.com>
Seems |
That seems like a much better solution than the one I purposed. Great work! |
refactor(steam): replace certain API calls to avoid rate limit (#20)
Due to recent changes to the steam api limitations, you are able to look up 1-2 items before your hit the request limit.
You seem to be using
/market/listings/{game_appid}/{market_hash_name}
in order to get the price of the items, which in my experience has a really small request limit, whilehttps://steamcommunity.com/market/priceoverview/?currency={currency}&appid={app_ip}&market_hash_name={name}
has a much larger request limit. Info gathered from herehttps://github.com/Revadike/InternalSteamWebAPI
I am not good enough with python to modify someone else's code yet, but I'm pretty sure the bot would work a lot better if you change the API end point.
Thanks
The text was updated successfully, but these errors were encountered: