Requiring OAuth for Helix Twitch API Endpoints

This seems to remove the use of many of the APIs for anyone building a JAMStack site without a back end.

If we want a banner to display a ‘live’ message that then links out to a twitch channel my impression is we can longer do this without prompting every user to login to twitch (even though our site is not twitch related) or requires a server call on every request (defeating the purpose of serving a static html page).

This is a fairly popular method for delivering sites with frameworks like Gatsby and Next.JS. Are there any ideas for implementing basic ‘check if live’ APIs without oauth, implicit auth, or spinning up a server only for this functionality?

1 Like