Programattically Get User OAuth Token for Subscriber Notifications

[BarryCarlyon]

@MountainRiderAK

So if you’re not too busy, maybe you could spend some time improving the documentation.

I don’t write the documentation and I cannot make modifications. I am not Twitch staff. I’m just another developer like you.

MountainRiderAK/TwitchChatBot/blob/master/example_config.json

Like 15, mentions the third party token generator.

@MountainRiderAK

Maybe instead of just pointing out the flaws (which you are really good at, you’ll make a great parent), you might also provide links to the correct way of doing things.

I already did this numerous times in this thread by linking to the oAuth documentation that Twitch has. Given that oAuth on Twitch works the same as many other services that implement oAuth. (Except Twitter that uses a older version of oAuth).

@BarryCarlyon

But you must of been using the broadcasters access token before this change. All this change does is require all helix endpoints to use a token, but the subscriber endpoints are gated by the broadcasters Twitch oAuth token anyway. So the change shouldn’t of effected you

The docs cover how to get tokens, the correct way to do something depends vastly on what you application is, how it runs, what permanent storage is available if any, is it stateful or stateless, what does it run on, what language is it to be built in. But my initial answers were wrong because you asked about Subscriber Notifications to start with. And the oAuth change for Helix requires people using subscriber notifications to make no changes, since you need the broadcasters oAuth.

And as I already said elsewhere, you started asking about authentication Subscriber notifications, when in reality you were talking about authentication for followers webhooks. Which are two totally different things.

Basically it’s all got a bit of a mess due to wrong terminology from the get go.