Type in your question below and we'll check to see what answers we can find...
Loading article...
Submitting...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
Please see below the most popular frequently asked questions.
Loading article...
Loading faqs...
Please see below the current ongoing issues which are under investigation.
Loading issue...
Loading ongoing issues...
Hello,
I hope you are doing well.
I am currently developing a platform for streamers that integrates Spotify playback and allows viewers to add songs to the queue through an intelligent bot. The project relies on the Spotify API and has been a significant investment of time and effort for me.
When I encountered the 5-user limitation in development mode, I followed the available guidance, registered my company, and submitted a request to the Developer Support team.
At this point, I am simply feeling a bit lost regarding the next steps. I fully understand that there are processes and requirements in place, but I am unsure how a small project like mine is expected to grow while remaining limited to a handful of users.
I would be very grateful for any advice or guidance from the team or the community on the best path forward.
Thank you for your time, and for all the work you do supporting developers.
Kind regards,
Yaël
Solved! Go to Solution.
Hello Yaël, @LaPileTW
Thanks for explaining the use case clearly.
The 5-user limit you're seeing is expected for apps in Development Mode. Extended quota mode is the path for apps intended for a wider audience, but the current requirements are quite strict. Spotify lists requirements such as being a registered organization, operating an active launched service, commercial viability, availability in key Spotify markets, and a minimum active user threshold.
One thing I'd be careful with in your case is the playback and queueing model. A streamer tool where viewers add songs to a queue through a bot may raise policy questions depending on exactly how it works. Spotify's policy has restrictions around automated manipulation, streaming use cases, non-interactive broadcasting, and commercial use of streaming apps. So it would be worth reviewing the dedicated documentation closely and making sure your app is framed around individual user control and authorized playback, not automated or shared broadcast-style listening.
Since you already submitted a request, the practical next step is to wait for the review response by email. The quota documentation says reviews can take up to six weeks. Also make sure the email attached to your Spotify developer account is active and monitored, since that's where feedback should be sent.
In the meantime, I'd suggest:
Confirming your app's Dashboard shows the request as sent
Reviewing whether the app can operate compliantly within Development Mode while testing
Preparing a clear explanation of how users authorize playback and how your bot avoids automated manipulation
Checking that your company details, privacy policy, and terms are complete and accurate
I know that may not be the answer you were hoping for, but there does not appear to be a separate small-project route around the current quota requirements. Hopefully the review team can give you clearer feedback on whether this use case is eligible.
Hello Yaël, @LaPileTW
Thanks for explaining the use case clearly.
The 5-user limit you're seeing is expected for apps in Development Mode. Extended quota mode is the path for apps intended for a wider audience, but the current requirements are quite strict. Spotify lists requirements such as being a registered organization, operating an active launched service, commercial viability, availability in key Spotify markets, and a minimum active user threshold.
One thing I'd be careful with in your case is the playback and queueing model. A streamer tool where viewers add songs to a queue through a bot may raise policy questions depending on exactly how it works. Spotify's policy has restrictions around automated manipulation, streaming use cases, non-interactive broadcasting, and commercial use of streaming apps. So it would be worth reviewing the dedicated documentation closely and making sure your app is framed around individual user control and authorized playback, not automated or shared broadcast-style listening.
Since you already submitted a request, the practical next step is to wait for the review response by email. The quota documentation says reviews can take up to six weeks. Also make sure the email attached to your Spotify developer account is active and monitored, since that's where feedback should be sent.
In the meantime, I'd suggest:
Confirming your app's Dashboard shows the request as sent
Reviewing whether the app can operate compliantly within Development Mode while testing
Preparing a clear explanation of how users authorize playback and how your bot avoids automated manipulation
Checking that your company details, privacy policy, and terms are complete and accurate
I know that may not be the answer you were hoping for, but there does not appear to be a separate small-project route around the current quota requirements. Hopefully the review team can give you clearer feedback on whether this use case is eligible.
Hi JBayudz,
First of all, my apologies for the delayed reply, and thank you for your detailed response and for taking the time to explain the current process.
Regarding the playback and queueing model, I completely understand your point and this was one of the first things I verified before building the platform.
The bot does not automate playback, manipulate streams, or provide any form of shared listening experience. Playback always remains under the control of the streamer through their own Spotify account and authorized devices.
The purpose of the bot is mainly to display information about the currently playing track and to provide a simple interface for viewers to suggest songs. For example, a viewer can send a message such as:
@NOVIABOT add "Blinding Lights" by The Weeknd
The bot then adds the requested track to the streamer's playlist or queue using the streamer's authorized Spotify account and permissions. No music is played automatically and no playback actions are performed on behalf of viewers.
I have already reviewed Spotify's Developer Policy and Terms carefully, and I designed the integration specifically to remain compliant with those requirements.
My quota extension request has already been submitted through the Developer Dashboard, so I will wait for the review team's response and provide any additional information they may require.
Thank you again for your guidance and feedback.
Best regards,
Yaël/LaPileTW
Hey there you, Yeah, you! 😁 Welcome - we're glad you joined the Spotify Community! While you here, let's have a fun game and get…