403 Forbidden on /v1/audio-features using both user and client credentials tokens

[pokokincso]

Hi everyone,

I'm developing a Spotify Web API integration and consistently receive 403 Forbidden responses from the /v1/audio-features endpoint.

What I tested:
– User access token (with user-top-read etc.): 403
– Client credentials token (no scopes): 403
– Reproduced outside my app via PowerShell / cURL (no proxy)
– Other endpoints work fine: /v1/me/top/artists, /v1/me/top/tracks (200 OK)

Example request:
GET https://api.spotify.com/v1/audio-features/1BxfuPKGuaTgP7aM0Bbdwr
Authorization: Bearer <app_token>

Response:
HTTP/1.1 403
{ "error": { "status": 403 } }

Could someone from the Spotify team confirm whether the /v1/audio-features endpoint currently has access restrictions for certain apps or regions? Other developers seem to be running into similar issues lately, so I’d just like to verify if this is an account or app-level policy limitation.

Thanks in advance!

[Ximzend · Accepted solution]

Hi @pokokincso 

Thank you for posting in the Spotify Community!

I'm here to inform you that the Audio Features endpoint is deprecated and cannot be used anymore by new apps that had no quota extension before the depression.

I hope this clears things up.

[thlucas]

 wish they would bring these endpoints back, as they are super helpful in Home Automation packages (e.g. Home Assistant, etc).

[sunsetandhigh]

This was super lame on Spotify's part to remove Audio Features functionality from the API.
I just want to build a small personal app that can get the tempo and key for songs in my playlists.
You should be adding API features not removing them.  Lyrics too.