Announcements

Help Wizard

Step 1

NEXT STEP

FAQs

Please see below the most popular frequently asked questions.

Loading article...

Loading faqs...

VIEW ALL

Ongoing Issues

Please see below the current ongoing issues which are under investigation.

Loading issue...

Loading ongoing issues...

VIEW ALL

Recently Played Tracks API Not Working

Recently Played Tracks API Not Working

 As the title suggests, the Recently Played Tracks endpoint has suddenly stopped returning any results. 

Trying from the Sporify Dev console also returns the same results.  

 

Has anyone else experienced this? 

 

IMG_9359.jpeg

Reply
8 Replies

Hello,

if you are talking about the fact that the spotify API limits the number of available tracks to 50, some other people also had this problem (https://community.spotify.com/t5/Spotify-for-Developers/Now-that-users-can-view-their-recently-playe...)

If this isn't your problem, maybe consider retrying with no parameters (before or after) or reload the page, delete the cookies and log in again, or stuff like that.

I checked a few minutes ago, and everything works fine for me

 

 

Hey there,

Thanks for your input. I do not think it is a parameter/browser-specific type of problem.

This behavior is observed both in Spotify's “Try It” console and the application that uses the API.

The issue seems to be specific to my account. When trying to hit the endpoint using a different account, the call works just fine.

IMG_0181.jpeg

I am using stats for Spotify and have the same issue. No stats for recent plays available. If I open a new free account it works. 

Do you already have a solution for this problem?

If anyone from Spotify is watching this, I would take a new account, as I just started with Spotify!

Unfortunately, I do not. I am still waiting for a response from Spotify. Maybe reach out to them with a description of your symptoms. You can also share the link to this thread so that they are aware more than one user is experiencing this issue. You can reach the support team at this address: **bleep**

I just realized, that this problem only happens when I listened to specific Playlists. I currently mainly listen to 4 Playlists. This problem counts for three of them. There seems to be a relation of this error between these playlists, my premium account and the recently played track api. I have to admit that the recently played api works with my parallel free account.

Example for my premium account: I play songs from the playlists that works fine and I can see all tracks via the recently played tracks api. When I switch to one of the „bad“ playlists, no track info appears via the recently played track api. After a while, no tracks appear in the recently played track api and the api shows 0 tracks.  This seems to be related to the after/before counter. The system seems to realize that I played songs but is not providing them via the api. 

im having this problem and using parametres or not using them is the same, i cant get past the 50 last streams

Suggested posts