/me/top/tracks returning 400 Bad Request

[leemartindev]

Not sure if it's only me but the /me/top/tracks endpoint started returning 400 "Bad Request" this morning both in my project and on the developer portal console. Any help would be much appreciated.

[oeco]

Having the same problem with all endpoints. I suspect something is down.

[leemartindev]

Cheers Oeco, thanks for the quick reply to confirm it's not just me. 🙏

[votinh8x]

Me too. tried to get track/album/playlist information, and got 400

[24archit]

Yeah, even I am facing the same issue..Please look into this matter asap..Even in the documentaion, if we try out to receive the response, its responding with response code 400..

[sipsy2]

Same here, the search endpoint for example seems to work but not the ones to retrieve specific album or track information. 

[NimrodYizhar]

Yes, At first I thought something got messed up with my code because I'm in a middle of a major change, but then I tried previous app versions, which didn't work either. Then checked some commercial apps using Spotify API and they didn't work too... That brought me here.

[TheDDtMM]

IT DEFINETELY IS NOT JUST YOU!!!!!
I'm having problems with loading playlists (/playlists) and getting users' playlists (me/playlists) and getting artists.

Running searches does not seem to be an issue.

[Elmoesdios]

How can such a fundamental thing go down like this? It's pretty shocking

[barduck]

This is not how a company that values it's developer community behaves.

I understand the service disruptions can happen and it's not always under the company's control but a major API that is used by many developers and serves possibly millions of end users is down for almost 2 hours now, no official announcement of any kind, no ETA, no mention of it anywhere. Shame.

[vituniko]

At least get track/playlist/album is working again now.

[sipsy2]

Seems like it's back up!