Join GitHub today
user.getArtistTracks will be deprecated soon #298
We will be removing user.getArtistTracks from the public API soon. The new scrobble storage back-end doesn't support it, and the results returned by the method are slowly going out of date, as it's still powered by the legacy back-end.
However there is a new method user.getTrackScrobbles which is just like user.getArtistTracks, except also takes a "track" parameter. This covers the most frequent use cases for the getArtistTracks which have seen (such as "find my first scrobble of a specific song" or "work out how many times i played a particular song on a particular album")
The timeline for deprecation is sometime before May 2019.
@ben-xo Hi, thanks for letting us know!
I'll add a deprecation warning to
For example, the old one is at https://www.last.fm/api/show/user.getArtistTracks, but https://www.last.fm/api/show/user.getTrackScrobbles is 404.
I have a use case for the old
Is that for when it will stop working, or for when it is officially discouraged? If the latter, do you have a timeline for when it will be switched off?
referenced this issue
Feb 28, 2019
Sorry we haven't added the documentation yet - but it's basically the same as for user.getArtistTracks, except with a "track" parameter as well.
Unfortunately the only way to get information per-artist with the current scrobble-storage design is to either fetch information about all scrobbles (i.e user.getRecentTracks) then filter it, or to fetch information about an artist (user.getTopTracks filtered by artist) and then poll the histories for each track. So, that's the workaround for your use case. We don't currently plan to offer that as a single method.