Querying /data/wow/auctions/commodities started to return “429 - too many requests” in the last day or so. I’ve confirmed the request aligns with the recent changes to the API gateway, confirmed a valid token (it works on other endpoints), and confirmed the issue exists through different systems. The requests are also well within the specified API limits - and even after 24 hours of zero requests I’m getting the same 429 response.
Is this a bug? Was there a change that I’m not aware of that’s causing this issue? Anyone else experiencing the same?
Thanks!
Poent
1 Like
I’m also seeing this issue, starting around Nov 6 18:30:00 UTC. US/TW/KR regions seem to be affected, but EU continues to work fine.
Occasionally the affected regions do return a valid response, but most of the time I get 429s. I wait at least 5 minutes after a 429 before trying again. Every request includes the “If-Modified-Since” header to allow for a 304 Not Modified response.
1 Like
Same, something on Blizz’s end, hopefully they fix it soon.
1 Like
Any update on this? Still happening for me…
Happening to me as well, and I am definitely not issuing too many requests. Not sure what to do here, I hope this gets resolved/looked into. I am doing maybe 1 request an hour just keeping a local sheet up to date.
Happening for me as well. Though some are eventually getting through, but making it really hard to keep things up to date.
I’ve been seeing this same error for over a week now. I know I’m well under the limit, and this issue is not consistent. It seems to come and go, but for the last few days I’m seeing this error more than not. It has been a big pain trying to keep data updated.
+1 here too. I’ve also been getting a 429 error pretty consistently for the past couple of weeks. I haven’t had a single successful request for 3 days (i’ve tried at least a couple of times per day morning and evening with the same result)
I ended up building a retry mechanism into my code and this seems to have partially mitigated the issue. I currently have it set to try 10 times, once every 2 seconds, and I get a valid response within that window about 80% of the time.
Clearly still an issue, but this does let me work around it for the time being.
1 Like
^ This is the right call. A simple retry loop solves this and I even put a 100ms sleep timer in there on the calls that fail. Once the data comes back properly, just break out of the loop.
I am only needing one retry on the 429 errors that I get.
Retrying often until you get a non 429 does seem to be the current workaround. I will remind people that if you try too fast/too often, you may get a “real” 429 (ironic, i know) as they made API calls against the commodities API a x25 hit to encourage less api calls to it since it is a larger data dump. (yes, another ironic) =)
Looks like this is resolved as of Nov 12th patch day. I’ve received no failures today at all on numerous updates.
1 Like