Guild Wars 2

Let’s see, I’ve seen the following requests:

Items:
- Have an index to which recipes they are created from and/or used in.
- If available from vendor, price in copper/karma for item.

Recipes:
- Clearly state the Crafting Discipline. In particular, bags are hard to “guess” who makes them.
- Include the ‘set’ Mystic Forge recipes.
- Source of Recipe: Discoverable, or bought?

I’ll add in:
- For food items, spell out what the buffs they give, like weapons do.
- Similar for runes, and any other types that don’t specify them.

I am excited by what I see here, as it would make adding new recipes to my crafting script very easy in the future(instead of having to parse the wiki and create custom tools I can just run an update vs the api).

However there are a few changes(more information) that I would like to see.

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

• Fine as is.

https://api.guildwars2.com/v1/recipe_details.json?recipe_id=3479 example recipe

• Field indicating if the recipe is a refine, part or item – different xp gained for each. Unless type is supposed to fill that function.
• What craft(s) can use this recipe.
• Recipe source. Discovery, learned automatically, learned from recipe(breadcrumb to recipe IE “35 karma, Scholar Tholin – Krongar Pass(Timberline Falls 50-60)”)

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

• Fine as is

https://api.guildwars2.com/v1/item_details.json?item_id=13273 example item

• Link to the icon used by the item. Such as https://dfach8bufmqqv.cloudfront.net/gw2/img/content/e414cb68.png

xanthic.9478:

https://api.guildwars2.com/v1/item_details.json?item_id=13273 example item

• Link to the icon used by the item. Such as https://dfach8bufmqqv.cloudfront.net/gw2/img/content/e414cb68.png

For item details, it would be useful, if the item is sold by a vendor, to get the cost of buying it from a vendor. Besides the price of SELLING it to the vendor, which we can also get from the Trading Post API anyway. Include “Gold Cost”, or “Karma Cost”, “Laurel Cost”, or “Skill point Cost”. This would make such derivations possible, for example:

http://www.gw2spidy.com/recipe/3157

I think gw2spidy is using the data provided by gw2db but now that we have an official source, apps can consider switching to use this provided it has the data that they need.

A great bonus would be supporting Mystic Forge recipes. You can expose mystic forge recipes as belonging to its own unique crafting discipline if you like. Sorry if we are asking for too much.

xanthic.9478:

https://api.guildwars2.com/v1/item_details.json?item_id=13273 example item

What I miss in this API is a recipe_id for those items that are also created using a recipe.

If you take your recipe example. One of its ingredients is this:

https://api.guildwars2.com/v1/item_details.json?item_id=12812

Which is a crafting material, but one that requires another recipe to craft. It would be nice if there was a recipe_id in there as well, so you can eventually find the base materials of the final crafted item.

LadyRhonwyn.2501:

xanthic.9478:

https://api.guildwars2.com/v1/item_details.json?item_id=13273 example item

What I miss in this API is a recipe_id for those items that are also created using a recipe.

If you take your recipe example. One of its ingredients is this:

https://api.guildwars2.com/v1/item_details.json?item_id=12812

Which is a crafting material, but one that requires another recipe to craft. It would be nice if there was a recipe_id in there as well, so you can eventually find the base materials of the final crafted item.

That is created by recipe_id 3392.

https://api.guildwars2.com/v1/recipe_details.json?recipe_id=3392

You would have to match the output_item_id from the recipe list.

But that would mean you have to download all recipe_details of each recipe to search for the output_item_id of the item that you need to craft. Since you can only request the recipe_details of 1 recipe at a time it is going to be a performance hit for both server and client.

I suggest we either:

1. Allow output_item_id as a parameter to recipe_details.json.

or

2. Like LadyRhonwyn suggests, have a recipe_id field in the item record. That would also mean having a unique value for this field in items that are not craftable.

or

3. Have a way for recipe_details.json to return all recipes in 1 call. Leaving it to the client to search for the required output_item_id.

I would like to see an API that gives me all of the recipe details for all of the recipes in one JSON file. Currently, the procedure for getting all of the recipe details is…..

