Few bits of Feedback

#1 - Aug. 10, 2012, 6:43 p.m.
Blizzard Post
Before I start, first off, let me say how awesome it is that you and your team have an API available like this for those of us that develop fansites, much thanks! I've started digging into the API now for D3Up.com and I've noticed a few things I'd like to mention.

Right now all of my feedback is involving the item API results.

#1 - There's no "Type" associated with the results

I thought I could get by using the "Icon" field instead of requiring a type field, but the icon field isn't really that parsable. The first test I did was against a wizard hat, which was wizardhat_###, which worked great. Split the string via underscores and take the first part, now I know it's a Wizard Hat item type. But then further along, I ran into amulet13.

Anyway we could get the item's type pushed out in a field of it's own? The actual HTML rendered tooltips have the type of the item in them, so I figured the data's there, just not exposed!

#2 - The socketEffects array seems to be empty, even if there's a gem in the socket.

The helmet I'm wearing has a socket with a +16% life gem in it, but in the JSON results, the array is empty.

Here's a link to the item's API call.

http://us.battle.net/api/d3/data/item/CIKr_NgFEgcIBBWDsaRoHVugG9gdKRJz4B1l3mdxHe0woCgdhgJj6h05byLFIgsIARWIQgMAGAAgHjAJOFxAAEgDUBBg8gJqIQoMCAAQ6uqK1YCAgOA4EhEIABIHCAQVz122ejAJOABAAQ

I'm sure I'll come across more things, but for now, those were the two glaring issues I had with parsing the item data :)

Thanks again!
Forum Avatar
Web & Mobile Team
#2 - Aug. 10, 2012, 6:48 p.m.
Blizzard Post
Thanks for this immediate feedback. We are working on a small patch to fix some bugs with the Item Information API. I'll be sure to incorporate this as well.
Forum Avatar
Web & Mobile Team
#4 - Aug. 10, 2012, 7:13 p.m.
Blizzard Post
Hmm.. so you changed the keys to use lower camel case instead of dashed seperated words, that means that the docs (preview, ha -- sorry, I couldn't resist) are mostly inaccurate (<3 sed!). The same is true for the previewed progression value.

But anyway, you missed one key (haven't looked closely enough to be honest).

- Hero json: last-updated should be lastUpdated
- Career json: stepMurrent (artisans/hardcoreArtisans) should be stepCurrent


They shouldn't be largely inarticulate, just that one block demonstrating what a career response should look like.

We are aware of those two typos. :)