apoch on master
/v2/pvp/seasons: add .ranks. Merge pull request #535 from ar… (compare)
apoch on master
add missing name tag to /v2/rac… Merge pull request #609 from Th… (compare)
It's been a few month since this question has been asked. And now after the dust after the layoffs last month has (mostly?) settled, I'd like to ask it again.
In November Daniel Snider stated, that the API is still valued and worked on. He also offered to post updates to the forum to at least communicate that the API is still alive.
This hasn't happened. API development looks as dead as it has for a long time. :( Last commit to github (api-cdi) was 3 months ago.
And since the company has recently shrunk and had to reorder their priorities I'm afraid the API could have fallen off the end of the priority list.
So, again I question: what is the current state of the API? Is it still worked on? If so: only bugfixes or is it still worthwhile to suggest features?*
v2/nodeshas moved to
v2/home/nodesfor consistency. The old endpoint is still available.
v2/catshas moved to
v2/home/catsfor consistency. The old endpoint is still available.
v2/account/home/nodesnow contains all home instance nodes including the garden plots.
v2/account/home/catshas an updated schema that is consistent with other similar endpoints (try
v2/account/home/cats?v=latestto see the latest schema)
I have been making some recent changes to the way that API content is updated that allows more developers into the process. The goal is to make missing data (such as nodes) less frequent. As such, the nodes list is updated and has been moved to a new url (more details below).
With these changes comes new code and potentially new bugs especially with having the new code mimic the way the old API works, so if you find any bugs or inconsistencies, I'd love to hear about them.
Also, in order to make it easier to tell if daily/weekly progress has been reset (e.g. raid clears), I've added
last_modifiedto account and character endpoints. This removes the need to poll & store the account
agefield (which allows serverless apps to monitor progress properly).
Finally, I've introduced schema versions for updated endpoints. The motivation is to prevent breaking existing apps while still allowing the API to be modified without fear. Find more details on how to use them below.
Some users of the API have already come to me with bugs in the recently released code. Thank you so much!
While refactoring the code to handle parsing IDs from urls and query params, I introduced a bug that caused any hiccup to report a 400 HTTP status code (instead of, say, a 404), which broke a few apps. Oops!
Also, some of the mount skin code modifications I added inadvertently mutated cached data. This caused the icon link to only show during the first request after a cache invalidation (i.e. pressing F5 deleted the icon link from the mount skin for a few minutes).
These are small but I wanted to make sure to include these changes on the forum.
Silver is hard headed
itemIDand not effect any currently running stuff
The API for the Hungry Cat Scavenger Hunt appears to be bugged.
(see also: https://en-forum.guildwars2.com/discussion/72532/api-key-for-hungry-cat-scavenger-hunt)
I have the all but the Shattered Observatory Cat in my home instance and yet the API shows I'm missing the WvW ones and the Holokitty.
I am trying to compile a cost of items to craft, For example a Grow Lamp. Which uses Charged Quartz Crystals as an ingredient. But that item does not have a price.
I would like acquire the next ingredient down that has a Price attached to it. In this case that would be Quartz Crystals.
Where in the API is there a connection between Charged Quartz Crystals and the ingredient for them, Quartz Crystals?
I recently posted about some internal changes I made to how API content is managed. Some of the fruits of that labor are here in the form of some new endpoints.
First, I've added the world boss clears and map chests to the API so you (or your tools) can keep track of those daily rewards.
Also, I've added daily crafting progress to the API, which is helpful for keeping tabs on the daily cooldowns.
Finally, I added account luck to the API. The schema is weird due to the way its stored internally, but if it causes too much trouble, please let me know so I can modify it to something more sensible.