Authorization scopes problem

API
1

i’ve being using tokengenarator for my bot for sometime now, but i wanted to read channel:points redemptions, when i subscribe to that on the evensub api it does not work, 403 not autorized or missing credentials, but if i create my own toke it does, but here is the kicker, if u do my own token the chat sub does not work

any ideas ?

ps.: this is url i’m using to start the flow https://id.twitch.tv/oauth2/authorize?response_type=code&client_id=ID&redirect_uri=https%3A%2F%2F127.0.0.1%3A8083&scope=analytics:read:extensions+analytics:read:games+bits:read+channel:bot+channel:edit:commercial+channel:manage:ads+channel:manage:broadcast+channel:manage:extensions+channel:manage:guest_star+channel:manage:moderators+channel:manage:polls+channel:manage:predictions+channel:manage:raids+channel:manage:redemptions+channel:manage:schedule+channel:manage:videos+channel:manage:vips+channel:moderate+channel:read:ads+channel:read:charity+channel:read:editors+channel:read:goals+channel:read:guest_star+channel:read:hype_train+channel:read:polls+channel:read:predictions+channel:read:redemptions+channel:read:stream_key+channel:read:subscriptions+channel:read:vips+chat:edit+chat:read+clips:edit+moderation:read+moderator:manage:announcements+moderator:manage:automod+moderator:manage:automod_settings+moderator:manage:banned_users+moderator:manage:blocked_terms+moderator:manage:chat_messages+moderator:manage:chat_settings+moderator:manage:guest_star+moderator:manage:shield_mode+moderator:manage:shoutouts+moderator:manage:unban_requests+moderator:manage:warnings+moderator:read:automod_settings+moderator:read:blocked_terms+moderator:read:chat_settings+moderator:read:chatters+moderator:read:followers+moderator:read:guest_star+moderator:read:shield_mode+moderator:read:shoutouts+moderator:read:suspicious_users+moderator:read:unban_requests+user:bot+user:edit+user:edit:broadcast+user:edit:follows+user:manage:blocked_users+user:manage:chat_color+user:manage:whispers+user:read:blocked_users+user:read:broadcast+user:read:chat+user:read:email+user:read:emotes+user:read:follows+user:read:moderated_channels+user:read:subscriptions+user:write:chat+whispers:edit+whispers:read

2

webhooks/conduits or websockets

Generally speaking those are for testing and shouldn’t be used in production use cases.

Not sure what “chat sub” is here, not sure if you mean IRC or eventsub.

As to the 403 depends on the transport for what advice is to be given:

webhooks/conduits

  • create a user token with the needed scopes between the user in question and the clientID
  • then create an app access token and create subscriptions

websockets

  • use create a user token with the needed scopes
  • away you go, connect to the socket and go

your errors sounds like webhooks/conduits and potentially juggiling client ID’s

3

i’m using websocket, thanks anyways

4

Then theres nothing obviously wrong here.

You have a lot of scopes in that list but the needed scopes for the channel.channel_points_custom_reward.add type (EventSub Subscription Types | Twitch Developers) is present, which is channel:read:redemptions (or it’s manage counter part)

This is code flow so you did exchange the resulting code for an access token? Normal under “staight” websockets you’d expect implict auth here since this would be userland side.