Step 1: Call “recipes” to get the list of recipe_id’s
Step 2: Loop through each recipe_id
Step 3: Call “recipe_details” to get the details of each recipe

This method takes a large amount of bandwidth as the current recipe_id list is 6870 items long….each requiring an individual call to get its details.

If a new “recipes_details” API was created or “recipe_details” would allow for the request of multiple recipes at once (say 250), then the number of requests would be dramatically reduced.

If the new “recipes_details” was created that contained ALL details for ALL recipes, then you would only need to call it once to get all of the information.

If the current “recipe_details” allowed for multiple requests (250), then you would need 6870 / 250 = 27.48 or 28 calls.

Either way, 1 or 28 calls, is FAR less than 6870 calls and would reduce bandwidth dramatically.

Edit: I haven’t tried using the “items” and “item_details” API’s yet, but I would hazard a guess that they work the same way.

For the items with type Consumable/Unlock, e.g. https://api.guildwars2.com/v1/item_details.json?item_id=9653

• recipe_id of the corresponding recipe which would be unlocked: 3182
• item_id of the crafted item, in this case: 12561

further for the recipes, example from above
https://api.guildwars2.com/v1/recipe_details.json?recipe_id=3182

• item_id of the Consumable which is required to unlock (if applies): 9653

and finally for craftable items
https://api.guildwars2.com/v1/item_details.json?item_id=12561

• recipe_id of the corresponding recipe: 3182

Items: add link to icon, like the current Trading Post API, but working without any GW2 account, and for every item.

I’ve forgot the chat code - i know we can calculate them on our own, but it would be more reliable to have them from the original source

smiley.1438:

I’ve forgot the chat code - i know we can calculate them on our own, but it would be more reliable to have them from the original source

I don’t know if this really is a good idea, it would add unnecessary information to the API. Maybe releasing a function in several languages to convert the ID into the chat code would be more useful!

By extension a link to an item icon is unnecessary as long as we get a resource from which we can fetch an icon corresponding to the item’s ID, which is already given. Having a way to get both icon and chat code would be nice but neither has to be in JSON format.

We can’t get every item icon from the ID, even with the Trading Post API. But we can generate every chat code with the ID.

The Talcmaster.7391:

That is correct. If it never has been sold on the TP, there is no image on there yet. As of yet there is no way to get icons for items not on the TP. I would put good money on it coming fairly soon though.

See the post: https://forum-en.gw2archive.eu/forum/community/api/Items-icons-and-in-game-code/first#post2086538

This isn’t a major problem, but I’ve found an item which is on the TP, but not in the API:
“Sealed Package of Snowballs” (item id 24)

Might this be because the item hasn’t dropped since the christmas event, so it’s not considered discovered (That’s a complete guess at how it’s been implemented)?

Charismatic Harm.9683:

I would like to see an API that gives me all of the recipe details for all of the recipes in one JSON file. Currently, the procedure for getting all of the recipe details is…..

Step 1: Call “recipes” to get the list of recipe_id’s
Step 2: Loop through each recipe_id
Step 3: Call “recipe_details” to get the details of each recipe

This method takes a large amount of bandwidth as the current recipe_id list is 6870 items long….each requiring an individual call to get its details.

I would like to second this suggestion and also include item_details for this suggestion also.

Considering that we would need to be registered developers with api key and set quota, this suggestion for being able to get all the item details in 1 call and recipe details in 1 call, becomes even more important.

I have posted on another suggestion thread before but since now we have an official suggestion thread for items, here goes:

For item details, it would be useful, if the item is sold by a vendor, to get the cost of buying it from a vendor. Besides the price of SELLING it to the vendor, which we can also get from the Trading Post API anyway. Include “Gold Cost”, or “Karma Cost”, “Laurel Cost”, or “Skill point Cost”. This would make such derivations possible, for example:
http://www.gw2spidy.com/recipe/3157
I think gw2spidy is using the data provided by gw2db but now that we have an official source, apps can consider switching to use this provided it has the data that they need.

