Changes to Web API

[Loneliest_Cabin]

Folks, some news on changes to the web API has been posted on the Spotify For Developers blog.

We want to reiterate the main message from the blog that we're committed to providing a safe and secure environment for all Spotify stakeholders. As such we have recently made some important changes related to access to some of our endpoints and functionality. You can read the details on the blog: https://developer.spotify.com/blog/2024-11-27-changes-to-the-web-api

We are here to listen to any feedback you may have. 

[schwouber]

How **bleep** you also cut down access to the non curated playlists (e.g. "This is Foo Fighters") through the API? I did not plan to do anything with this content besides playing them on Sonos (using the API) but now I cannot even find them using the search (these items now show up as "null"). wth?

[Karnay]

I just created an app relying on the api calls for track analysis and track features!
Can you bring it please back? A lot of developers who used it a disappointed and angry! Doing it this way is like the worst thing!
Also it is so bad that the error response calling this api is not even telling you any of this! I am so mad right now, i just finished my app and wanted to show it to a colleague and now nothing works anymore!

[Rendereduseless]

I want to add my voice to this thread and express my support for everyone here. These endpoints have been vital to many of our projects, and their removal has disrupted a lot of hard work and innovative applications that rely on Spotify’s API.

While I understand Spotify’s need to maintain security and manage platform resources, I’d like to plead for the restoration of these endpoints, even if under more restrictive access terms. Perhaps implementing stricter API rate limits, requiring additional scopes or permissions, or introducing usage tiers could strike a balance between platform protection and supporting developers who contribute to the Spotify ecosystem.

The developer community has consistently shown how these tools can enhance the Spotify experience for users in creative and meaningful ways. By restoring access to these endpoints, Spotify would empower developers to continue innovating and delivering value to Spotify users. Thank you for considering this feedback and for your ongoing engagement with the developer community.

[hjdeheer]

Is there some replacement for the 30-second previews? My application relies a lot on this functionality, and it completely stopped working right now. You cannot suddenly remove this... this is unacceptable.

|

Update (contacted support):

Hello there! Camsey here. Nice to meet you. I'm here to assist you with your issue today. Kindly give me a few minutes to review the details you've sent, I'd be glad to help.
Camsey at 03:41 PM, Nov 28

Hi. Yesterday you deprecated the SPotify Web API. https://developer.spotify.com/blog/2024-11-27-changes-to-the-web-api
You at 03:41 PM, Nov 28

Without any warning... now my app that uses the 30 second previews does not work anymore. Is there some replacement available
You at 03:42 PM, Nov 28

Thanks for waiting! I understand your concern. No worries, we will figure this out. Just give me a couple of minutes while I review your account.
Camsey at 03:44 PM, Nov 28

Ok
You at 03:46 PM, Nov 28

I've checked, and there's some exciting news about Web IPI! The updates are impressive, and the innovation is amazing. Stay tuned to this page for updates in the next few days!
Camsey at 03:49 PM, Nov 28

What?
You at 03:49 PM, Nov 28

You just removed functionalities, so that all type of applications do not work anymore. Do you expect replacements for this
You at 03:50 PM, Nov 28

https://community.spotify.com/t5/Spotify-for-Developers/Changes-to-Web-API/td-p/6540414
You at 03:50 PM, Nov 28

80+ people are already complaining under 24 hours
You at 03:50 PM, Nov 28

What I meant is that in the next few days, a replacement is coming, and there's an exciting innovation that customers like you will enjoy. I understand this is happening a bit early without prior updates.
Camsey at 03:52 PM, Nov 28

Ok, so the functionality will be replaced?
You at 03:53 PM, Nov 28

Ok great
You at 03:54 PM, Nov 28

That's correct! No worries about that.
Camsey at 03:54 PM, Nov 28

It is a bit strange though, that you completely deprecate the old functionality. Can't you give us access to the deprecated functionalities a bit longer, so that we have time to refactor to the new ones when they release?
You at 03:55 PM, Nov 28

Isn't that a way smoother operation?
You at 03:55 PM, Nov 28

Since the development team is handling the changes, I'll reach out to them right away to address your request immediately.
Camsey at 03:57 PM, Nov 28

Yes please
You at 03:57 PM, Nov 28

I think I speak for 100+ people
You at 03:57 PM, Nov 28

Right now, you can join the forum here: https://community.spotify.com/t5/Spotify-for-Developers/Changes-to-Web-API/td-p/6540414. This way, the development team will see that many users are affected by these changes. Since the replacement is coming soon, it makes sense to extend the functionality, don't you think?
Camsey at 04:00 PM, Nov 28

I already did
You at 04:00 PM, Nov 28

Great! Give me a minute or two to get in touch with the development team. Hang on a bit.

Same issue here, it seems like they intentionally deprecated it after they removed a lot of features on 27th November 2024. https://community.spotify.com/t5/Spotify-for-Developers/Changes-to-Web-API/td-p/6540414.

Done! I hope that I helped you with your concern today. Do you need anything beside this though?

Camsey at 04:03 PM, Nov 28

No I hope this gets resolved quickly. Since my clients depend on it.

[musicD4RKH3LM3T]

