Programattically Get User OAuth Token for Subscriber Notifications

[BarryCarlyon]

@MountainRiderAK

lol @ "you could [have] used {self.tim_token} ". bruh, that was one of the first things I tried. You really don’t understand how bad the documentation and support for Twitch is if you think I didn’t literally spend hours trying everything I could think of before finally breaking down and asking a question here.

I predict the error there was that you got “client-id and token don’t match” as the token looks like it would of been generated via the TMI Token Generator mentioned in example_config.json, so you would of had to have used TwitchApps Client-ID.

The general advice is to not use a third party to generate tokens.

So right now your code uses a token from Service A to run the bot, and a token from Service B to run webhooks. So you are managing Two Sets of tokens from two Different providers, where the first set you can’t auto refresh as it was generated via a third party. (and you don’t have the refresh token or client secret to automate refreshing of the token at bot boot)

Side note: TwitchApps is probably still generating tokens that last forever, but those tokens will get killed in the not to distant future.

@BarryCarlyon

Yes, either use the token that you are using for the bot to login to chat with, or use a server to server token aka App access token aka “client credentials”

I covered that here.

But I didn’t know you were using a Token from a Third Party Service, which introduces it’s own problems.