Announcements

Help Wizard

Step 1

NEXT STEP

FAQs

Please see below the most popular frequently asked questions.

Loading article...

Loading faqs...

VIEW ALL

Ongoing Issues

Please see below the current ongoing issues which are under investigation.

Loading issue...

Loading ongoing issues...

VIEW ALL

Changes to Web API

Changes to Web API

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. 

Reply
544 Replies

I have been integrating each and every episode of a podcast I manage into a wordpress site using the iframe code like the following:

<iframe src="https://podcasters.spotify.com/pod/show/ show name here /embed/episodes/ episode name here" height="160px" width="100%" frameborder="0" scrolling="no"></iframe>

I have many hundreds of episodes going back to 2014. But now I notice that the iframe integration pops up a cookie notice within the iframe. 

Is there any way of removing that cookie notice? I am only guessing this is in some way related to the recent changes mentioned here.

 

Thanks

Well, I guess I'm just another guy in a long list of disappointed developers and tinkerers. 

 

I created a little web app to make it easier for my family and my children to access certain content on smart speakers.
Spotify is one of my sources and we all use the artist radio quite frequently. Seeing this feature (amongst other) removed, especially in this way, is a huge blow.

 

I get that Spotify want's to protect metadata but there should be a way doing so and not offending all the honest developers.
But seeing the way Spotify handles the community here, I'm left with very little hope.

 

Just to follow up, I have been a Spotify Premium user for 9 years, I've now cancelled my subscription and switched to deezer.com. I was very happy with Spotify but removing curated content from the API was the last straw. !00s of comments and not one response from Spotify either.

Today I received my "Registered for 10 years badge" and have been a premium member all that time.  I evaluated Deezer at the time and it was a close call between the two.

 

I also think it is time to drop Spotify and switch to Deezer.

I wonder if there are js/python/whatever libraries that provide a conversion layer between Spotify and other services? That would make switching very easy and also help Spotify on their quest to commoditise their API (a really dumb move.!)

Just chiming in here to say that I sincerely hope whoever was in charge of this idea never knows happiness again.

I so desperately miss the days of an open internet. It's so over. Everything sucks now. I made a little app for personal use to sort a playlist. It worked so well. Can't get any of that info anymore. So it goes.

Yep, with the recent change, I stopped working on or even thinking about my own apps. In the meantime, if they don’t bring this back, I’ll have to consider working on my own projects elsewhere.

If we really want this to change we are gonna have to be annoying about it.  You can follow Daniel Ek, spotify CEO and wealthiest musician to have ever lived, on X.com and let him know your distaste with this course of activity

x dot com slash eldsjal

This is truly disappointing... I hope the endpoints will come back, even at a charge. Many of us rely on these for work!

Either post a reply or use the PM feature ....

Time to develop for Apple Music. Spotify always limit your projects. Wasting time for nothing.

Late to this discussion since I haven't been doing any development work the past few months. Went back to check my application today and noticed my function calls are erroring out. Came here to find out some very key endpoints were being removed. I have been using the audio features endpoint and think it provided a great amount of detail for my application. As others have stated here, months of work gone. Security is the issue? I am a little confused here since this call is only sending back text. Is the security issue giving out that information? I see it as useful, not a threat. Truly upsetting all of these endpoints are gone. A step backwards. very upsetting.

Are there any alternatives to retrieve this type of information?

Are there any updates on whether this feature will return? I’d really like to continue automatically copying all songs from my weekly recommendations into a separate playlist. I’ve been doing this for a while and I’m still looking for a way to make it work again. Why is this such a challenge?

do you have any information related to "get track's audio features" ? is there any development or change related to it ? 

 

Here are some questions I'd like Spotify to answer:

  1. Will you plan on providing access to audio analysis information or track audio features on a licensed basis in the future?
  2. What kinds of integrations does Spotify envision based on the APIs available?
  3. This one is rhetorical, but I'm sure it's on everyone's mind: why even provide an API if many core features are no longer available? Just shut the whole thing down.
  4. Why do you hate beauty?

"Why do you hate beauty?"

😂 Brilliant

I was trying to build a python script that, after reading the 'loudness' value of a track from the audio-features endpoint, would adjust (somehow) the volume on my Google Cast devices.

You know... because the volume normalization, since day one, is completely broken on Google Cast.

Well, fine! I'll do it myself then... nope! Cause you killed the API endpoint.

You, Spotify devs, just earned the "skill issue" badge! Congrats!

I am a Web API developer whose applications rely on your API. Recently, the disabling of this API has caused key features to malfunction, greatly inconveniencing both me and my users. I understand the complexities of API management, but this change has significantly impacted the user experience. Please re-evaluate this decision and consider restoring the API's functionality.

I know Spotify doesn't care at this point but can you at least put a noticed on the documentation page. I've spent weeks coming up with a web app idea for my final project in CS50 just to make a good bit of progress and realize that my app is dead in the water after three hours of troubleshooting when an api call doesn't work.

Suggested posts

Let's introduce ourselves!

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…

ModeratorStaff / Moderator/ 4 years ago  in Social & Random