topic Get request for multiple tracks audio features in Spotify for Developers

Get request for multiple tracks audio features

thelaughingduck — Mon, 03 Jan 2022 12:19:59 GMT

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?

Re: Get request for multiple tracks audio features

denise26 — Sun, 01 Jan 2023 07:53:50 GMT

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.

Issue accessing audio features of the tracks

gurusaini — Sun, 12 Jan 2025 05:40:16 GMT

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?

Re: Issue accessing audio features of the tracks

LambertSpot — Mon, 13 Jan 2025 07:49:02 GMT

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