You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed that since the maintenance on 03-06-13, that an api call that includes the client_id parameter will cause the api to return an empty "streams" object.
The above will return an empty "streams" object, even if the channels you poll for are online. But if you drop the client_id parameter, then it will return a "streams" object with data about the online channels. IE:
Not a huge issue, since I can fix it on my end by dropping the client_id. I am however worried about future issues with rate limits if I cannot include my client_id.
Just wanted to point this out,
-Nox
The text was updated successfully, but these errors were encountered:
We recommend not using the client_id parameter in the URL anymore. Don't worry about rate limiting because we currently don't have a strict policy with regards to rate limiting. This issue was caused by a new feature we were pushing out, but should be fixed in ~20 minutes.
Greets,
I've noticed that since the maintenance on 03-06-13, that an api call that includes the client_id parameter will cause the api to return an empty "streams" object.
Example:
https://api.twitch.tv/kraken/streams?client_id=YourClientID&channel=destructoid,avitag
The above will return an empty "streams" object, even if the channels you poll for are online. But if you drop the client_id parameter, then it will return a "streams" object with data about the online channels. IE:
https://api.twitch.tv/kraken/streams?channel=destructoid,avitag
Not a huge issue, since I can fix it on my end by dropping the client_id. I am however worried about future issues with rate limits if I cannot include my client_id.
Just wanted to point this out,
-Nox
The text was updated successfully, but these errors were encountered: