Skip to Content
7-21-2011 @ 8:11PM
Except I read http://blue.mmo-champion.com/topic/183869/java-library-for-the-community-platform-apiwhere Straton says "Blizzard advises against using 3rd party data APIs and services. Use at your own risk."As a programmer, this is plain silly. It is advice from another millennium or written by a suit/lawyer.I have great hopes for the API in the future but I am afraid it will take Blizzard a long time to internalize an API and give the community what they want. And of course why wasn't the AH in the first round of API???
7-21-2011 @ 9:58PM
"I'm specifically talking about proxy APIs or services that republish data provided by our own API."- Same blue, same threadNow then, Blizzard has a premium service for accessing the AH via the remote. They've already had issues with the Undermine Journal spamming their services as it is. The AH is huge and contains far more info than a simple character sheet or guild roster will have. The max on a guild is 1000 people, the smallest AH I've ever seen still had 15 times that.In short, in the face of far more potential for abuse and already having a paid service for it, why are they going to open AH API's and specifically, why would something that complicated be first?
7-22-2011 @ 7:33AM
@icyproFor a time I was the lead dev for EveMon (at the time when CCP launched their character sheet APIs If you were around then, you may remember me as "Brad Stone") I took a week off work to recode EveMon to work with the new api as we wanted to be ready for launch day.Anyway, to my point: It proved SO popular that CCP had to limit the character queries to once an hour. If you called it any more than that, you just got back a cached version, and CCP strongly encouraged me and other API consumers to ensure that our apps only queried the API once an hour for specific character's data. Technology has moved on since then but the AH data is MASSIVLY bigger than a list of character stats and skills. I could well see the same thing happening here- Blizzard will throttle back the frequency of requests that can be made.
First time? A confirmation email will be sent to you after submitting.
Members enter your username and password.
Enter your AOL or AIM screenname and password.
Please keep your comments relevant to this blog entry. Email addresses are never displayed, but they are required to confirm your comments.
When you enter your name and email address, you'll be sent a link to confirm your comment, and a password. To leave another comment, just use that password.
To create a live link, simply type the URL (including http://) or email address and we will make it a live link for you. You can put up to 3 URLs in your comments. Line breaks and paragraphs are automatically converted — no need to use <p> or <br /> tags.