Web API - Recently Played Next Link Response is Empty

wuor — Tue, 07 Jul 2020 05:13:58 GMT

My Question or Issue:

I am currently attempting to retrieve all of my recently played tracks up to the start of the day using the get-recently-played endpoint. I am able to get the first 50 tracks, but when attempting to use the "next" property provided in the response I receive an empty "items" list even though the status is 200.

I believe it was working before (maybe a couple weeks ago), not sure if there is something I missed. Any help would be appreciated.

Example for Better Context:

1st Request:

https://api.spotify.com/v1/me/player/recently-played?before=1594097999999&limit=50

1st Response (partial paste):

Status: 200 OK

{

...

}

"next": "https://api.spotify.com/v1/me/player/recently-played?before=1594064630449&limit=50",

"cursors": {

"after": "1594094900468",

"before": "1594064630449"

"limit": 50,

"href": "https://api.spotify.com/v1/me/player/recently-played?before=1594097999999&limit=50"

}

2nd Request ("next" property):

https://api.spotify.com/v1/me/player/recently-played?before=1594064630449&limit=50

2nd Response (full paste):

Status: 200 OK

{

"items": [],

"next": null,

"cursors": null,

"limit": 50,

"href": "https://api.spotify.com/v1/me/player/recently-played?before=1594064630449&limit=50"

}

Feel free to let me know if more information is needed.

Thank you!

Re: Web API - Recently Played Next Link Response is Empty

omerta89 — Wed, 20 Jul 2022 23:26:08 GMT

I am also having this issue using spotify-web-api-node. The first call return the first 50 tracks but using the "next" URL provided responds with a 200 code and empty/null values in "data".

topic Web API - Recently Played Next Link Response is Empty in Spotify for Developers

Web API - Recently Played Next Link Response is Empty

Re: Web API - Recently Played Next Link Response is Empty