Type in your question below and we'll check to see what answers we can find...
Loading article...
Submitting...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
Please see below the most popular frequently asked questions.
Loading article...
Loading faqs...
Please see below the current ongoing issues which are under investigation.
Loading issue...
Loading ongoing issues...
Hello Spotify Team,
I am currently working on a project to catalog my vinyl collection along with additional song information.
I recently learned that the audio-features/{id} endpoint has been deprecated. Could this be the reason why it is returning a 403 error?
Is there an alternative way to access information about audio features?
Thank you for your assistance!
This endpoint is returning 403 because it is deprecated. Only apps that had a (pending) quota extension before November 27, 2024 can still use it. You can read more about it at this news article.
@Ximzend thanks for your answer!
The article mentions security reasons—do you know if there will be an alternative endpoint to access the audio feature information? Or do you know of any other API that could provide this information? I found a webpage built on top of the Spotify API where I could extract the BPM number and keys, but it feels a bit hacky to scrape a webpage for that info. I would prefer to work directly with an API...
If you know something or an alternative that would be great!
Hello, I'm trying to use the Track Audio Analysis endpoint "https://api.spotify.com/v1/audio-analysis/{TRACK_ID}" but it always returns 403 code with response data: "{"error":{"status":403}}".
I used the Client Credentials flow to authenticate my application (I guess this auth method is enough since I'm not trying to retrieve user-related data).
I tested the same credentials with other endpoints like "https://api.spotify.com/v1/search" and it works flawlessly.
Can anybody help me?
Plan
Free
Country
IT
Device
local machine ATM (server-to-server connection)
Operating System
---
My Question or Issue
I'm going to move every new 403 error here.
And I don't know any service that offers the same features.
Hi ne_lea,
I am working on the same thing, I only need the BPM though. Did you find a suitable solution? Would you help me out? Good ideas, how to get in contact? And to Spotify: is there any plan, to bring these features back? At least some of them? Your API was very powerful, it is very sad you decided to shut it down like that.
Kind regards!
Hi Team,
I am working on track feature but whenever i am requesting to
Hey @Darius-IX,
I haven't had time to continue to work on my app. I have found this site with API: getsongbpm.com . I just checked and it seems to have loading issues. Nevertheless one can get an API key there and I would hope that this gives me the needed information.
Cool that you are also working on a Vinyl app, would be great to connect and exchange ideas.
Cheers
Nele
There are no alternative endpoints available from Spotify. This has been intentionally broken and will not be fixed.
Spotify realised this was valuable data and they shut it down rather than continue to provide it and support their community of devs. It has nothing to do with security concerns, it's monetary concerns. Their API is no longer any better than competitors, there is no reason to build an app around Spotify unless you enjoy having your hard work broken on their whim. You have been warned.
Yeah this decision absolutely stinks.
Deprecating the audio-features (and other useful) endpoint(s) without giving us a solid alternative is a slap in the face to all the devs who’ve been building with your API. Citing "security reasons" feels like a weak excuse, as kingosticks4 points out - there is clearly a financial imperative that they're not addressing.
This move is crushing for those of us who’ve invested time and effort into projects that rely on this data. It’s like Spotify doesn’t care about the community that’s helped make it stand out. Without these features, what’s the point of building on Spotify? We’re left with broken apps and zero support.
Spotify, it’s time to step up and actually support the devs who’ve been championing your platform. Give us back the tools we need or at least offer something that doesn’t leave us high and dry.
Hi! My app has a granted quota extension before November 2024, why am I receiving a 403 error on this endpoint?
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…