Type in your question below and we'll check to see what answers we can find...
Loading article...
Submitting...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
Please see below the most popular frequently asked questions.
Loading article...
Loading faqs...
Please see below the current ongoing issues which are under investigation.
Loading issue...
Loading ongoing issues...
For a few weeks or even months, I'm regularly getting 503 Service Unavailable in my requests. Seems to be mostly when accessing any of the
https://api.spotify.com/v1/me/player endpoints. I think it prominently started after the issues back in September of 2022 when the device endpoint was not working at all for a few days.
Solved! Go to Solution.
Seems like they got their **bleep** together and the issue is far less occurring for me. I had 5 503s within 4 hours on a 1 second request delay.
Wanted to add my voice here. I'm seeing the same.
I've been using the Spotify API in my application for a long time and everything worked fine, unfortunately for three days half of the requests to https://api.spotify.com/v1/me/player end with a response with status code 503 and information { error : { status: 503, message: 'Service unavailable' } }, I also noticed the 502 code a few times.
Unfortunately it's not even limited to this particular endpoint. I've seen it on me/following, too. Tried to get in touch with Spotify on Twitter, but they sent me to developer.spotify.com - which only has a Twitter handle as contact, which can't be messaged...
The support for developers is straight-up garbage. The only way of communication is this "forum". But even then, you barely get any helpful answers.
I managed to work around the problem in this way, it works fine, maybe someone will find it useful if their application is written in JS/TS:
A user of my application has suggested something similar to me, and it seems to be working for him, too. At least you have a maximum retry number - he doesn't... but this kind of retry can cause an additional load on the failing infrastructure, potentially leading to a longer time for recovery as the service might struggle with the higher number of requests. You should add some back-off strategy, too: with each re-try you should increase the delay.
I implemented the same procedure but with at max 5 tries and 1-second delay. But this is not the fix for an obvious issue on Spotify's end.
I am having a similair issue but I am using the
Seems like they got their **bleep** together and the issue is far less occurring for me. I had 5 503s within 4 hours on a 1 second request delay.
Same here. It seems to work as normal now (which means that it only fails rarely now) 🙂
Hey there you, Yeah, you! 😁 Welcome - we're glad you joined the Spotify Community! While you here, let's have a fun game and get…