Web API — /v1/audio-features returns 403 for all requests (other endpoints OK)

[PeterLeach]

Plan

Premium

Country

Italy

Device

Mac mini M2pro

Operating System

Sonoma 14.2

My Question or Issue

Context
- Timestamp: 22 Aug 2025 ~09:35 CEST (UTC+2)
- App: new app (client_id ends with: ...dbd919)
- Environment: Python 3.12 (Homebrew), Spotipy 2.25.1, macOS, no proxy/VPN
- Scope/token: both client-credentials and user OAuth tested

Issue
- All calls to GET /v1/audio-features/{track_id} return 403.
- Meanwhile GET /v1/tracks/{track_id} returns 200 with the same token.

Evidence

1) curl with fresh client-credentials token:
$ curl -i -H "Authorization: Bearer <token>" \
https://api.spotify.com/v1/audio-features/7pKfPomDEeI4TPT6EOYjn9

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

2) curl with same token on tracks endpoint:
$ curl -i -H "Authorization: Bearer <token>" \
https://api.spotify.com/v1/tracks/7pKfPomDEeI4TPT6EOYjn9

Response:
HTTP/2 200
{ ... JSON with album/artist info ... }

What we’ve tried
- New app (new client_id/secret)
- User OAuth flow OK (me endpoint works)
- Different network (hotspot)
- Spotipy vs raw requests
=> Always 403 on /audio-features; other endpoints OK.

Question
- Is /audio-features restricted for new apps? If so, what is the current process to request access (quota extension or similar), and where is the official policy documented?

Thanks!

[Ximzend]

Hi @PeterLeach 

I understand this might be disappointing. The documentation confirms that this endpoint has been deprecated, which means it can’t be used by new apps anymore. Unfortunately, there isn’t a way to access it.

I know this isn’t the answer you were hoping for, but I wanted to be as clear as possible so you don’t lose time trying to make it work.

Take care, and feel free to reach out if you have any other questions.

[bhuvaneshpatil80642]

I am also trying to use the same endpoint, but I get the error 403. But with make.com spoitfy module I can access it. Not sure how it's working there

[Shreyesh_Singh]

can