Illegal scope user-read-email

[jacobimpson]

Hello, I have a Spotify Developer App that was granted quota extension back in early 2024. I am trying to use this app to impliment 0Auth. The only scope this requires is user-read-email, but no matter what I try, I recieve Illegal Scope errors.

When I set up a new test Spotify application in development mode (new clientId/secret) - everything works perfectly. 

My suspicion here is that my previous application was granted access to a limited number of scopes that I was using at the time. Does this sound plausible? And would it be possible to get an additional scope added to my existing application? 

My understanding is that my app should have access to all scopes in the developer documentation, but that doesn't seem to be the case.

Thank you. 

[Ximzend]

Hi @jacobimpson 

Thanks for posting in the Spotify Community!

I understand you're trying to use a new scope with an app that already has a quota extension. Unfortunately, this isn't directly possible because once a quota extension is granted, the scopes are locked in.

However, you can request a scope extension. On your app's detail page, look for a green link that lets you submit this request.

Hope that helps!