Another great feature would be supporting Mystic Forge recipes. You can expose mystic forge recipes as belonging to its own unique crafting discipline if you like. Sorry if we are asking for too much.

The problem with including vendor costs is that different vendors can sell the same item at different prices. I’m not talking just coin versus karma, but I know at one time during beta there was an item that different vendors sold for different amounts of coin.

A better way to present that data would be via a vendor_details.json API, that would key off of actor_id or something and list all the items the vendor sells, along with the prices.

Dr Ishmael.9685:

I know at one time during beta there was an item that different vendors sold for different amounts of coin.

Golem-In-A-Box is such an item – sold in Metrica Province at 2 different vendors for different price …and it’s missing in the Items-API :o

Dr Ishmael.9685:

The problem with including vendor costs is that different vendors can sell the same item at different prices. I’m not talking just coin versus karma, but I know at one time during beta there was an item that different vendors sold for different amounts of coin.

A better way to present that data would be via a vendor_details.json API, that would key off of actor_id or something and list all the items the vendor sells, along with the prices.

Alternatively we can have a vendor array on each item record with each element in the array containing the vendor id and the gold/karma/laurel/skill point cost for the item.

This would be similar to an item record with something like this:

{...,"SoldBy":[{"NPCExternalID":700000,"KarmaCost":49},{"NPCExternalID":700001,"KarmaCost":77}]}

{...,"SoldBy":[{"NPCExternalID":700000,"GoldCost":8}]}

The advantage of this approach is that I won’t need to load the vendor.json, when I am not interested in vendor information, in order to generate a tree view like the one shown in http://www.gw2spidy.com/recipe/3157

Receiving the image / icon for an item is totally necessary

Would be nice if Arenanet would release an official asset kit containing all those icons for use with the API or some sort of tool to pull the data from the gw2.dat. People have already started to pull the data in some ways from the AH which i believe wasn’t intended. Official sources would also help the wikis

For these API to be useful for me I would need the additional information in bold. This is what I envision needing to automate my crafting guides recipes.

get all valid/known recipes via recipes.json

via recipe_details.json get each(new) recipes item_id created, skill level, craft required(eg cooking), recipe source(eg discovery, learned automatically, learned from recipe – with source), craft type from refine, part and item(they each give different xp)

Sample fields:

“craft”:“cooking”
Possibly values: cooking, jewelcrafting, artificing, leatherworking, armorcrafting, tailoring, weaponcrafting, huntsman

“source”:“discovery”
Possible values: discovery, learned, recipe name eg “Recipe: Ooze Custard”

“craft_type”:“item”
Possible values: part, refine, item. This may be redundant if “type” already implies that information but it would need possible results documented somewhere.

smiley.1438:

Would be nice if Arenanet would release an official asset kit containing all those icons for use with the API or some sort of tool to pull the data from the gw2.dat. People have already started to pull the data in some ways from the AH which i believe wasn’t intended. Official sources would also help the wikis

What Zicore’s TP notifier does is to cache those images in a folder whenever his app tries to fetch an item image. This way, the app actually runs faster the more the user uses it at the cost of some disk space (which is cheap nowadays anyway). My image cache folder has 4738 PNG files right now.

When caching many small files, you can save a little bit of disk space by creating one large file. Files are allocated a specific amount of disk space, which for mostly everyone is going to be in intervals of 4KB. If you have a 1 byte file for example, it’s going to use up 4 KB.

For ~4700 3-8KB files, you could save anywhere from 5-10 MB of space, assuming 64×64 icons.

In my case, I’m caching 24,853 raw responses that are just a few 100 bytes in length each. In total, it’s only 11 MB, but since they’re all separate files, it’s actually 97 MB. In database form, it’s 4 MB.

Healix.5819:

When caching many small files, you can save a little bit of disk space by creating one large file. Files are allocated a specific amount of disk space, which for mostly everyone is going to be in intervals of 4KB. If you have a 1 byte file for example, it’s going to use up 4 KB.

For ~4700 3-8KB files, you could save anywhere from 5-10 MB of space, assuming 64×64 icons.

