I’m trying to listen to the channel-points-channel-v1 topic using pubsub. In the scope when generating my token, I’ve put channel:read:redemptions as stated in the documentation : https://dev.twitch.tv/docs/pubsub#topics .
But when i send the LISTEN message, the answer comes back with the error ERR_BADAUTH.
If I add “channel_read” in the scope, it works without the error. But this scope is deprecated from what I understand, and I don’t want those privileges, which I shouldn’t need.
Am I doing something wrong or am I missing something ? Or is it a bug in the API ?
The token is a user access one, generated via the Implicit code flow. If I try a request to https://id.twitch.tv/oauth2/validate with the header Authorization: Bearer and the token, I’ve got a json response, with a login key and a value which is my username.
I’m using the endpoint : https://api.twitch.tv/kraken/channel to find the channel id. So it’s the right one. And if I only keep the following topic, I don’t have the error, and if I try a follow on my channel, I’ve got the message through pubsub which confirm it’s the right one.
Any idea ?
Is there another to find my channel id ? I’m using v5 api for that, which is deprecated. Maybe there’s something new ?
User/Channel ID’s the same regardless of white API version you use.
So to confirm it is working with the “old scope” on the channel points topic but not the scope defined in the documentation?
Which doesn’t make sense since channel points is post Helix existing.
Edit: I tested I cannot replicate an issue. I generated a brand new access token for myself using the channel:read:redemptions scope and it booted right up.
It seems it does. Try adding it and you’ll see you receive messages with the topic following.channelid .
I checked the code you gave here. Thanks a lot. And I replaced my v5 /channel api call with the helix /users one, and now it works without the old scope channel_read.
It seems ok now. Thanks a lot.
But can you check for the following topic please ?