topic Failed audio_features in Spotify for Developers

Failed audio_features

anadelgars — Sun, 21 Sep 2025 18:06:43 GMT

Plan

Premium

Country

Spain

Device

Windows computer

Operating System

Windows 11

My Question or Issue

All calls to GET /v1/audio-features return 403 Forbidden even with valid Authorization Code Flow tokens.

Re: Failed audio_features

Ximzend — Sun, 21 Sep 2025 18:28:24 GMT

Hi @anadelgars

Thanks for reaching out.

That endpoint has been deprecated, meaning this can't be used by apps anymore.

Note: some old apps may still be able to use this endpoint.

I hope this clears things up.

Re: Failed audio_features

anadelgars — Mon, 22 Sep 2025 09:49:56 GMT

Is there an alternative to obtain audio_features then?

Re: Failed audio_features

anadelgars — Mon, 22 Sep 2025 09:50:42 GMT

Is there an alternative to obtain audio_features then?

Re: Failed audio_features

arthurab — Wed, 24 Sep 2025 03:54:59 GMT

@anadelgars have a look at this thread and vote!

https://community.spotify.com/t5/Spotify-for-Developers/Bring-back-audio-features/m-p/7145019#M18834

Re: Failed audio_features

radwan_almsora — Sun, 10 May 2026 02:32:34 GMT

Hi there,

The 403 Forbidden error you are encountering with the audio-features endpoint is not a token issue. It is a result of Spotify's API changes that have restricted this data for many developers.

Here is what is happening:

Deprecation: Since the recent updates, access to Audio Features (like energy or danceability) is now limited to specific approved applications.

App Tier: Even with a valid Authorization Code Flow, if your Client ID is not in the approved tier for audio analysis, the API will return a 403.

What you can do:

Check your Developer Dashboard to see if there are any specific restrictions on your App.

If your app depends on this, you may need to apply for an Extended Quota, although these are rarely granted for acoustic metadata recently.

Use the GET /v1/tracks endpoint for basic metadata, though it won't include the granular audio features.