No. You must use a user token
When the token expries you’ll need to use the refresh token to get a new token.
So .env might not be practical since the key will change periodicailly.
Sure use .env for ClientID and Secret (since you need the secret to run refreshs)
But the actual token/refresh token probably does work well in .env as it changes
This will give you a useless user token. As when the user token dies you’ll have to manually give it a new token
You should create your own oAuth flow using your own ClientID. And then seed the bot with a user token/refresh token.
I touched on that here. You really shouldn’t be using someone elses generator for your own tools. If that ClientID gets revoked all your stuff dies
This is the wrong kind of token for a chat bot.
As A Client Creds token does not represent a user.
channel:moderate is the required scope, this lets this key be able to send /ban
However the account will also need to be a mod on the channel you are trying to perfrom moderation actions on.
This indicates that your bot user account is not a mod on carbow
And/or the User Token used omits the channel:moderate scope.