Issue with GET /v1/me/player/recently-played paging

[MikePenhall]

Issue found on December 4th 2019.

Endpoint(s):

• GET /v1/me/player/recently-played

Scope(s):

• user-read-recently-played

Steps to reproduce:

1. Open the API Console
2. Go to the console for get-recently-playedand request user-read-recently-played scope
3. Enter type=track, limit=50 then submit
4. Results come back with 50 tracks and paging info that looks like:

   "next": "https://api.spotify.com/v1/me/player/recently-played?before=1575332662799&limit=50&type=track",
   "cursors": {
   "after": "1575405194517",
   "before": "1575332662799"
   },
   "limit": 50,
   "href": "https://api.spotify.com/v1/me/player/recently-played?limit=50&type=track"

5. Go back to the console and add before=1575332662799 with other fields the same and submit.

Expected behaviour:

The previous 50 recently played tracks are returned.

Actual behaviour:

An empty result set is returned that looks like:

{
  "items": [],
  "next": null,
  "cursors": null,
  "limit": 50,
  "href": "https://api.spotify.com/v1/me/player/recently-played?before=1575332662799&limit=50&type=track"
}

Points

• 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?

[MikePenhall]

Anyone else having a similar issue?

[dominik-meissner]

50 is the max overall you can retrieve.