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...
My Question or Issue
Since the major Web API update, basic track metadata such as BPM/Tempo, Key, and Scale remains inaccessible. While I understand the importance of prioritizing security and data control, these particular attributes seem fundamental and non-sensitive. The popularity metadata is already included, so extending access to these basic musical properties would align with user needs without compromising security.
Such metadata is essential for developers and creators who work with Spotify's ecosystem. I’m not requesting access to advanced audio features API data but rather the inclusion of these basic attributes in the Web API. Could the Spotify team consider providing these features or at least address the rationale behind their exclusion in a blog update? It’s worth noting that this data isn’t confidential; building an API wrapper to include it would be feasible but unnecessary if Spotify included it officially.
Thank you for considering this suggestion!