skins.json and skin_details.json!

#1 - April 18, 2014, 11 a.m.
Blizzard Post

Bored at work, on a whim I decided to just type “skins.json” into the URL. And whaddaya know, it worked!

https://api.guildwars2.com/v1/skins.json

Okay, how about skin_details.json? Yep!

https://api.guildwars2.com/v1/skin_details.json?skin_id=1343

The details appear to be a stripped-down version of item_details.json. I haven’t attempted to process everything yet, but here’s what I’ve seen so far:

{
skin_id: integer,
name: string,
(maybe) description: string,
type: enum(Armor, Back, Weapon),
flags: [any(“ShowInWardrobe”, “HideIfLocked”, “NoCost”)],
restrictions: [<race>],
icon_file_id: integer,
icon_file_signature: string,
(maybe) armor: { type: <armor_subtype>, weight_class: <armor_weight>},
(maybe) weapon: { type: <weapon_subtype>, damage_type: <damage_type> },
}

I’d guess that type can also be Outfit or Back, but I haven’t found any of those yet since there are so few compared to armor and weapons.

[edit] Found type:Back, does not have a back:{} sub-object.

[edit2] Found flag HideIfLocked, seems to be on most gemstore skins. This explains all the people on reddit who couldn’t unlock a quaggan backpack (because they hadn’t opened the container yet) and also couldn’t see it in the wardrobe.

[edit3] Doesn’t look like outfits are in here at all.

#4 - April 18, 2014, 12:26 p.m.
Blizzard Post

Ya, you guys found it before I could document it. Was part of the item “name” fix and a result of the wardrobe feature. I’ll get some documentation up on the API wiki today (unless someone beats me to it).

As you can see it isn’t very interesting yet since you can only cross-reference skins that are the ‘default_skin’ of certain items. But will be more useful once we ship APIs that show personalized items, such as the /characters API.

#13 - April 18, 2014, 6:30 p.m.
Blizzard Post

Stefan, you might not be the right person to ask it, but…

Could you tell us if this problem (transmuted weapons receiving name from stats item and not skin item) is a temporary bug or an intended change? We, the aesthetics-driven people, are really saddened by this change and would appreciate any official news. Thanks!

The API bug and the transmutation bug(if it is a bug) were unrelated. The API bug was patched last hotfix.

Hi Lishtenbird,

Yes, this isn’t the correct forum. But I went ahead and inquired internally here to someone who might know. In short, this can be considered a bug, but one that is not easy or fast to fix. There is a desire to address this along with some other improvements to the tool tips of transmuted items. But there is no ETA for this.

As to any ETA for other API releases, unfortunately I don’t have one right now either.

Thanks all!