I’m trying to use EventSub.
Sorry, seems like the bearer token liked to troll me. Seems like now is working. I regenerated again the code after at least 30 min and seems to work fine. I don’t know if it has something to be with the changes on scopes or with the privileges being granted after the token generation.
Anyway, as I asked on the last part, could I know the purpose of per user (or as it seems to me but I don’t exactly know) bearer tokens? I mean using this authorization. I don’t know if the permissions are granted and then the next bearer tokens can be used on that channel, and that could be way it started working now, or if the token that I get after this authorization has something special.
I get the following JSON with the information of the token by the retrieved code:
{
"access_token": "REMOVED",
"expires_in": 15738,
"refresh_token": "REMOVED",
"scope": ["bits:read", "channel:read:hype_train", "channel:read:redemptions", "channel:read:subscriptions", "user:read:email"],
"token_type": "bearer"
}
Even having the scope and being a bearer token, gives me the next JSON when trying to make a subscription using it:
{
"error": "Unauthorized",
"status": 401,
"message": "Must provide valid app token."
}
Edit: Sorry, I already had in my mind about removing the tokens, but my head is just messed up. Anyway luckily it’s just a test bot without oficial porpuse, so I can’t delete it just in case.