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
534 Replies

Do you see further changes? I'm getting 404s on my own playlists now.


@keibak wrote:

Do you see further changes? I'm getting 404s on my own playlists now.


It seems like this issue is specifically affecting newly created playlists. Existing playlists appear to still work fine with the Web API. This could indicate a recent change or restriction implemented on Spotify's side.

It’s hard to say definitively whether this is intentional (e.g., a new policy or feature rollout) or a bug.

 

Update: My bad: Playlist was made for me, and not created by me.

I'm trying to build a html scraper with Selenium that scrapes the trackid's from a playlist webpage. But I'm having trouble auto-scrolling to the bottom of the page.

If it any easier to scrape a playlist widget?

I spent 5 years backing up my Discover Weekly into a yearly playlist, merged them all recently, **bleep** went through two system changes to do this (IFTTT, then N8N), I even started doing it with Daylist, so I could better understand my music habits over time. To just up and kill these endpoints, I know Spotify are the champions of enshittification, but this poorly thought out choice is pathetic, you have 22 pages of backlash on this!! Roll the change back, make your platform not actually just a representation of how **bleep** users and developers off

Please do open the 'WebAPI-Get Track's Audio Features/Analysis'api to my android apk.
I'm doing a philips hue syncing with spotify Audio Analysis beats.
I did another way diferent with philips hue's app, and my apk will make Spotify more intracting.
Spotify User ID <snip-moderator edit>, Username <snip-moderator edit>
6 years ago, i made a philips hue apk that sync the beat of local music, it's pretty good,
then i go back working, as i need overwork most of the career time, i missed upgrade keeping pace with the android updating,
and the apk is kicked out market.
Now i lost my job, as is hard to find new job if you are above 40 years old and my age is 55,
so i decided to rework on philips hue apk first, so i worked on hue syncing local music syncing for some
time, i found it's more easy to successs if i focus on philips hue syncing with Spotify, and i started
to work on spotify, after 2 weeks, when i'm debug 'WebAPI-Get Track's Audio Analysis', i found it is closed to apk undering
deveoping.
The local music syncing with philips hue is pretty good, if ported to spotify, with spotify's Track's Audio Analysis beats info,
it will be even more better.
please refer to following videos
it it can not play, please retry one or more times:
https://pan.baidu.com/s/1RoelgIToExaa1xnC4-V5Bg?pwd=eyh2 
https://pan.baidu.com/s/1VIUL7Q30bVqllOOKN0tgQw?pwd=taqj 
https://pan.baidu.com/s/1QqeV3R8ClcqNP1r8FTAYTg?pwd=tpi6 
https://pan.baidu.com/s/13No2lefilOY-W29EXwg_5w?pwd=kfax 
Thanks

Hope it worked out Binc.

FYI, scraping the website is against the Spotify User Guidelines point 5. Although it does seem like the only option to retrieve information about Made for You playlists.

https://www.spotify.com/us/legal/user-guidelines/

Sue me

That would be an eventuality to take into consideration if your thing ever get big enough to fall under their radar.


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

Meanwhile, two months later, NOT A SINGLE REPLY from anyone at Spotify. Just goes to show how much they care about their paying customers.

no way they took my lastfm away 

I maintain one of the largest Spotify API client libraries. I've added information to make developers aware of Spotify's practices, which, as apparent from this thread, may discourage developers from interacting with Spotify.

 

I'm sure this outcome was considered in Spotify's risk assessment when deciding to remove API functionality without prior notice. To achieve their goals with the developer community, I see improvements in their overall communication style as indispensable.

Boo. I really enjoyed my little app that would let me jam to the key of a now playing track. Does anyone know if any other app lets you query the key of a song, now that Spotify is dead?

While posting about the fixed Last.fm playlist export to Spotify today, I noticed that the import of Spotify created playlists like Discover Weekly and Release Radar does not work anymore ("playlist not found" is the shown error) which was possible in the past and a handy method to back them up. I guess this has been caused by the November changes to the API, but wonder why Last.fm would be considered a private or new user in this case.

Well this is unfortunate...  I was building a personal app using some of the now deprecated features (get audio track features, in particular). Came back after the holidays and my project is basically useless now.

 

I do greatly appreciate that they were ever available in the first place, but this change has made me very sad. I understand why the change was implemented, but my project has nothing to do with AI in any capacity and does not use it. Considering it's already against the developer TOS to do so, I wish there was some way of restoring that functionality for the developers who were using it legitimately. If I had known the change was coming, I would've applied for extended mode much sooner.

 

Anyway, thank you for having it while it lasted, rip to those of us affected :'(

I have been working on an app for several years and recently did some updates to it where I was using the endpoint for related-artists. I was so thrilled when I made it work and so pleased to use it, until the endpoint got deprecated and my app became practically useless since the function retrieving related artists was the most used functionality of my app. I hope the endpoint will be available in a near future. Thanks!

My app im developing solely relied on spotify's ability to provide BPM/Tempos for a song. I thought it was annoying to see the recommendations endpoint gone, but it was still manageable to make my own recommendations; now without the tempo, my app is rendered useless for my spotify integration. 

will likely be leaving the spotify api ecosystem because of this. imo this was a terrible update for the spotify-for-developers team to have done. 

i agree, this was one of the main points i stuck with Spotify loved their API, now thats no longer the case might as well switch over

What would be nice, is to allow it with very high rate limitaitons, such that the restricted features can only be used for developers and by developers such that they cant deploy it or share the API keys easily. This will allow developers to continiue making their own apps just for them selves and stopping competition from growing for Spotify. 

Suggested posts

Type a product name