February 2026 Spotify for Developers update: thread

[ThePodfather]

Hey everyone, I’ve created this thread to provide an open space for discussion, feedback, concerns or ideas on an upcoming update to Spotify for Developers access.

We’ve shared a blog post that explains what’s changing and why. Please use this thread to share any thoughts about the update.

We'll try our best to answer questions but we're not in a position to respond to every reply in this thread. Where appropriate we will add updates in this post to ensure visibility to all commentators (instead of burying the information in the comments). I am not able to reply to individual DM’s but please note that everything shared here will be read and considered. If related questions or discussions pop up elsewhere in the community, we’ll link or merge them back here so everything stays in one place.

Thanks for taking the time to share your thoughts.

Update:
After some review and following feedback we have received from you below, we have decided to postpone endpoint access changes for existing Development Mode integrations. All other changes, including the Spotify Premium requirement, the authorized user cap and one Client ID per developer limit, will take effect for existing Development Mode integrations as planned. Newly created Development Mode Client IDs remain subject to the updated rules introduced on February 11. We will share additional details on revised timelines as they become available.

You can find the full details in the blog post, and we’ll add links to any supporting documentation there as it becomes available.

[GB122]

I guess I'll be going back to perfecting my "Youtube" time machine. Was over 50,000 songs from meticulous historical (1970-2025) chart data in many genres cross-referenced to Spotify links. Already filled up my 25 in beta testing. There's better partners out there. Spotify loses more than I do here, but that's business.

[JonAgra]

At this point, I'm starting to give up on Spotify. My developer "apps" (yes, apps, plural) are all personal/hobbyist projects that by no means were abusing the API. The apps I've created are solely for myself and nobody else. I use(d) them to enhance my experience with Spotify. Quite frankly, the only reason I was staying with Spotify, due to the apps I created to enhance my experience. Now that I can't use the apps I've developed (again, for myself and myself only), I have zero reason to be sticking with Spotify. 

I've already begun my transition to a superior platform that has a wide-open API for their subscribers and higher-quality audio beyond Spotify lossless. Once I complete that transition, I'll be cancelling my Spotify subscription. It's pointless to pay for something I simply can't use anymore in the way I've been using it for over 12 years. You'll be losing (many) once-loyal subscriber(s) over this, myself included.

The only way Spotify may be able to retain me as a subscriber is if they quickly address those of us who use the API non-abusively for personal and hobbyist projects, and re-open it for those of us who utilize it in this way. I'll give them 30 days to address that and implement a solution. If it's not addressed on day 31, I'll be swiftly clicking that subscription cancellation button.

[newbie_duck]

I’ve created an iOS app which improves Spotify users listening experience and I’m getting great traction from my 5 users. But I cannot launch it because you need 250K MAUs to qualify for Extended mode! I have to take my innovation and my PRO subscription to Apple Music because I won’t pay for two services at once. You are spot on with stifling innovation, Spotify won’t recognise this until it’s too late. The lesson of the IT industry is capture the developers and the platform success, Spotify is alienating developers 🤯. 

[newbie_duck]

The biggest limitation to developing is the requirement for 250K MAUs to apply for Extended quota when Dev quota is 5 users!

See Quota Modes

[newbie_duck]

I’m in exactly the same position, iOS app created and limited by 250K MAUs out of the box. I have to cancel and switch family subscription to Apple Music. I’ll take some heat from family but it’s better to move now that wait for Spotify to self destruct.

[newbie_duck]

 

Sad message to family, in case you think Developers are joking. 5 users to 250K MAU isn’t working for me & I pay the bills. 

[retrodaredevil]

First I wanted to voice my dissatisfaction with all of the changes. Second I wanted to comment that the language "API access will be limited to a smaller set of supported endpoints" is offensive. This is a drastic change in Spotify API access, and the language acts as if these changes aren't a big deal. In addition to the concerns voiced in other comments on this thread, I wanted to specific talk about external_ids.

https://developer.spotify.com/documentation/web-api/references/changes/february-2026 talks about "Changes to endpoints" and "Changes to fields". Changes to fields is what I have a problem with. Specifically this for the track object:

• [REMOVED] external_ids — Known external IDs for the track.

