@Six Confirmed. It’s because it’s multiple regions. I was seeing different behavior than you because of the locations I was using to run my tests. I used local instances and I am being blocked by client-id.
Sort of at a loss here, because how am I supposed to build a popular twitch app that only does 120 requests per minute. What if I have 120 users? That’s one API request per user? That’s impossible to scale. And the endpoints I want aren’t available with just client-id.
I’m at a loss here. The only solution to this problem seems to be to create 1,000+ clientids and bake them into my app using a random distribution. I feel like twitch would not look kindly upon that.
For now I think my suggestion here is to revert to the v5 API since that isn’t rate limited. And hope twitch comes to their senses on the New Twitch API and realize that phones are an actual market that exists in 2017.
Limits need to be per-oauth not per-client-id. Per-client-id doesn’t scale.