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...
The new "Get the User's Queue" endpoint is pretty neat: https://developer.spotify.com/documentation/web-api/reference/#/operations/get-queue
However, it has a small problem that prevent it from being usable in all cases. You see, the queue will usually return exactly 20 items. The problem is that it never returns less, even when it's appropriate. This has the side effect that the end of a queue is never clear, as it simply repeats itself until 20 items are returned.
View on Spotify Client:
Result of the API:
There is no way to know if the queue is actually like this or if it's simply a side effect. It also doesn't give any information for whether the user has actually manually queued songs or if the upcomings songs are simply the next ones in the respective playlist context.
It would be nice if Spotify extended the API endpoint to reveal this information as well, as right now more than a good guess isn't possible.