It seems to effect every query using the fantasy sports API, but other APIs are okay. For example, this query fails with that INKApi Error. That is one of the canned example queries, so it certainly should work.
The only thing I can think is that it could be some kind of authentication issue, but I thought the console handled those automatically as long as I am logged in (I am).
Am I doing something wrong? How can I work around this problem? Thanks in advance for your help!
Glad I checked here. I was attempting to build out a quick prototype to see if it was worth the time to build something around this API and I've been getting failures around everything. Even the YQL examples are breaking with 500s. Quite frustrating, especially when you don't know if as the developer you're the one messing up or not.
It's interesting. Some API calls work, others don't. For example, I can pull back a list of NFL players via an API call (outside of YQL Console in my case, but same YAHOO DB), but I can no longer pull back details about my specific league as I could previously (just last month).
I'm a YAHOO fan and just wish they would devote more resources to this and at least put up a disclaimer on their Developer Network if maintenance or some issue resolution is in progress.
The API itself is stable, I think. I have been developing a new app using it over the last couple of weeks and it has been up the whole time. I basically had to write my own version of the console so that I can see what kind of JSON they API returns for different requests (and, of course, sign them appropriately with my API key).
Glad to see this is heavily supported by Yahoo... An open issue since at least May and a "We're looking into it" is the only thing that has been posted by what appears to be a yahoo someone or other. If it is important to you, I would fallow humdinger's lead and create your own console.
I was going to start developing with this API, but I don't feel like taking the time to write a console to figure it out at the moment. The console seems great if it worked though.