Just turned on a couple of new endpoints:
- /v2/pvp/stats (example, github)
- /v2/pvp/games (example, github)
- /v2/character/:id/specializations (example, github)
/v2/pvp/stats
Requires “pvp” permission.
Dumps a bunch of aggregate pvp data — basically some of the stuff that’s displayed in the in-game UI. Some of it’s missing (e.g., fav map, etc). Consider this an initial pass — going to try to add more details here at some point.
/v2/pvp/games
Requires “pvp” permission.
Dumps the most recent pvp games played. This is a very very initial implementation; there honestly isn’t much useful here right now. There’s a lot more I want to do with this endpoint, but data needs to be plumbed through multiple services owned by multiple teams (who are all already busy) so it’s going to take some time.
As an important note, this endpoint only serves the 10 most recent games (that have occurred within the last 30 days, IIRC). I realize this is terrible and would like to make it a bit more reasonable, but it’s gonna take some time to get better data retention. Highly recommend any applications interested in this data use a server component which periodically polls+persists the endpoint data.
/v2/characters/:id/specializations
Requires “builds” permission.
The specializations are available in both /v2/characters (in the .specializations field) and in /v2/characters/:id/specializations. Data is provided for all of PvE, PvP and WvW builds (specializations can be cross-referenced against /v2/specializations, traits against /v2/traits which I just turned on).
Skills and PvP equipment will be coming at some point in the future but probably not this month (sorry!).
Questions/comments?
(edited by Lawton Campbell.8517)