topic Re: Spotify Web API: Queue endpoint needs polish in Spotify for Developers

Spotify Web API: Queue endpoint needs polish

wireframed — Tue, 24 Jan 2023 15:31:37 GMT

I'm working on building a queue view using the newish Queue endpoint, but there are a few bugs/missing features:

Firstly, it returns 20 results, including currently playing. But it always returns 20 results - even when the queue is 12 items long. You just get the first 8 items looped.
Secondly, if I want to play the track by skipping to the track in queue, it's not clear what context to use - is it not possible to jump to the 5th track in the queue, without actually skipping 5 tracks?
Lastly, the Spotify player seems to "know" if a track is added in the context of a user-modification, or continueing the current playlist, artist or whatever context of playback. This does not seem exposed in the API.

Re: Spotify Web API: Queue endpoint needs polish

monkeyboy2805 — Tue, 06 Feb 2024 13:07:43 GMT

to add to this, the limit of 20 seems inconsistent given e.g. the desktop app will happily display 80 tracks.

Re: Spotify Web API: Queue endpoint needs polish

syeo66 — Wed, 17 Jul 2024 17:39:09 GMT

Juli 2024 and this is still an issue. The looping of the queued items until the 20 is full makes the API mostly useless. Spotify! Any plans to address this?