Original Url: http://forum-en.guildwars2.com/forum/community/api/API-Suggestion-API-for-the-wardrobe

nightzirch.3126:

Hello

I recently started the development of gw2wardrobe which I intend to make the go-to source for players who seek to fill their wardrobe 100% or players who wonder how to acquire certain items.

I am currently using both the GW2 official API and gw2spidy’s API in order to get easier access to item data. However, calling gw2spidy’s API for all armor items, I get 7418 results back. Lots of these items share the same look, making the majority of the items redundant.

I started this thread with questions in mind, but turned it around to include suggestions instead.

I would love to see an API for the wardrobe. Kind of like items, but with skins instead.

  1. https://api.guildwars2.com/v1/wardrobe.json would return a JSON object with all the different looks there are in the game.
  2. https://api.guildwars2.com/v1/wardrobeDetails.json?item_id=1234 would return details about a specific skin. It could also include an array of item IDs for the items that have this particular skin.
  3. I would also love to see some order in the returned object, so we could with a few lines of code automatically sort the items in the order they appear in the wardrobe. This could either be the order they are returned in the JSON object from wardrobe.json, or as an integer property in wardrobeDetails.json.

I know this would take hours and hours of work off my shoulders, not having to create a database manually.

I would love to hear your thoughts on this matter. And I feel I should thank all the devs. for their work. We all appreciate the great job you are doing for the developer community!

Dr Ishmael.9685:

I already asked basically the same question: https://forum-en.guildwars2.com/forum/community/api/The-API-the-Wiki-and-the-Wardrobe but instead of proposing new endpoints, I suggested that they just add skin_id to item_details.json (the data is probably already structured this way anyway, which should make it relatively easy to implement).

I don’t know what else you would expect to get from a wardrobe.json endpoint… I doubt they would be able or willing to host model/texture files the same way they do item icons.

nightzirch.3126:

I quickly browsed through the API category to see if there were any threads like this. I must’ve missed yours.

As you say, we propose two different approaches to basically the same end-result. I agree that your suggestion seems alot easier to implement.

Let us cross our fingers and hope for a response from the devs.

Sariel V.7024:

You have probably already seen, but items sport a skin_id.

nightzirch, GMTA. I am also working on something similar, though I don’t expect to do much beyond a single release.