topic Re: Getting a 502 bad gateway when trying to read /me/tracks in Spotify for Developers

Getting a 502 bad gateway when trying to read /me/tracks

derwish — Tue, 14 Dec 2021 19:10:17 GMT

Plan

Premium

Country

Belarus

Device

Operating System

Windows 10

My Question or Issue

Description:
I have about 135,000 saved tracks in my library and I can't get a list of them.
Everything worked until there were not many saved tracks.
I can see the list of tracks in the desktop app. But the list is not displayed in the web player. After a long wait, it tells me that the playlist was not found.
Also, I cannot get the list using API Console (/me/tracks). I get the "502 Bad Gateway Error" in response.

Try to get /me/tracks for my user_id.

Endpoint(s):

GET /v1/me/tracks

Scope(s):

user-library-read

Steps to reproduce:
- Add 135,000 saved tracks
- Open the API Console
- Call the Get Current User's Saved Tracks endpoint /me/tracks

Expected behaviour:

Some data

Actual behaviour:

502 Bad Gateway Error

Re: Getting a 502 bad gateway when trying to read /me/tracks

spotifyjosh — Thu, 16 Dec 2021 07:34:52 GMT

What an impressive music collection, @derwish!

Are you seeing the 502 error response from every request that you make to /me/tracks? Or does the request succeed some of the time for you?

Re: Getting a 502 bad gateway when trying to read /me/tracks

derwish — Thu, 16 Dec 2021 12:22:00 GMT

This happens on every request. The list of my tracks is never available either through the api or in the web player.

Re: Getting a 502 bad gateway when trying to read /me/tracks

scottonspot — Sat, 05 Mar 2022 15:12:07 GMT

I am having this same problem. I can get my user info from /me, but /me/tracks consistently gives 502 errors.

Re: Getting a 502 bad gateway when trying to read /me/tracks

scottonspot — Sat, 05 Mar 2022 15:31:09 GMT

@spotifyjosh I tested the other /me endpoints and they all work except for /me/tracks and /me/albums, which both consistently return 502: Bad gateway.

Re: Getting a 502 bad gateway when trying to read /me/tracks

scottonspot — Sun, 06 Mar 2022 16:09:22 GMT

The 502 error occurs even in the Spotify Developer console

Re: Getting a 502 bad gateway when trying to read /me/tracks

Soch — Tue, 04 Feb 2025 16:19:19 GMT

Did you manage to solve this?

I'm having the same issue with my app, it works well for every user, except for one that has 19k saved tracks. Seems like the API returns a 502 when there are too many tracks.

Perhaps with an offset it works?

Re: Getting a 502 bad gateway when trying to read /me/tracks

scottonspot — Thu, 06 Feb 2025 00:46:01 GMT

Last time I tried I had the same problem. I don’t think adding an offset changes anything; that /tracks endpoint just always fails. Very annoying.

Re: Getting a 502 bad gateway when trying to read /me/tracks

flyflyfly — Sat, 23 Aug 2025 21:01:03 GMT

I'm getting 502 errors about 15-20% of the time with the /me/tracks endpoint. Super annoying - especially given the relatively small maximum limit of 50 tracks. Used to think the spotify API was a stellar example of goodness. With the elimination of being able to get my Spotify created playlists (which I have seen no formal explanation for) and repeated 502 errors - especially on my liked tracks (about 40K), and API errors my Tesla has fought with (and are a result of Spotify errors) I've changed to seeing it an example of how not to do end user APIs. I've paid a premium for Spotify - and the API access was a big driver in that - but I'm nearing the end of it being worth what I pay. Apple's Music API hasn't let me down yet. Just sayin'... And so no one at Spotify is surprised where long time evangelists and fans are heading...