My API Wishlist

My API Wishlist

in API Development

Posted by: Kuzzi.2198

Kuzzi.2198

I use the API to help with guild management/leaderboards, and there are a few things that I would like to see added at some point in the future. I know implementing new API paths is time consuming so I don’t really expect these anytime soon, but just want to spread awareness about what some casual users like myself might find useful.

Already part of API but disabled:

  • Achievements – I would love to be able to access some binary flags for every achievement per account. Progress could also be nice, but just a list of completed achievement ids would be sufficient for me personally.
  • Guilds – In particular I’m interested in the list of members. This may be a looong shot, but I would love to be able to access members’ API keys through the guild API. This would probably require some kind of permission from the members to enable API access for guild leaders. It would be nice if this permission step could be entirely contained in-game, but I’d understand if this is not feasible.
  • Leaderboards – It would be nice to access leaderboards information without web scraping, so I am definitely interested in this feature. I also hope it allows me to view the achievements leaderboard for my guild through my API key. (either that or the achievements for any guild leaderboard through a guild API key)

New API Paths:

  • Minis – I’m surprised I haven’t seen a suggestion for this. It would be a nifty feature similar to dye unlocks.
  • WvW – I would like to have API access to an account’s WvW rank. Per character WvW point distribution would also be nice, but not something I foresee needing personally.

My API Wishlist

in API Development

Posted by: Lawton Campbell

Lawton Campbell

Web Programmer

Achievements should start coming out next week-ish. Only have support for daily achievements until some more backend support lands, but we’ll probably have per-achievement account progress of some form around next month.

Guilds aren’t coming out until post-HoT. I don’t have enough test cases for the code and I suspect it’s bitrotted a bit.

Leaderboards... I’m not sure why we haven’t exposed this data programmatically. It should be fairly straightforward to do.

Minis and WvW Rank are pretty straightforward; I just need to find the time to implement the backend support for ’em. Probably post-HoT as well.

My API Wishlist

in API Development

Posted by: Nabrok.9023

Nabrok.9023

At the moment, my wish list is short …

Status – Most recently played character name (the current character if online now), possibly also with class/level though we could just query characters for that. The online status (online/away/offline). Current map if online. Amount of wvw supply carried. Short TTL (1 minute maybe).

“I’m not a PvE, WvW, or PvP player – I am a Guild Wars 2 player”
Tarnished Coast – Dissentient [DIS]
All classes

My API Wishlist

in API Development

Posted by: smiley.1438

smiley.1438

Most recently played character name

/v2/characters does actually return the character names ordered by last log in, the same way as in the character selection screen.

My API Wishlist

in API Development

Posted by: Nabrok.9023

Nabrok.9023

Most recently played character name

/v2/characters does actually return the character names ordered by last log in, the same way as in the character selection screen.

I thought this too at first, but it really doesn’t. I tried it to determine the character being played, and it does usually come back in that order, but not always. It’s not reliable.

I had to abandon that idea and just give users a drop down to select which character they are on (it does default to the list order though, so most of the time they don’t need to change anything).

Also, the 5 minute TTL is too long for this purpose.

“I’m not a PvE, WvW, or PvP player – I am a Guild Wars 2 player”
Tarnished Coast – Dissentient [DIS]
All classes

(edited by Nabrok.9023)

My API Wishlist

in API Development

Posted by: smiley.1438

smiley.1438

Hmm, weird, for me it’s always in that order. Maybe it’s a caching issue – i didn’t check immedeately after log-out. But yeah, it’d be perhaps usable with a 30s TTL like some of the AH APIs.