More detailled API Documentation

More detailled API Documentation

in API Development

Posted by: Aartsie.9840

Aartsie.9840

When we saw the forum post of Cliff Spradlin on the API documentation on the API Development forum we where thinking, how can we make this documentation more clear.. So we decided to create this API documentation website. We hope you will find this API guide useful. http://www.guildwars2api.com

More detailled API Documentation

in API Development

Posted by: The Talcmaster.7391

The Talcmaster.7391

Very cool. Thorough documentation is generally a good thing. Feel free to grab my unofficial Trading Post API guide and stick it on there if you want.

Fort Aspenwood – [fury], [SAO], [NICE]
Fun on someone else’s schedule is not fun

More detailled API Documentation

in API Development

Posted by: Dr Ishmael.9685

Dr Ishmael.9685

You need a margin-left of about 100px on your .content_box, it’s hiding behind the #leftside-navigation for me.

More detailled API Documentation

in API Development

Posted by: Think.8042

Think.8042

It’s because the content_box is centered (wow, with <center> instead of margin:auto), and the nav is position:fixed. As soon as the browser size is smaller than the fixed width content + navbar, it will start to clip.

Regarding content: currently, I don’t see anything there but copy-pasted tables from the sticky threads. I’d love to see many more details to be able to use this at all. What immediately comes to mind is the fields for item data (which can already be found because of the work of at least two people on the wiki), detailed example queries, etc.

(edited by Think.8042)

More detailled API Documentation

in API Development

Posted by: Varonth.5830

Varonth.5830

You definitely put alot of work into this, but isn’t the wiki a better place for hosting these informations?
http://wiki.guildwars2.com/wiki/API

There are also subpages with additional informations like this one:
http://wiki.guildwars2.com/wiki/API/item_details

More detailled API Documentation

in API Development

Posted by: Aartsie.9840

Aartsie.9840

@The Talcmaster: Thank you i will take a look for that.

@varonth: I think that was a good location for it but i saw a post on the forum about this and though they will wait with it.

I know there are some css problems I will fix this in a few days.
And i will add some more content like objects locations on the maps.

More detailled API Documentation

in API Development

Posted by: DarkSpirit.7046

DarkSpirit.7046

I don’t see any documentation on the Recipe type property value enumeration on the website or the wiki. Here are the valid values that I have found for Recipe type:

Refinement,
Component,
Bulk,
Bag,
Dye,
Potion,
UpgradeComponent,
Inscription,
Insignia,
Consumable,
Dessert,
IngredientCooking,
Seasoning,
Feast,
Snack,
Soup,
Meal,
Coat,
Leggings,
Gloves,
Helm,
Boots,
Shoulders,
Sword,
Hammer,
LongBow,
ShortBow,
Axe,
Dagger,
Greatsword,
Mace,
Pistol,
Rifle,
Scepter,
Staff,
Focus,
Torch,
Warhorn,
Shield,
Harpoon,
Speargun,
Trident,
Amulet,
Ring,
Earring

Typical call: https://api.guildwars2.com/v1/recipe_details.json?recipe_id=3392
Output:
{"recipe_id":“3392”,“type”:“Component”,“output_item_id”:“12812”,“output_item_count”:“1”,“min_rating”:“0”,“time_to_craft_ms”:“2000”,“ingredients”:[{"item_id":“19680”,“count”:"2"}]}

(edited by DarkSpirit.7046)

More detailled API Documentation

in API Development

Posted by: The Pointless.3869

The Pointless.3869

snip!

I did get around to adding that to my page, along with the rest of what I could find from the data I’d grabbed: http://wiki.guildwars2.com/wiki/User:ThePointless/APIMap#Recipes

Not that I got much of a response on it on the other thread after the fact, like.

More detailled API Documentation

in API Development

Posted by: DarkSpirit.7046

DarkSpirit.7046

snip!

I did get around to adding that to my page, along with the rest of what I could find from the data I’d grabbed: http://wiki.guildwars2.com/wiki/User:ThePointless/APIMap#Recipes

Not that I got much of a response on it on the other thread after the fact, like.

For what it is worth, I looked into yours and compared it against his.

1. His has a mistake for the “tool” type. It should be “charges” instead of “uses”, so yours is right. Can you fix it for him or tell him?

2. Both of you have the same mistake of listing “Toy” under the weapon type. There is no “Toy”, only “TwoHandedToy”.

3. Minor mistake on your recipe type. Amulet should be listed under Jeweler instead of Artificer.

Nicely done.

More detailled API Documentation

in API Development

Posted by: The Pointless.3869

The Pointless.3869

For what it is worth, I looked into yours and compared it against his.

1. His has a mistake for the “tool” type. It should be “charges” instead of “uses”, so yours is right. Can you fix it for him or tell him?

2. Both of you have the same mistake of listing “Toy” under the weapon type. There is no “Toy”, only “TwoHandedToy”.

3. Minor mistake on your recipe type. Amulet should be listed under Jeweler instead of Artificer.

Nicely done.

1. I’ll try and pass that on to him. [EDIT: Correction made]

2. There are a few entries in the data I’ve got with the weapon type “Toy”, actually. An example of this is the Frying Pan. Not even sure whether it even matters ingame, though, because I’ve not been able to buy town clothing sets.

3. Cheers, I’ll fix that in a sec as well. [EDIT: Done]

(edited by The Pointless.3869)

More detailled API Documentation

in API Development

Posted by: DarkSpirit.7046

DarkSpirit.7046

2. There are a few entries in the data I’ve got with the weapon type “Toy”, actually. An example of this is the Frying Pan. Not even sure whether it even matters ingame, though, because I’ve not been able to buy town clothing sets.

You are right, I missed that.

More detailled API Documentation

in API Development

Posted by: DarkSpirit.7046

DarkSpirit.7046

@The Pointless: The recipe and item schema have changed.

More detailled API Documentation

in API Development

Posted by: The Pointless.3869

The Pointless.3869

I noticed, but I been a little overworked since before then.
I will have a gander at the changes this week, though.