62

Not currently

the validate endpoint may suffice

1 Like
63

If all I want to do is create a JSON or RSS feed of streams and videos under a specific category, I need to set up server-side scripting to generate and send an App Access Token? And why can’t Twitch just provide feeds natively from its web server?

1 Like
64

You should make a feature request to the Uservoice for RSS Feeds

https://twitch.uservoice.com/

1 Like
65

It seems like there were changed to V5 (Kraken) endpoints too.

As of this morning, my API calls to V5 are now requiring not just an OAuth token as before, but now a client ID as well.

1 Like
66

v5 always had the Client-ID as requirement for as far as i know.

1 Like
67

According to the v5 documentation, you are incorrect.

To identify your application to the API, every request must include your application’s client ID, either explicitly or implicitly by including an OAuth token. If you use an OAuth token in your request, the API figures out the client ID for you.

1 Like
68

Welp guess i just screwed the auth headers when i tried the calls.

1 Like
69

I have submitted a PR and get Merged on passport-twitch.js so you can use :slight_smile:

1 Like
72

So now when I want to do something as simple as checking if user stream is live or not, my website visitors first have to authorize themselves with Twitch, get the OAuth token and them my website can do the “Is streamer live or not” check?

1 Like
73

Yes, you will either need to have a login with Twitch button on your site and use a token from the user, or you can have your server generate an App Access Token itself and do all of the requests to see if the streams are live on your server and just send that data to the users frontend.

2 Likes
74

Yes, or have a server that fetch the information and you call this server from your website

2 Likes
75

And as others have suggested, if you move the call to your server, you can utilise webhooks to monitor for stream up/downs instead making you code not need to call the API at all

1 Like
76

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
77

There are no sustainable plans for that. You can currently still use Kraken without an OAuth token, but that’s deprecated and will be removed at some point in the future.

After Kraken is removed, and Helix requires an OAuth token, your options are to use the Implicit OAuth flow (which only has to be done once per user, it’ll be transparent to them after that), or use a backend server to make the requests.

1 Like
78

Is this going to help or hinder unwanted bots in most peoples chats trying to steal gifted subs? Just wondering.

1 Like
79

Connections to chat has nothing to do with Helix, so this will have no impact whatsoever.

2 Likes
80

Oh good I have enough trouble dealing with them, this eases my mind thank you

1 Like
81

Can we have more time to implement these features? I do not keep up with these changes actively on the forums and this has broken my app.

1 Like
82

for anyone who had apps break today, I put together a tiny Node utility that will get app-to-app OAuth tokens so you can get your bots back online

1 Like