Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

client_id parameter causes empty streams object #69

Closed
NoxiusInfernus opened this issue Mar 7, 2013 · 1 comment
Closed

client_id parameter causes empty streams object #69

NoxiusInfernus opened this issue Mar 7, 2013 · 1 comment

Comments

@NoxiusInfernus
Copy link

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

@mpoon
Copy link
Contributor

mpoon commented Mar 7, 2013

Hi Nox,

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.

Cheers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants