topic Re: Web API quota updates for Development Mode in Spotify for Developers

Web API quota updates for Development Mode

ThePodfather — Thu, 23 Jul 2026 10:54:40 GMT

Hey everyone, I've created this thread to share some updates to how quotas work for Development Mode apps on the Spotify Web API to help you better organize your projects.

We've shared a Blog post that explains everything in detail. Here's the short version:

What's changing

Client ID limit increased from 1 to 25 per developer account
Quota counting is now per developer account, not per Client ID — all your Development Mode apps share a single quota
We’re making it easier to distinguish quota limits from rate limits, so the 429 error responses now include a "reason": "QUOTA_EXCEEDED" field.

What you need to do

Handle the new 429 response body — use the reason field to distinguish quota limits from rate limits
If you use multiple Development Mode Client IDs, be aware they now share a single quota pool

We'll do our best to answer questions in this thread, and we'll add any updates to this post..

Re: Web API quota updates for Development Mode

AdamusEsq — Thu, 23 Jul 2026 12:47:36 GMT

The increased client ID limit is definitely a step in the right direction; only being allowed one was incredibly restrictive. That said, I'm curious about how the shared quota affects existing apps. For those of us who had multiple client IDs before the changes in February, I assume we were able to make more API calls overall since the quotas were per client ID. Now that they're combined, would this reduce the number of overall API calls before hitting the quota?

Re: Web API quota updates for Development Mode

garr1k — Thu, 23 Jul 2026 14:35:52 GMT

my account says Development Mode but i tried creating a new app and it won't let me save. i have only one total app in my account.

the OP said "Client ID limit increased from 1 to 25 per developer account" so why am i still getting blocked from creating a second app? do i need to wait 24 hrs for the changes to take effect?

EDIT: i've been trying every 30m and finally i was able to add a second app! thre was a 4hr delay between when the announcement was made and when the site actually acknowledged the new changes

Re: Web API quota updates for Development Mode

smotify — Thu, 23 Jul 2026 14:02:55 GMT

So quick question tangentially related to this. The developer mode limits me to 5 users and I see the extended Quota takes that to 25 but if I want to take my app live and have it accessible to more than 25 people. How on earth doI do that. And I also see there is a requirement for the quota extension for you to be a registered company so does that lock out hobby devs?

Re: Web API quota updates for Development Mode

tylerpashigian — Sat, 25 Jul 2026 17:59:44 GMT

@smotify I am running into the same thing. I know I've done this in the past with no issue, but seems like some changes went into place earlier this year and now you need 250k monthly active users to go beyond 5 users per app? Is this Spotify's way of saying it's only allowing personal apps? Would love to know if anyone knows a way around this. Been working on a fun app the last few weeks and was bummed when I tried to share it with some friends and ran into this.

Re: Web API quota updates for Development Mode

hkarlsen_06 — Mon, 27 Jul 2026 02:26:33 GMT

same. this is devastating...

Re: Web API quota updates for Development Mode

eastoncrafter — Tue, 28 Jul 2026 14:47:00 GMT

@tylerpashigian I'm in the same boat, I run a yourspotify instance for me and my friends, and my plan currently is to have 25 yourspotify instances, capable of hosting 5 users each. This is completely stupid.
The spotify api is a very important piece of what made it so popular in the first place. It has allowed developers to create whatever their hearts desire and to share it with a small audience of friends and family. The api client application limits put in place have been detrimental to that original thriving ecosystem of developers, and with no clear reason behind moving to the new limits. Additionally, restricting extended quota to services that have 250 THOUSAND users is just plain stupid. How are any small spotify applications supposed to take off organically anymore?

Re: Web API quota updates for Development Mode

Dover — Tue, 04 Aug 2026 10:29:28 GMT

I've been following this and the other thread around this limitations of the developer API. I've developed an app that's isn't going to be heavy on API requests and shouldn't hit any sort of limits. However, I can't publish it due to the user limit. The user is to log into to their own Spotify account to create playlists for themselves. How can we possibly reach 250,000 MAU if we can only launch a beta to 5 users?

Re: Web API quota updates for Development Mode

Kumkwat — Tue, 11 Aug 2026 06:09:04 GMT

Hi!
Still I can't connect my HomeAssistant with Spotify integration however I have "development mode" at my app

The Spotify API has been changed and Developer applications created with a free account can no longer access the API. To continue using the Spotify integration, you should use an Spotify Developer application created with a Spotify Premium account, or upgrade to Spotify Premium.

Re: Web API quota updates for Development Mode

nylocx — Sat, 15 Aug 2026 13:39:17 GMT

I am developing a small event app for my family that is similar to Festify. To get the playback state, I was polling every 3 seconds because Spotify does not provide an event-based API for that, and I ran into the new limits, which are not really documented.

It feels like Spotify is treating every developer as a potential source of abuse by default. I will now work around this by falling back to 30-second polling during idle periods, but the fact that I need to do this at all feels wrong.

Re: Web API quota updates for Development Mode

bdev2026 — Sun, 16 Aug 2026 19:26:27 GMT

Why is there no clearly defined quota and quota reset?

I have hit 429 - QUOTA RATE EXCEEDED but there is nothing to guide me as to when this resets or not and requiring 250k monthly active users makes no sense if your app relies on Spotify to use in the first place

Re: Web API quota updates for Development Mode

Sintypitch — Tue, 18 Aug 2026 23:10:17 GMT

It's been six months since we've been waiting for more clarity regarding the possible permanent status of the 250,000 MAU quota, which roughly is 5% of the adult population of my country and exceeds any reasonable startup status.