`external_ids` contains the ISRC for tracks. This value makes it easy for developers to convert between a Spotify URI and other streaming platform URIs/links.

For this reason, I see some of these API changes as anti-competitive. They prevent developers from creating applications that can easily convert between Spotify and other streaming services by intentionally omitting data that may facilitate fair competition.

[Ph4sm4]

On the article it is stated that the changes will be applied to all existing apps on MARCH 9, IT AINT MARCH 9 YET - im already unable to add any users above 5 even though my app has been registered 6 months ago. Can u explain???

[semmu]

Folks, I think it's time to accept the fact that spotify doesn't care about indie developers, only business partners (e.g. car manufacturers, smart appliances, etc.)

It is very clear they basically don't want people to build anything based on their platform, so they are slowly killing it or making it practically impossible. The 5 user/developer to 250k MAU jump is a ridiculous requirement which is literally impossible to make. I guess for them we (the indie devs) are simply not worth the hassle, as they can get much more money from B2B partners with less maintenance, support, etc.

It's really a shame, because spotify has a huge userbase and collection of music, not to mention integrations with other (established) platforms, also alternative clients, etc., but they are slowly eliminating their own loyal userbase. Classic (contemporary) case of enshittification.

I recommend you all export your cherished playlists while you still can (via exportify.net for example), because who knows when will they axe other elementary API endpoints?

I will miss spotify, because it became the de facto standard to share music and create playlists with friends, etc., but I had enough.

[BBSD]

Can't add tracks to playlist — 403 Forbidden despite correct ownership

Hi, I'm building a song request web app using the Spotify Web API. I'm getting a persistent 403 Forbidden when calling POST /v1/playlists/{playlist_id}/tracks.

Setup:

• OAuth flow with scopes: playlist-modify-public playlist-modify-private playlist-read-private
• show_dialog=true to force account selection
• Verified via /v1/me that the authenticated user ID is 31suefks5aozg6nbhwnn4orb3cne (display name: Byron Bay Silent Disco 2)
• The playlist 58SmsBN6WGTCb08xnQTFpB was created by this same account
• App is in Development Mode

What I've tried:

• Created a fresh playlist under the authenticated account
• Attempted to make it collaborative (fails with "You cannot make public playlists collaborative")
• Made the playlist private via the Spotify desktop app
• Confirmed Client ID and Secret are correct

Question: Why would adding tracks to a playlist owned by the authenticated user return 403? Is there something specific about Development Mode or Premium Duo accounts that restricts this?

[ImBurni]

Hello how is it Possible to get the Extended Quota Mode now? i created a App and i have more than 5 Users and need it very quick, i spent so much time in my App and now its for nothing im so unhappy with it, i know so many People they got it before the changes affected and now i cannot give my App to more than 5 Peoples im pretty sad about it 😞

[JoaoAranha]

We are one week to the take down of a huge bunch of apps and still lacking proper documentation and limits... Please or postpone or put the needed to we can keep going. Thx in advance

[Miyamota]

Why can I only create one app per day? I had to delete my app to troubleshoot an issue with API scopes, and when I tried to recreate it I've been blocked. I understand imposing limits, but ONE app per day?? Come on. Deleting apps is an extreme, but sometimes necessary, troubleshooting step. Why make me wait 24 hours before I can create it again? Is there anything that can be done to allow me to create my app before tomorrow night?

[LambertSpot]

Just dropping by with an update. We don't believe it is fair that having one app blocked/disabled prevents you from ever creating a new one - so we are redesigning the system around this new one app per user model. I don't have any specific date on when you can expect to see it, but know that we are committed to shipping something asap.

Secondly we are going to address/clarify the development mode / extended quota mode next week. Historically there was a path where you start in development mode, submit your app for review, and if it was not in violation of the developer terms - would be granted extended quota mode. This is not how it has been working since the introduction of the business criteria back in April, and next week I hope we will have made things a lot more clear.

[NASMusicManager]

