Talk:Steam Web API

From Valve Developer Community
Jump to: navigation, search

Invalid JSON

The API for GetGlobalAchievementPercentagesForApp gives invalid JSON (not detected by JSONLint however). There's an incorrectly encoded UTF-8 character at around character 21,290 of [1] (see [2]). This stops it being parsed by JSON libraries (for example, PHP's json_decode). Not sure what character, will stick to XML results for now unless that's affected too. --Rmasters 12:42, 7 July 2010 (UTC)

These errors are in the XML as well as the JSON for this request so I'll run through them.
Line 1048, GetGlobalAchievementPercentagesForApp (xml) - Malformed XML
		<achievement> 
			<name>	<achievement> 
			<name>TF_SOLDIER_BUFF_TEAMMATES</name> 
			<percent>3.999221</percent> 
		</achievement>
Line 872 - Strange name? Not a constant like the rest (non parser-breaking)
		<achievement> 
			<name>Sapador e punhalada</name> 
			<percent>9.451244</percent> 
		</achievement> 
Line 272 - Empty <name> (more likely a non-printable character)
		<achievement> 
			<name></name> 
			<percent>19.812321</percent> 
		</achievement> 
Also got this error but not sure what to do with it
Entity: line 1050: parser error : Input is not proper UTF-8, indicate encoding !
Bytes: 0xE6 0x4B 0x3C 0x2F
--Rmasters 13:31, 7 July 2010 (UTC)

Steam Badges API?

Anyone got any news on whether or not an API will become available for the steam badges, trading cards and/or the player level/xp? --Roelof 07:26, 25 July 2013 (PDT)

Steam Market API Items Purchased and Sold

Is there an idea when an api will be available to pull information in regards to items purchased and items sold under the market, so a spread sheet can be created for users that have more than 200 items sold in a calendar year, so a developer can create a ledger/balance sheet for tax purposes.

New CAPTCHA to Steam Trade offers affects web applications using it?

Sorry about this really new post,
Just wanted to clarify if the new CAPTCHA system for accepting Trade offers will affect any HTTP requests accepting incoming trade offers.
If so, is there a solution to this problem?

NewBee (talk) 20:06, 9 January 2015 (UTC)

Change structure of documentation

I suggest creating subpages for each interface, and then another subpage of the interface for each method, for example:

`Steam_Web_API/ISteamUser` would be one page, listing all methods for that interface (and possibly describing it), and then another subpage, `Steam_Web_API/ISteamUser/GetPlayerSummaries`, listing the details for that method, e.g. parameters, description, example URL

--Th0masR0ss (talk) 21:53, 24 May 2015 (UTC)

Expose Public Tag Information for Games

With the addition of Steam Tags, along with Valve-defined tags, this information should be available for all.

One candidate is adding an additional parameter to GetOwnedGames (v0001), such as include_tag_info which, if defined, would list both user- and Valve-defined tags. Also, tags could be returned if include_appinfo is defined, as that is already a recognized flag:

 {
   community_tags: [
     {
       name: "fun",
       url: "http://www.store.steampowered.com"
     }
   ],
   valve_tags: [
     {
       name: "Single Player",
       url: "http://www.store.steampowered.com",
       image_url: "http://www.store.steampowered.com"
     }
   ]
 }