We currently launched our event based app with 150000 artists (techno) and have now fully integrated Soundcloud and Apple Music into our key features. While we understand that Spotify wants to limit the abuse of its valuable data, we hope that reasonable changes will happen in the near future for potential new partnerships, for solo entrepreneurs or businesses like us.

Re: Web API quota updates for Development Mode

nayborbob — Thu, 03 Sep 2026 20:38:16 GMT

**Development Mode API quota — guidance for designing well below the limit?**

I'm developing a personal Android Spotify companion app in Development Mode. I'm trying to design the app so that its normal operation stays comfortably below Spotify's Development Mode API quotas rather than simply reacting after receiving a `429 / QUOTA_EXCEEDED`.

I understand from Spotify's documentation that Development Mode requests are grouped into quota buckets, and that the specific bucket groupings and limits aren't published and may change.

Could Spotify provide some practical engineering guidance on what level of API usage a Development Mode app should target?

For example:

* Is there a recommended maximum or target number of Web API requests per hour, day, week, or fortnight for a Development Mode developer account?
* What utilization level would Spotify consider comfortably below the Development Mode quota?
* What is the quota/reset period — hourly, daily, weekly, rolling, etc.?
* Do different endpoint groups have substantially different quotas?
* Are playlist metadata, playlist-item paging, playback-state polling, search, and playback-control requests in different quota buckets?
* When `reason: "QUOTA_EXCEEDED"` is returned, is there any way for an application to determine when that quota will reset?
* Is there any API response/header or Developer Dashboard information that lets a developer determine current quota consumption or remaining quota?
* Besides caching, playlist `snapshot_id`, batching/page-size optimization, lazy loading, and respecting `Retry-After`, are there other practices Spotify recommends specifically for staying comfortably below Development Mode quotas?

I'm not looking to maximize traffic up to the limit. I'd like to architect the application so normal use consumes only a small fraction of the available quota, but it's difficult to establish a safe design target without knowing the approximate scale or reset period.

Even guidance such as "design for fewer than X requests per user per day/week" or "keep normal operation below roughly X% of the quota" would be very helpful.

Thanks.

Re: Web API quota updates for Development Mode

yu0223 — Mon, 07 Sep 2026 14:43:20 GMT

Hello,

I am currently getting a 429 QUOTA_EXCEEDED error with my Development Mode application.

I understand from the July 23, 2026 quota update that Development Mode quotas are calculated per developer account.

Could you please tell me where I can request a quota review or quota increase for my application, if such an option is available?

This is quite urgent because I need my application to be working by 1:00 PM tomorrow (September 😎.

I am already reducing API requests by adding caching, deduplication, and avoiding unnecessary repeated searches.

Could you please point me to the correct request form, support channel, or process for this?

Thank you for your help.

Re: Web API quota updates for Development Mode

paulmurray48 — Wed, 09 Sep 2026 18:09:30 GMT

I have been developing a Spotify controller app for smart watches for a while, and today read about this quota. This seems insane. How can a new developer get from 5 to 250000 with no capability to release an app to more than 5 people? Surely whoever came up with that idea wasn't thinking clearly? My app does not infringe on any of Spotify's rules, the app doesn't contravene any of their "not allowed" list, I've put serious time and effort into the watch app, the phone app etc and now it appears it was all for nothing....or so that a massive total of 5 people can enjoy it! When this will be addressed as this makes no sense for people who create apps that promote using Spotify.

Re: Web API quota updates for Development Mode

josesmartin — Mon, 14 Sep 2026 04:28:00 GMT

Hey Spotify, no responses to any posts in this thread?
Is there literally no way to have anything but either less than 5 users or OVER 250,000 users?? Do you understand how this is not just unlikely but literally impossible. What the **bleep** is this? Please respond.

Re: Web API quota updates for Development Mode

Guaruja20 — Mon, 14 Sep 2026 21:56:39 GMT

também estou nessa situação, e o pior são aplicativos que vejo que estão fazendo que favorecem a própria platafomra deles!, o meu mesmo traz uma facilidade pra eles que se quiseem saber muitos aqui teriam o potencial de elevar a marca deles com seus aplicativos!

Re: Web API quota updates for Development Mode

Guaruja20 — Mon, 14 Sep 2026 22:22:38 GMT

Olá,

Entrei em contato com o suporte do Spotify anteriormente a respeito de uma solicitação de Modo de Cota Estendida para meu aplicativo de desenvolvedor.

Entendo que esta solicitação está fora do escopo do suporte geral ao usuário. Solicito gentilmente que esta mensagem seja encaminhada para a equipe do Spotify para Desenvolvedores ou que me forneçam o canal de contato correto para solicitações de extensão de cota da API Web para pequenos aplicativos em produção que ainda não se qualificam para o Programa de Parceiros.

Meu aplicativo está disponível na Google Play Store. Usuários reais estão sendo bloqueados com um erro 403 após concluírem com sucesso a autenticação OAuth do Spotify — unicamente devido ao limite de usuários do Modo de Desenvolvedor. Isso está prejudicando diretamente a credibilidade do aplicativo junto aos usuários finais.

Estou em total conformidade com todas as Políticas para Desenvolvedores e Termos de Serviço do Spotify. Estou simplesmente buscando uma solução para aplicativos legítimos de pequeno porte.

Qualquer ajuda para redirecionar esta solicitação para a equipe correta será muito apreciada.

Obrigado,
Marcos