How about our fair request to be created an Indie Quota mode ? Something that at least show some faith in us indie developers that are willing to even someday achieve the actual in place 250MAU to be able to apply for consideration ? We are not asking for nothing new, all serious business have middle quotas and middle tiers for stimulate the continuous grow of the eco-system, so why a fair and aligned with all the companies in the World now operating with this model of several quotas of use, it's just not taken in consideration ? This sadly leave the only answer possible: Spotify don't want us anymore here and now is a B2B company, and this was just possible because of the tons of contributions from the whole develop community, since we as an army tested your API in a time where Spotify didn't had conditions to hire developers or testers, so again we are just asking for fair treatment, and it's just being denied and worst, with silence... Please consider our plead and at least say a gigantic NO !! just to we know with what we are dealing... We are adjusting code again and again with a sense that at any moment, you are going to close all and we are just going to be kicked out... Please prove us wrong... Best regards.... 

[n_spired]

Amazon Music API  

Apple Music API

^^^ here you guys go. Maybe you could potentially shift. The only value for me were the track insights like bpm etc anyways which is gone. If you want to stick it to them, it’s time to switch. They don’t write code anyways anymore… support going to get worse. 

[paulnics]

Please go back to this old Dev -> Extended Quota mode structure, the 250 MAU is ridiculous. Also, for me, most importantly, I need the playlists endpoint to provide the track IDs, date added and preferably the popularity for artists as it's critical for playlist analytics tools like mine!! The work arounds are pretty much web scraping the data or using a middle man who is already approved for extended quota and rips me off! (they surely also are breaking your API terms by reselling your info but you are not stopping them...). I don't want to have to do these things and would much prefer to become a business partner!

Please can you at least DELAY THE SWITCH OVER until you are able to provide absolute clarity. It sounds like you are still in business discussions and taking into consideration the developer community response, so why don't you delay the change until you can provide fully decisive and fully detailed documentation. I have read through the API doc changes and there are gaps, meaning it's difficult for developers to adapt their software. I literally had to pay for a second Spotify subscription and get an API key to check what is not available on a new key account as part of my apps risk reduction.

The management/delivery of this change is making it painful for us developers, and without the extended quota endpoints, i'm forced to pivot my app to be focused away from Spotify, so you will get less traffic coming from my app as I scale and put Spotify artists at more risk, as they cannot see on my app up to date bot detection of playlist activity or up to date tracks (so more risk of getting on botted playlists). Without the playlist tracks endpoint, I also cannot offer artist discovery features which you say is one of the approved purposes of the API!

I welcome any direct contact on the matter and i'm very close to applying for developer roles at Spotify (not even joking) so I can come help you guys fix the issues! The moves are harmful to artists who are the ones driving the customers to Spotify, after you already hit them with AI music everywhere (which btw your business are taking way too long to find a solution for). I understand that the business has to make money and keep satisfying shareholders and partners. I am a shareholder also, but the lack of poor decisions recently is leading to a bad reputation and making me and others think twice about our investments.

I have the hope that you developers mean well and the problem solvers, so please keep fighting for our voice to your management! ❤️

Thanks!

[Thajobe]

I'm a PhD student an I just started a small project with some students that I supervice to build an application as an extension to the Spotify ecosystem. The idea was to link smartwatch data (i.e. hear beat) to the live somg beeing played and ideally recommend suitable sonsg based on the physiological data.
A pre-stage of our application was almost ready to be launched in the Google Playstore. Now I think we have to cancel the entire project, especially if the rate limits / daily quota is not adjusted to a reasonable rate, not to speak of all the other restrictions that we already have to work around ...
Is such development (that would be a clear win to the Spotify ecosystem) not wanted anymore?
Can we file for any exceptions for research projects?

I'll probably have to look out for an other music streaming service - it's a shame, I loved to work with Spotify in the past.
Any recommendations for alternative services?

[JoaoAranha]

We are one week to the take down of a huge bunch of apps and still lacking proper documentation and limits... Please or postpone or put the needed to we can keep going. Thx in advance

[Thajobe]

@Spotify can you please re-consider to provide the "external_ids" information (especially the ISRC) for spotify tracks?
I was relying on it to clearly identify and match songs on Spotify. I don't see how this will be possible from now on.
Especially, because sometimes the same track appears multiple times (with different spotify id) on Spotify (e.g. when published as single and as part of an album). The only way to truly uniquely identify the audio (and duplicates of the audio) was the ISRC information.

I don't see how providing this information would do any harm to Spotify or it's users or partners.