First off, don’t use other peoples generators.
The best advice here is to create the loop on your own server.
Second off, this generates an implicit oAuth token, which when it dies, means you need to manually recreate the token.
If you used “regular” oAuth on a server you control, you’ll get a refresh token which you can use to generate a new token automatically.
This sounds like you logged in as your bot, which means you granted the bots user client ID to read the bot users redemptions.
When you need to login as you.
You need to create a link betwee your application and your broadcaster account
In order to read the broadcaster accounts redemptions
Doesn’t matter who own’s the clientID. (People generally do not have bot accounts own clientID’s, they attach clientID’s to a “real” user for easier managment of applications/clientID’s)
If you take the token and call the validate endpoint
The user_id returned in the result needs to be the broadcasters user_id. I anticipate the token you have will return the bot’s user_id instead. which is your problem.
So essentially, there should be no bot user involved here at all.
TLDR: You need to generate a token for the broadcaster. Owner of the client_id is irrelevant.