What other APIs are planned? I'm assuming that character/guild info will be the next one up. Is the Remote Auction House API going to move over from the wowarmory domain? What else can you whet our appetite with? =)
Thanks for establishing this forum. It's nice to have a place to give feedback. I don't know if this is the sort of thing you want to collect, but I could write up some of my experiences working with the RAH API.
We will definitely be rolling out character and guild feeds in the near future. Arena team feeds and general PVP feeds is something that we are interested in, but they might be a little later on. As for the auction house, we are looking at exposing historical data in the form of regular auction house dumps for each realm periodically. We need to work out some of the details, but we should have more information somewhat soon.
That would be great. |
|
When it's ready. (TM)
With that said, we are shooting for the weeks time-frame. Given the quantity of work in front of us, it doesn't make any sense trying to give exact dates. It should be noted that as we roll out new APIs, the old ones will be deprecated and will eventually go away. I would strongly advise building against the new ones. |
|
I'll try to break these down into FAQ style responses. Please let me know if I didn't answer one of the questions.
Q: Will item data be exposed through APIs? A: It is something that we would like to do, but there are other higher priority items that need to be hammered out first. Q: Will there be a transition period between a new release and retiring the old? A: Yes. Once the character and guild API features are complete and launched, we will announce a deprecation time-frame. Q: Would it be possible to setup the API to allow us to manage the guild from our web page? A: No. We have no plans or intent to create APIs that allow any data to be modified. Q: Are you planning on introducing XML or are you sticking with JSON? A: We will continue with using and suggesting JSON and JSONP. We are also looking at support Protocol Buffers as a line-wire protocol. XML isn't completely out of the picture, but is lower in the list of priorities. |
|
Until the auction house dumps and data services are deployed, it wouldn't be wise to give any details as they may change. I can say that providing sales history will probably not be developed and released.
JSON is because it allows client-side (browser) use of data provided through the new HTTP/REST API and can also be parsed/processed by most programming languages. It doesn't take much effort to see that there are a lot of major services using JSON as a primary protocol (Facebook, Google, etc). For developers interested in a more compact payload format, protocol buffers is an excellent and valid option. Any further debate about JSON vs XML or why one is better than the other should be had somewhere else. Lets continue with keeping this thread about future API plans. |
|
If you haven't read the authentication and registration overview sticky, please do so. It outlines the general plan for application level identification when consuming the API.
http://us.battle.net/wow/en/forum/topic/2369881359 What we are still solidifying is the plan for user-level identification within the application authentication system. It may end up being somewhat similar to how Facebook and Twitter allow applications to act on behalf of users. |
|
That should go out with the next api-wow deployment. |
|
So true. Given that there seems to be a lot of questions about AH data dumps, I'll do some research into what we can expose and the level of difficulty in doing so. Again, keep in mind that there are a lot of features and datasets that we would love to expose, but the biggest roadblock is simply time. We have to balance the cost of data mining sales data and exposing it vs getting other APIs out. |
|
Yes, these APIs will be available in all regions. |