Any notice prior to this change, or more what you would call "secure" workaround or access to this data would have been helpful. Your entire platform is built off of playlist creation, where recommendations are vital. You are turning away great developers in an ugly way by limiting creativity and great ideas that would bring more users to spotify. These devs will now turn to Apple Music, Amazon and other streaming providers who will be more than happy to enable great devs to use their data to create outstanding work. Just an absolute joke to, literally overnight, break so many devs appllications. Be better.

[Nyko_Dev]

I was working since several weeks on an app to help people to generate Playlist on Spotify ONLY...

The endpoint "recommendations" was my key component.
I don't know what to say, really surprised and disappointed to see it's deprecated overnight.

That's a project with multiple purposes:

• I'm about to start as freelance so it's a proof of my developing knowledge
• Creation of real use case which is not present on our app whereas it should be.

What can I do now?

1. I can try to generate playlist with less diversification and less qualitative on and for Spotify
   try on another platform 😞
2. What do you suggest me ?

[Nyko_Dev]

Same for me, it drives me crazy..

[robpolachek]

@Loneliest_Cabin

I have been developing an app for the past several months that relies heavily on a few of the deprecated APIs (Audio Features, Audio Analysis). I was planning to migrate out of development mode next week, which apparently would have allowed me to continue using these APIs. If I had been notified of the planned deprecation by Spotify, would have filed before the deadline. Is there any way to allow existing in-progress applications that leverage these APIs to retain access. Can I please file my extension today or tomorrow?

I respect wanting to provide a safe and secure environment for all Spotify stakeholders, but I don't see how suddenly yanking access to features that don't provide user-specific information and also cutting down your app ecosystem benefits that.

Thanks for listening, please figure out a means to let those of us that are relying on the now-restricted APIs to maintain access so we can complete and release our apps.

[aris2504]

This is extremely disappointing. For a while I've been working on a small app that leveraged the recommendations API (not training or using AI models) and this has rendered it completely non-functional and resulted in countless hours wasted. Very upset.

[greedymau5]

Half of the endpoints in my app are now deprecated. Great!!! I have been working on this for two months now.
At this point, I don't think I'll be continuing with Spotify anymore. 
Thinking of creating my app through Apple MusicKit. 

A little heads-up about these changes would've been nice.

[Mordicus]

Well, I for one will be continuing my dev projects using ListenBrainz APIs, they're much more developer friendly.
https://blog.metabrainz.org/2024/11/28/**bleep**-off-by-spotify-enshittifying-more-api-endpoints-we-...

[DouglasAdams]

Why not give your developer community any advance notice about this change? I have a study in a clinic trial depending on the recommendation feature that is now completely dead in the water. Deprecating APIs without warning is basically unheard of from companies of this scale. Even Reddit gave app developers months of notice before offering paid access to APIs that apps depended on.

The app review process takes months, there's no opportunity for apps that would need this feature to apply, cutting it off at its knees hurts the community. At least give apps that were in flight a chance to apply for long term support, or a chance to pay for it. This rug-pull on a major American holiday just sucks.

[DouglasAdams]

I saw a post in this thread about new replacement APIs coming soon. Why not include those details in this message? This order just feels backwards, why not release the new APIs and provide your community time to migrate? If you want to gate access, why not charge a fee? Why not grandfather in apps already under development if they submit for review?

This feels intentionally alienating to do before a holiday weekend with no alternatives.

[spo-api-devastated]

Could you please allow us to use it under more restrictive terms / paid conditions? At least some notice would do so that we are prepared - overnight, you have destroyed many plans, dreams, and jobs with this move.

[bvermeulen]

Why? Will it come back in a paid form? Some explanation please...

[robpolachek]

UPDATE: I am in chat with Spotify support. They say they do not have any information about whether these APIs will be replaced but that "you can still submit your extension application within this week, best that you submit it today so that our team can review your request"

Hopefully this is accurate information, I will provide additional details if any emerge.

[DouglasAdams]

@robpolacheck - How did you contact them? I tried their support chat and the representative didn't seem to have any information and escalated me to another tier of support that would e-mail me based on my message above.

I hope the rumors about the new replacement capabilities and your latest note are true. Unfortunately, I'm still going to have to spend this while weekend working on an alternative in case that doesn't come true.

[trevbook]

Just chiming in to say: this is a pretty disappointing change. It feels pretty unfortunate that this was announced without any notice. I've had a multitude of ideas for a while about ways to use these endpoints, and it's pretty sad that I won't be able to realize them. 

[DubbayouDJ]

@hjdeheer… Appreciate you investigating w/ Spotify Support and sharing that convo. SILVER LINING:

Camsey [Spotify Support] at 03:52 PM, Nov 28:

“[…] in the next few days, a replacement is coming, and there's an exciting innovation that customers like you will enjoy.”

Personally, I'll forgive the inept transition (i.e., pulling the plug w/out any warning or reference to future replacement), IF… the replacement is actually "an exciting innovation". 🧐

[Vegas303]

This is a terrible update that makes the API basically useless. Multiple projects that I have been exploring are now useless without endpoint access. Please revert these changes for the sake of ongoing innovation.