We’re having an issue with getting 429s on our extension now that we’ve released it. Our extension checks for the state of the stream to see if the streamer is live to display the ability to make a bits transaction. When the streamer is offline and the extension is displayed as a panel, we inform the viewer that the streamer is offline.
We are using:
To check if live:
For authenticating the call:
That is ran in our backend and we call our end point on the front end.
In the front end, what we are doing is while the api returns that the channel is offline we called the api again until it returned online in 0.5 second interval. After it returns online we stop the calling the api.
Does this look like it should run into issues with the Twitch API rate limiting?