Auction House API is live!

Web & Mobile Team
We're very pleased to announce that the first version of the Auction House API is now live - we have been hard at work on this for the last few weeks, and are looking forward to seeing what new and exciting applications spawn out of it!

As of right now, US and Europe are live and populating, and Korea will be following in a couple of days.

Please refer to the documentation at http://blizzard.github.com/api-wow-docs/#id3683980 for further information, and don't hesitate to post any thoughts on this thread.

Thank you for your patience!
Reply Quote
12 Human Mage
50
{"auc":1347942360,"item":14344,"owner":"Sanctuary","bid":2041200,"buyout":2268000,"quantity":3},


It seems like "Time Left" is still not being included in the AH dump. I was under the impression that this was going to be modified on release, as per this thread: http://us.battle.net/wow/en/forum/topic/2878699690

Is it possible to know if this is a bug or not?

Thanks! :)
Reply Quote
Web & Mobile Team
{"auc":1347942360,"item":14344,"owner":"Sanctuary","bid":2041200,"buyout":2268000,"quantity":3},


It seems like "Time Left" is still not being included in the AH dump. I was under the impression that this was going to be modified on release, as per this thread: http://us.battle.net/wow/en/forum/topic/2878699690

Is it possible to know if this is a bug or not?

Thanks! :)


It is indeed a bug and is planned for the next API deployment.
Reply Quote
12 Human Mage
50
08/01/2011 06:10 PMPosted by Straton
It is indeed a bug and is planned for the next API deployment.


Cool, thanks!

Is it possible to get an ETA? Nothing official, of course. I'd just like to know if we're talking about hours, days or weeks. Nothing more than that.

Thanks a lot! :D
Reply Quote
Web & Mobile Team
Looking to get the fix for this rolled out tomorrow - sneak preview of the format (docs to be updated when we push it):
timeLeft: "SHORT|MEDIUM|LONG|VERY_LONG"
Edited by Osundir on 8/1/2011 6:35 PM PDT
Reply Quote
12 Human Mage
50
Looking to get the fix for this rolled out tomorrow - sneak preview of the format (docs to be updated when we push it):
timeLeft: "SHORT|MEDIUM|LONG|VERY_LONG"


Awesome! Thank you so much.
Reply Quote
12 Human Mage
50
I'm not sure how important this is but the content-type being returned for the actual AH dump is text/plain instead of application/json. Took my a little while to figure out why my test was failing ;D.

https://us.battle.net/api/wow/auction/data/aegwynn
["Content-Type"]=>
string(30) "application/json;charset=utf-8"


http://us.battle.net/auction-data/aegwynn/auctions.json
["Content-Type"]=>
string(25) "text/plain; charset=UTF-8"

Reply Quote
62 Human Death Knight
550
How often is the auction-data updated?
Reply Quote
1 Troll Rogue
0
I want to say thanks to the Blizzard Web Dev team for their heroic efforts at getting the AH API live in the final hours before the wowarmory.com shutdown! My visitors at The Undermine Journal are all grateful. Or, at least, they should be. :)

The docs from a few weeks ago were followed well enough that my prepared scripts fired right up once the actual APIs were available. I had to make a few changes just on my end for efficiency and such once I saw it running, but so far so good.

Couple things different from what I expected:
1) Auction data isn't gzipped at all. The docs made me expect a gzipped file with json in it, but all I get back is the raw text. Even if I accept gzip with the HTTP headers, it doesn't come back compressed, even though the API to get the filename does return gzipped json. I figure this difference is from pushing it out ASAP, and that gzip-compressed data will follow shortly. I hope so. :)
2) Auction data filename is static, and not timestamped. No big deal, just curious.

Thanks again, folks.
Reply Quote
Web & Mobile Team
Couple of replies (Thanks for the great feedback so far!):

@Vynz - This is most likely a minor web server tweak that we can get hooked up tomorrow.
@Ujournal - Point 1 - Will also look at getting the gzip compression hooked up tomorrow - file extension won't change, but it should get streamed as gzip :). Point 2 - We've been back and forth on this and may change it once we observe the live behavior - thats why its so important to read from the API call to get the filename, so we can change it at-will.
Reply Quote
85 Troll Druid
4180

I'm have a bit of trouble accessing the AH API. For my realm, Black Dragonflight, I access:

http://us.battle.net/api/wow/auction/data/black-dragonflight

and get

{
"files":[
{
"url":"http://us.battle.net/auction-data/black-dragonflight/auctions.json",
"lastModified":1312287828000
}
]
}


However, when I access the URL from the return data, I get a 404. I've tried adjusting the filename to include the last modified timestamp as nebulously indicated in the documentation, but nada.

So what is the proper URL for accessing the current AH data file for a given realm?
Reply Quote
12 Human Mage
50
I'm having trouble getting any data this morning. The first call responds fine but the url returned gives me a 404.


You are getting a 404 because the realm is currently under maintenance.

Neriak: This answer goes for you too :).
Edited by Vynz on 8/2/2011 6:47 AM PDT
Reply Quote
85 Troll Druid
4180

friggin maintenance strikes again

thanks
Reply Quote
90 Human Mage
19100
This is great timing as I'm in the middle of developing some web-based tools for WoW. Guess it's time to add in some AH tools. :)
Reply Quote
85 Orc Warlock
6440
You are getting a 404 because the realm is currently under maintenance.

Neriak: This answer goes for you too :).


Why is this though? If this is cached snapshot data why isn't it just waiting until the realms are back up to update? Seems like a bug to me that it would announce a new update (via lastModified) but not actually populate a file.
Reply Quote
1 Troll Rogue
0
I don't think it's a realm maintenance issue.

Last night, I would get results like this:
1) Pull https://us.battle.net/api/wow/auction/data/onyxia using my authorization headers
2) Notice the lastmodified value changed. Decide to get the actual auction data.
3) Pull https://us.battle.net/auction-data/onyxia/auctions.json (the URL returned in step 2, but changed to https) using my authorization headers
4) Retrieve uncompressed text/plain file that was in json format with all the auction data for Onyxia

This morning, it looks like this:
1) Pull https://us.battle.net/api/wow/auction/data/onyxia using my authorization headers
2) Notice the lastmodified value changed. Decide to get the actual auction data.
3) Pull https://us.battle.net/auction-data/onyxia/auctions.json (the URL returned in step 2, but changed to https) using my authorization headers
4) Receive a 302 redirect to http://us.battle.net/en/auction-data/onyxia/auctions.json
5) Pull http://us.battle.net/en/auction-data/onyxia/auctions.json with no authorization headers
6) Receive 404 not found

This redirect path started around two and a half hours ago, like 8am EDT/5am PDT. I don't send the auth headers in step 5 because I didn't anticipate that I'd have to handle redirects, but it's probably a good thing anyway since the redirect goes to http. I imagine something unrelated to the API is responding to the URL in step 3 and redirecting it like most other pages.

Hope this gets fixed soon. :)
Edited by Ujournal on 8/2/2011 7:27 AM PDT
Reply Quote
85 Human Rogue
10755
Also hoping it's back up soon... I was going to do some playing around with a few ideas :)
Reply Quote
Web & Mobile Team
I can confirm that some of the json files are returning 404s when they shouldn't be. We'll look into it this morning.
Reply Quote

Please report any Code of Conduct violations, including:

Threats of violence. We take these seriously and will alert the proper authorities.

Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.

Harassing or discriminatory language. This will not be tolerated.

Forums Code of Conduct

Report Post # written by

Reason
Explain (256 characters max)
Submit Cancel

Reported!

[Close]