Kantharr.2308:

Is there a way to get the karma cost of an item through the API? I tried looking for it but all I found is the unit price and the trading post prices.

StevenL.3761:

Same question for other currencies (dungeon tokens, bandit crests, …).

Lawton Campbell.8517:

Not currently, no.

I’ve looked into implementing this and it’s probably not going to happen. The same item can be sold by multiple vendors for different prices (or different currencies) — consider the Dry Top geode vendors or the Fortune Scrap vendors — and I don’t think there’s a feasible way to determine whether a vendor is still (or was ever?) accessible.

Dr Ishmael.9685:

What if you approached it from the other direction? Presenting the same data with the vendor as the focus would make more sense. The data could be organized to reflect the vendor window in the game – a list of the tabs within the window, then each of those is a list of the items (and their costs) offered on that tab.

As for the accessibility of vendors, would it be possible to implement a “discovery” system similar to what’s already in place for items/recipes/skins?

StevenL.3761:

^ This would make a great addition to the the floors API. Maybe consider it for /v2/floors?

AysonCurrax.3254:

I actually intend to implement something of the sort into my webapplication, which i am sorta working on on and off (mostly off than on lately). It will require a ton of manual, explorative work on my part, but considering where i plan to take it, it would be well worth it. additionally, i would also make an api of my own to allow others to use that data, if they wish. It is however still in the stars when i ll find the time to work on that though. what do you guys think about that?

Lawton Campbell.8517:

As for the accessibility of vendors, would it be possible to implement a “discovery” system similar to what’s already in place for items/recipes/skins?

Not sure whether that’s feasible or not; will have to look into it. Having a vendor endpoint would definitely be the best approach though — at that point, we’d be able to reference the vendor IDs from both /v2/items and /v2/floors.

AysonCurrax.3254:

As for the accessibility of vendors, would it be possible to implement a “discovery” system similar to what’s already in place for items/recipes/skins?

Not sure whether that’s feasible or not; will have to look into it. Having a vendor endpoint would definitely be the best approach though — at that point, we’d be able to reference the vendor IDs from both /v2/items and /v2/floors.

IF you are going to do that, please do warn us ahead of time. As i mentioned in the post right above yours, i was intending to go exactly what that api would provide through hours of manual exploration and discovery before providing it as a 3rd party api of my own. I would appreciate it not to waste so many hours i could have spent another way, only to be slapped in the face by a shiny new api a day after i am done. I fondly remember that day where i finally got my code running properly for the v1/item_details api that took about 6-9 hours (because i was so kind not to violate the api with 1 billion request simultaniously and instead only used 4 threads for that) to draw in all items that existed at the time in all 4 available language, and literally the next day you smacked me with the much faster v2/items apis. Anet pls.

A rough estimate, if possible, would be very welcome.

Sariel V.7024:

If you could manage a vendor API I would love you forever XD I’ve already scoured the merchants on the wiki, but they remain incomplete, and certain items in the API that SHOULD be connected to vendors are unknown or missing in-game.

Kantharr.2308:

I’m hoping that the layout for the vendor values would happen to look something like this in the items API:

id
name
icon
description
type
rarity
level
vendor(array of objects)
——vendor_prices (array of objects)
————vendor_value (number)
————vendor_type (string)
——vendor_name(string)
default_skin
flags
game_types
restrictions
details

The reason why I put array of objects for vendor is because there could be an item that has 2 different prices (I could be wrong, if I am then it can just be a single object).

The vendor_prices is an array because I know that there are items that require more than one currency type to purchase (like WvW for example that requires gold and badges of honor).

I do hope that something like this gets implemented. That would be awesome and would make our lives easier