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. 

[eeeh]

I am going to fail my final project because of this...

[keibak]

I have to say, I’m deeply disappointed by these changes. The Spotify Web API has been a cornerstone for so many developers and creators in building innovative applications and integrations. These recent updates, however, feel like they’re prioritizing Spotify’s interests at the expense of the developer community.

What’s particularly frustrating is that these changes render my current app in development completely unusable. I’ve invested a significant amount of time and effort into building something that enhances the Spotify experience for users, and now it feels like all of that work was for nothing. The reduction in accessible endpoints and the stricter rate limits are a huge setback, making it nearly impossible to create meaningful applications without major redesigns or compromises.

I understand that businesses need to evolve and protect their platforms, but there has to be a better balance. Developers have been some of Spotify’s most passionate advocates, and decisions like this make it harder to feel like we’re valued. I really hope Spotify reconsiders or at least provides more transparency and reasoning behind these changes.

[bener]

Anyone has an email to contact Spotify? I can not find one. I am trying to apply for extension (if possible), because my thesis is due in 1 month, and this change is almost 'killed' the whole project.

[thesystemera]

So I'm looking at all options here. The situation that I just can't find a work around for is audio analytics, specifically dB readings through out the track. Our app works like a radio station and needs to know when an artist has finished singing essentially so our DJs can come in at the appropriate time. I care very little for the tempo and things like that, though useful, not critical. I've showered the internet for free or even paid options and have had no luck.. Would run the analytics ourselves but to the best of my knowledge DRM stops this from being an option. I really don't like this new internet. Its getting extremely evil. Project is actually based on my original 2010 thesis, when TheEchoNest was a thing. FARK this new world. Honestly! I mean, how are you even meant to run a web based visualiser these days! This is insane!

[kisLimpa]

Hi, I have been working on my graduation project for half a year now, which integrated the recommendations API. The deadline for handing it in is tomorrow. I can not fathom what kind of business practice would find it a good idea, to shut down several highly used APIs without prior notice. At least if you notified developers using your API, we could have switched to something else in time.

If I fail or have any negative repercussions because of this change, I am cancelling my premium subscription permanently.

Sincerely,

A student you have possibly ruined

[giuseppevincenzo]

Not sure if anyone has mentioned this already, but some playlists created by Spotify can't be queried with the API anymore. See for instance this playlist: https://open.spotify.com/playlist/37i9dQZF1DX3wF1YbAXxkA and try its id here https://developer.spotify.com/documentation/web-api/reference/get-playlist . Same thing for other playlists like "Hot hits UK", "Fresh finds indie", etc. They all share they same pattern, made by Spotify. Anyone could query them via API before November 27th

[michiinya]

Pretty much all of the work I did for a college project I have due in next month is gone as I used most of these endpoints. Time to switch to SoundCloud I guess..

[alberto_trobia]

This is an authentic tragedy for me! I'm a popular music studies researcher. I've been working for months on a sociological project that uses the get track audio features. This means the end of the project for me and my co-reserachers. I strongly suggest to allow for an academic permission to use the data or some kind of subscription for a limited number of songs. This could discourage the massive use of data for the training of IA model (if this is the problem) and allow academic research on music to go on. I hope this solutions could give us back the get track audio features instruction.

[81tay3]

I totally agree with you.

[aconlin]

I understand that a service needs to change things up on occasion, but I also feel like this could've been handled much better.

+ Advance notice, ideally an email to the developer accounts that would be effected.

+ Not turning things off the day before a major holiday in the US, one that coincides with a notorious bombarding of emails into people's inboxes (not just in the US). I mostly ignored my email for a couple days not only because of the holiday but also because I didn't want to deal with the swarm of black friday emails. As a result, I missed my the emails I've programmed to inform me that my project is broken. Obviously this part is on me, and if this were a production system or a public app, I would've needed better notifications. Still, I think the timing of this could've been more gracefully handled.

