Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Originally posted by Sneeza™:
I've already reported this to Valve. The CS:GO official API is returning empty objects 95% of the times, which is why you're seeing this error message.
Other sites rely on the private Steam Community API but it isn't really meant for third-party use, so I stuck with the official API because I figured that would be more sensible. Turns out it has more issues, so I kind of shot myself in the leg.
I manage the website p337[dot]info\condition where you can see the condition / quality of your csgo skins, and the API that stores these float values is absolute rubish.
not advertising, just stating my experience with this API
it is complete rubish, valve need to fix it, but there are other workarounds in the time being.
What the devs need to do is set up a caching system so when it fails to load your backpack, you at least get to see an old copy of your CSGO inventory.
For reference the API is the following web service from valve
https://steamhost.cn/api_steampowered_com/IEconItems_730/GetPlayerItems/v0001/?key=[SteamAPIClientKey]&steamID=[SteamUserID]
This is the only API that tells you what quality your skin is, its also much better formatted to read what stickers are attached.
Another alternative however would be to read the steam inventory API
which just gets peoples public backpacks in json format.
This is a really frustrating issue to face, considering that there are at least 2 options around it that the outpost devs could do