Quota Extension Approved, but Scopes Reset – Urgent Assistance

[jamesking2004]

My Question or Issue

Hello Spotify Developer Community and Team,

Our team recently received approval for a quota extension request, which we deeply appreciate. In our submission, we explicitly outlined the specific scopes required for our application in the request to ensure compliance with Spotify’s guidelines. However, upon receiving the quota increase, we discovered that our previously approved scopes were reset, fully disabling our apps functionality for users. This poses a critical challenge as we’re preparing to launch later this month and rely heavily on uninterrupted API access to finalize testing and onboard users seamlessly.

We urgently seek guidance on restoring our scopes without requiring reauthentication or expediting the reapproval process to avoid delays. If any additional steps are needed from our side, please let us know—we’re happy to collaborate to resolve this swiftly. Thank you for your support, and we’re hopeful for a quick resolution to ensure our launch stays on track!

Plan

Premium

Country

United States

Operating System

IOS ond ANDROID

[Ximzend]

Hi @jamesking2004 

Thank you for posting in the Spotify Community!

To get the removed scopes back, you first need to request a quota extension through the Developer Dashboard. But keep in mind—once that extension is granted, your existing user tokens won’t automatically pick up the new scopes. Users must reauthenticate to generate tokens that include the extended permissions.

Here are some steps you can take to requesting a Quota Extension:

1. Log in to your Spotify Developer Dashboard.
2. Click on your app’s name to open its details, then hit the Settings button.
3. Navigate to the “Quota Extension Request” tab and click the “Request Extension” link.
4. Fill out the questionnaire—explain your use case, the APIs you’re using, and why you need additional scopes. (The review process may take up to six weeks, especially during peak periods.)

And again, even after your extension request is approved, the scopes granted during the initial authorization remain “locked in” on any tokens already issued. This means that to benefit from the extra scopes you now need, your users must reauthenticate. In practice, you’ll need to prompt them to log in again so that new access and refresh tokens—including the extended permissions—are generated.

Hope this helps clear things up. Don’t hesitate to reach out if you have any more questions or need further guidance. Cheers and good luck with your launch!

[jamesking2004]

No I had the quota extension approved already, but it didn't include the scopes I requested.

[Ximzend]

Sorry, I meant "Scope Extension".