Audio Features endpoint returns HTTP 500 for some tracks

johnreutersward — Mon, 29 Jun 2020 10:42:00 GMT

Getting audio features for certain tracks yields a HTTP 500 with an empty body.

Normally, when an ID is invalid or missing a null value is returned in its place.

Input:

7ouMYWpwJ422jRcDASZB7P,invalidId

Response:

{
  "audio_features": [
    {
      "danceability": 0.366,
      "energy": 0.963,
      ...
    },
    null
  ]
}

For some values the whole request fails with HTTP 500 and the response body is empty.

2yOGzJ8xqGyCGa5ML2Vfoq

77tzXLHIK1bBQiS04O0fpX

topic Audio Features endpoint returns HTTP 500 for some tracks in Spotify for Developers