In my case, I’m caching 24,853 raw responses that are just a few 100 bytes in length each. In total, it’s only 11 MB, but since they’re all separate files, it’s actually 97 MB. In database form, it’s 4 MB.

That is cool, but in the case of my app that would be a little in the realm of adding more complexity for little gain since hard disk space is very cheap nowadays anyway. Squeezing better performance is where I have been investing time into.

Tonights changes added everything I was hoping for. Crafting guide should get automated recipe lists tomorrow and then I won’t have to touch it again (except to add any new cooking recipe locations)

I am still holding out hope that they would provide NPC vendor “SoldBy” info for items soon.

I would really like to be able to come up with something like this:

http://www.gw2spidy.com/recipe/3157

…with the data provided.

I already have the code developed for this against the gw2db data but their data is missing some NPC vendor prices for some items so I had to supplement it.

As a bonus, if they can also provide Mystic Forge recipes that would be even better. I tried mixing the MF recipes into the crafting recipes and my code came up with new cheaper ways to make some of the named exotics, which is very cool.

recipe_details: Suggestion / Missing

For the recipe_details I´m missing: The category of recipe: Insigmia, refinement, Upgrade component, Ring, and so on (such as seen here: http://wiki.guildwars2.com/wiki/File:Jeweler_Crafting_Pane.png). Even mystic forge can be applied there.

That’s the “type” element in recipe_details.json. Mystic Forge recipes are not included in the API at this time.

I have one more suggestion. Right now there is no way for me to find out the Recipe item itself that is required to unlock a particular recipe.

For example, take the recipe for Candy Corn Custard:

https://api.guildwars2.com/v1/recipe_details.json?recipe_id=6472

…and the Recipe item to unlock the above recipe:

https://api.guildwars2.com/v1/item_details.json?item_id=36103

There is currently no way for me to link one to the other, short of doing fancy regex matches. It would be great if the recipe item can specify the recipe id that it actually unlocks OR the recipe itself, with the “LearnedFromItem” flag, can specify the recipe item that is used to unlock it.

Thanks.

DarkSpirit.7046:

There is currently no way for me to link one to the other, short of doing fancy regex matches.

Even that wouldn’t work all the time. Example: Recipe: Atzintli’s Spear teaches the recipe for Quetzal Harpoon. Some others aren’t quite as bad (Recipe: Eggs Beetletun teaches Beetletun Omelette), but there are a lot like this.

I second this request.

Thats pretty much what i’ve already suggested in post #3, isn’t it?

smiley.1438:

Thats pretty much what i’ve already suggested in post #3, isn’t it?

That just goes to show how much the community needs this.

EDIT: If we have this, and the “SoldBy” property for items, then apps would be able to start providing useful information on how + where to unlock recipes.

If not the “SoldBy” property, we can use the Vendor API, if that is provided instead.
https://forum-en.gw2archive.eu/forum/community/api/API-Suggestion-Vendor-API/first#post2175422

Unlocks now list the color_id/recipe_id they unlock. Whoo!

That was a fast turnaround! Woot!

The new unlock_type enum:

    public enum GW2APIUnlockTypeEnum
    {
        CraftingRecipe,
        Dye,
        BagSlot,
        BankTab
    }

And now it’s obvious that there are a lot of recipe sheets missing. Both of the ones I linked above (Eggs Beetletun, Atzintli’s Spear) are missing, as is Eda’s Apple Pie Recipe. Some of the recipes are listed (recipe_ids are 2968 for Beetletun Omelette and 2903 for Eda’s Apple Pie) and they have the LearnedFromItem flag, but the items API discovery mechanism still has some big flaws.

Yes but items are getting “discovered” with each day so at least there is hope. The only thing that I need now from the items API is either a “SoldBy” property (with its vendor acquisition cost) for vendors OR a vendor API that lists the items each vendor sells and its cost.

With that I would be able to show where and how to unlock recipes and also be able to generate a tree view for minimum crafting cost for craftable items, like in gw2spidy.

I believe gw2spidy had to supplement their data that they got from gw2db since the SoldBy property in gw2db items API is not very complete.

I made a spreadsheet of all the LearnedFromItem recipe details and added the item_id of the consumable that unlocks it, as well as the name of the output_item_id.

https://docs.google.com/file/d/0B5NobLNMdY89TnpzVC00Zm1vemc/edit?usp=sharing

Looks like the majority of the recipes with an unlisted Unlock are where the recipe sheet is purchased for karma, although there are still some Bulk and Feast recipes with an unlisted Unlock even though you get those recipe sheets from the Mystic Forge.

As I missed this thread on the first glance I beg for pardon and simply repost my suggestion here:

It would be kind of nice if you provide more information for bags, especially their type.
Currently a definition looks e.g like this one:

{u’restrictions’: [], u’name’: u’12 Slot Equipment Box’, u’level’: u’0’, u’rarity’: u’Fine’, u’bag’: {u’no_sell_or_sort’: u’0’, u’size’: u’12’}

As you can see there is no information about that equipment go firstly in this bag .
For "Invisible" Bags such information is already provided (u’no_sell_or_sort’: u’0’) why not for other bag types?

With best regards, Paranaix

I’d like to see a bulk get(like the TP api has) so I am not doing 10,000 individual api calls when rebuilding recipe sheets. EG https://github.com/xanthics/gw2craft/blob/master/create_recipes.py

I’m bored about items pictures/icons…. I mean, if I want to get the pictures for each object I have to connect to the TradingPost API and this is pretty painfull to do.

I use certificates, https connection and simulate from my application the connection through a browser. But I would be please to simply get them from the items hash, as a link to the picture.

I just want to do it one time, but I can understand than beginners will request it all the time and slow down the assets server. Please, find a solution about it !
I’m thinking about blocking ip if doing two times the same requestor more.

As far as icons go, I’d be perfectly happy with a simple icon_file_id. I’ve already got GW2DatBrowser to extract the files, so I don’t need the file itself presented through the API or on a cloud server or anything like that.

Glad to see there is already a lot of interest for icons to be added to item_details.json – I was just going to make a post suggesting it.

Since ArenaNet are encouraging people to hotlink to their map tiles rather than mirror them, I have hope that they will add icon support to the current items API. As many people have stated, at the minute it’s very much needed.

While I personally have no issues using GW2DatBrowser to get the icons, I don’t think it would be good practice to have icon IDs in the API without also providing those icons directly.

The best implementation I can think of would be to have something like “icon_id” in item_details.json, and create item_icons.json with URLs to ArenaNet-hosted PNG files that correspond with the IDs.

Hi

discovering new recipes becomes a technical chalenge.

How is discovering we recipes any sort of challenge?

Maintain a list of known recipe IDs. If the list changes over time, you know what was added/removed.

You can spot changed recipes in a similar way… You just need a few thousand API calls.
//Yamagawa

I just found out there’s a new field in the item details json… (two in fact..)
“icon_file_id”
“icon_file_signature”

Now a way to figure out how to use them…

icon_file_id is the id of the file in the gw2.dat file. You would have to extra the dat file for that number to be of any use to you.

I assume they’ll release the icons in the same way they did map tiles.

Apparently I was ahead of the official update post

Now I’ll need to update my entire list of 26429 items to get the icon id and signature…

See https://forum-en.gw2archive.eu/forum/community/api/Render-service-for-item-icons-404 for ANet Icon Render Service URLs.

I’d like to see some kind of filtering options for items.json. For example, being able to only show item IDs for items that are exotic by calling items.json?rarity=6 (or something to that effect). Ideally we’d be able to add as many parameters as we want – for example, Exotic gloves that are heavy armor and usable by Sylvari: items.json?rarity=6&weight=3&slot=4&usable_by=3. Just made up numbers, but you get the idea.

I’d also like to see the ability to retrieve more than one item’s data at once using item_details.json?item_id=[3012,7610,3478,1029] or something similar.

Maybe I just miss it, but I still can’t find the Mystic Forge recipes in the API.
If I just don’t see them, can anyone tell me where to look for them? If they are still not inside I hereby support the request for Mystic Forge recipes. That would be really good.