This issue tracker is no longer used. Join us in the Spotify for Developers forum for support with the Spotify Web API ➡️ https://community.spotify.com/t5/Spotify-for-Developers/bd-p/Spotify_Developer
981
stars
79
forks
source link
Issue with GET /v1/me/player/recently-played paging #1405
If I repeat the above with a limit of 10 the above works as expected. However if there is a total limit of 50 results overall, why offer paging in this case at all? The docs seem to imply that 50 is just the max results per page.
Could I possibly be missing a scope or permissions on my application?
Issue found on December 4th 2019.
Endpoint(s):
GET /v1/me/player/recently-played
Scope(s):
Steps to reproduce:
get-recently-played
and request user-read-recently-played scopeExpected behaviour:
The previous 50 recently played tracks are returned.
Actual behaviour:
An empty result set is returned that looks like:
Points