Announcements

Help Wizard

Step 1

NEXT STEP

FAQs

Please see below the most popular frequently asked questions.

Loading article...

Loading faqs...

VIEW ALL

Ongoing Issues

Please see below the current ongoing issues which are under investigation.

Loading issue...

Loading ongoing issues...

VIEW ALL

Get request for multiple tracks audio features

Get request for multiple tracks audio features

My Question or Issue

Hi!

 

I'm trying to get the audio features for multiple tracks, but can't get the request right.

I've looked through the documentation for getting multiple tracks, as well as the similar documentation for getting a single track. According to the documentation, the query that I'm trying looks like

 

https://api.spotify.com/v1/audio-features/id1,id2

 

But it won't work, and returns the error 400: Bad Request. Any idea what I'm doing wrong?

Reply
3 Replies

It works with https://api.spotify.com/v1/audio-features?ids=id1%2Cid2, so there are two changes: replace the last / with ?ids= and replace each comma with %2C.

Plan

Premium

Country

USA

 

 

My Question or Issue

I am working on a Reinforcement Learning project where I need to access the audio features of tracks using Spotify’s Web API. While attempting to call the /v1/audio-features endpoint, I have encountered a persistent 403 Forbidden error, even with a valid access token. This issue occurs for globally recognized tracks such as Billie Jean (Track ID: 3n3Ppam7vgaVa1iaRUc9Lp). My access token successfully works for other endpoints like /v1/me, confirming its validity. The error response returned by the API includes status: 403 with minimal details. Here are the headers from the failed request: content-type: application/json; charset=utf-8, cache-control: private, max-age=0, and other standard CORS headers. I am using a Spotify Premium account (family with me as the primary) and am currently based in the US. Could you please help identify why this endpoint is inaccessible and provide guidance on resolving the issue?

This is due to the recent changes in Web API, see point 3.

Suggested posts