I LOVE that spotify has provided audio features and analysis for so long. I can understand if Spotify may not want to give out this information anymore, but I can't help but be sad that it may no longer be available. It's frustrating too since my app has always been in development mode as it's an app that has 

"...been built for accessing or managing data in a single Spotify account."

https://developer.spotify.com/documentation/web-api/concepts/quota-modes

Now, even though it has successfully been using these endpoints for 4 years, it's not grandfathered into the grace usage you're leaving in place. (If someone from Spotify reads this, please let me know if there is a way I can still somehow get "extended mode Web API access" for an app in my situation.)

Besides not having access to audio features, my script is now failing when trying to do something as seemingly benign as getting the name of certain playlists (playlists that I imagine are part of the post's "Algorithmic and Spotify-owned editorial playlists"). My particular use case involves a user's recently played tracks which include a context item (album, artist, playlist, etc.). The context item provides the type, but an additional call is necessary for getting the name. (To be fair, I'm still debugging, so there may be an additional way to just get the name related to a spotify URI another way.)\

The initial post says "we're committed to providing a safe and secure environment for all Spotify stakeholders." I would argue that developers are absolutely spotify stakeholders. Indeed, I've been a spotify evangelist. I don't think this was handled in a safe and secure way for developers or the users or their legitimate apps.

[kingosticks4]

You used to be able to search for URIs to get some metadata for them. They did overhaul (break) a load of search features not that long ago, not sure if this one survived that round of 'improvement'.

[aconlin]

Additional context for the decision makers at spotify:

I just looked in my email archive and found that I started using spotify May 9, 2012. About a year later on Jun 3, 2013 I started a 30-day premium trial and began paying the next month. iirc, I've never not been a subscriber since then. And happily so! Even as a substantial Apple fan who even recently got access to apple music thanks to a combo plan with apple tv, I still haven't wanted to move away from Spotify. This API access/my listening history/scrobble-ability has been a significant part of that.

I understand that you need to prevent your API from being abused, and at any rate you have the option to offer your service as you see fit, but know that the way this was handled has a long-time user actively seeking out alternatives. If there had been notice given, I would've been sad but modified my code and carried on.

I know that one paying user potentially moving away is hardly going to move the needle, but this is something I can do.

[ua-projects]

I've been working on my app leveraging the audio features endpoint for some months. I started working today to find I was getting a 403 error and discovered the endpoint was deprecated. It's very disappointing to learn of a major change this way, without warning. It shows a disregard for the developer community and has drastically reduced my confidence in the Spotify API or desire to build using it in the future. At the very least can you allow an extended period to submit extension requests?

[drunkenberger]

Sorry to hear that. Something very similar happened to me!! it's very disappointing. We´ve been developing tools based on metrics obtained from playlists and audio features to help Independent artists market their music and now almost none of our tools work. Amazing how they **bleep** us!

[samr8]

I don't even know why they allow comments on these posts. They never read them or reply. I think spotify must have some of the worst PMs in the business if they even have any lol

[kingosticks4]

I think you raise a good point, there is zero value anymore of developers using this forum. The limited Spotify presence there once was has gone. It makes more sense for discussions (including unsanctioned workarounds) to be had elsewhere, on a forum that's not moderated by Spotify.

[name_1]

I've cancelled Spotify in the past over boneheaded decisions like this. Looks like I'll be cancelling again.
Screw the executive who came up with this.

[NetflixAndBurn_]

Yes I use the 30s preview urls daily for discovering music, so this is incredibly disappointing. I don't know of any replacement.

[tarsinzer]

I'm not about to retell all my "hard way" stories now.

I'm just speechless and deeply sad.

Such a disappointment, Spotify.

[levvvski]

Three years were wasted working on the app and going through two extension request denials while other existing apps had similar usage. Lesson learned: do not rely on any third-party API to build your app; shame on you Spotify! 🖕