The scope you are requesting is currently unavailable

API
1

Hey,

Im currently working on a website, that requires an Authentificationtoken from the user with the “chat_login” scope. But whenever a make a request for getting it, I get the following message as an response:

Sorry, the scope you are requesting is currently unavailable. Please contact integrationsuccess@twitch.tv for next steps.

My Request-URL looks like this:

“https://api.twitch.tv/kraken/oauth2/authorize?response_type=token&client_id={My-ClientID}&redirect_uri={My RedirectURL}&scope=user_read+chat_login”;

I only get this typ of response, when I use the “chat_login” Scope in the URL. Otherwise it works fine.
Has anyone an idea why this happens, because on other websites of me it works like this perfectly.

Thank you in advance.

2

Did you contact integrationsuccess like it suggests?

And when you say “this is my request-url” you are redirecting people to that url and not cURL GETting it?

3

Did you contact integrationsuccess like it suggests?

Yes I contacted them, but i got no reply so far.

And when you say “this is my request-url” you are redirecting people to that url and not cURL GETting it?

I redirect them to that url. Sorry if I explained that badly :smile:

4

For anyone with the same Problem. They answered my E-Mail with the following:

This is an issue we are currently aware of and are actively working to resolve.

5

@jonas-weinhardt Did they manage to fix it for you? I am having the same error and it happens on chat_login only. The rest of the scopes work fine.

6

I also have another update to this thread. This is what I was told via email.

This is a known issue from the chat_login scope after a security update.
Can you provide your clientID and the reason you need this scope so we may include you on the scope’s whitelist?

You will need to provide your app’s Client ID and the reason you want to use chat_login in your scope.

7

I’m able to successfully get a chat_login token via https://twitchtokengenerator.com

8

Applications created prior to this thread are whitelisted to be able to provide tokens with the chat_login scope. Any new applications will require connecting Twitch to request the client ID be whitelisted.

9

15 Sept, i am getting the same error as well.

{“status”:400,“message”:“Sorry, the scope you are requesting is currently unavailable. Please request access to this scope by completing the form at https://dev.twitch.tv/limit-increase.”}

10

Fill out the form to request access if you need it.

11

Thats not suitable in my case. i am providing a bot to users/streamers, and i require them to create a twitch app for making the bot capable to query the v5 API. But the primary function of the bot is to login to chat, the streamer who downloads the bot cant go via this procedure of filling in the form and waiting for X days before the app will be capable of getting tokens with chat_login scope.

12

You could try the new chat:read, chat:edit, and channel:moderate scopes since it looks like those don’t need to be whitelisted. They were recently introduced after chat_login started being abused but have not been added to the documentation yet.

1 Like
13

Yes, i will instruct the users to create a token via https://twitchapps.com/tmi/ (which has the mentioned scopes) and add manually the extra scopes they need for API access. thank you

14

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.