I know API support isn’t exactly a top priority for Twitch, but I really wish something can be done about these issues. /streams often returns a user object instead of a channel object. /streams sometimes returns corrupt data (or an object for a completely unrelated user/channel). /streams sometim…

At least some sort of acknowledgement by the devs would be appreciated!

They are already fully aware of the broken state of the API, but there’s been little-to-no API upgrades since 2013. We might eventually see an improved API, but I wouldn’t count on that being anytime soon. Your best bet would be to throw out all the bad data you get.

Thank you, night. I guess I’ll have to come up with some ghetto methods to ensure that received data are reasonably correct.

Hi jkface, If you can provide concrete examples, it would be immensely helpful in making sure these issues can be verified and resolved. For example, when you say that /streams returns “corrupt data”, in what way is it corrupt? Is the response malformed? Thanks!

You can see some concrete examples in this thread: [image] /channels/:channel/ occasionally not returning followers/views count API There is a bug that’s been going around for a long time causing the channel object to get mixed…

The issue the spawned that thread was temporary – it was introduced and fixed within about eight hours. Though it is interesting that 3ventic claims it’s been going around for a long time. If you have examples outside of that window I’d love to see them. Thanks!

It’s been around for a long time in other endpoints where the user/channel object is part of the response, /streams for example. The whole response being incorrect was new and more serious

I have a script that repeatedly calls /streams and goes through the list of streams until the viewer count falls below a certain number. Well, the script often ends prematurely because /streams returns data with faulty viewer counts. The following is a good example of what gets returned. stream: …

Thanks, that information is helpful! How often are you calling /streams and how often would you say that you see these types of issues?

I tried to recreate the problem just now and I’m beginning to think the above example isn’t quite representative of how the bug typically behaves. I configured my script to call /streams until it gets data for about 450 top streams. I ran it in terminal repeatedly with random breaks in between each …

Multiple bugs with /streams - it's pretty broken

API

OurFlagIsMined July 14, 2015, 1:19am 6

You can see some concrete examples in this thread:

Topic		Replies	Views
/streams/ returning a user object instead of channel API	4	2003	May 4, 2015
Twitch API Bugged...? API	14	8339	May 4, 2015
/channels/:channel/ occasionally not returning followers/views count API	6	2167	July 17, 2015
Inaccurate followers/views values from streams endpoint API	0	1533	April 22, 2015
/streams/:channel returning inconsistant results API	4	3928	September 12, 2013

Multiple bugs with /streams - it's pretty broken

Related topics