search

spotify / web-api

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

Retrieve User's Currently Playing Track #12

Closed sanjams2 closed 7 years ago

sanjams2 commented 9 years ago

Is there a way/plans of an update to the web-api that provides a way to get the song a user is currently listening to?

mennolaan commented 8 years ago

+1

ghost commented 8 years ago

I recently made a twitch chat bot and i wanted to have a !currentsong command, i ended up "scrobbling" my spotify to a lastfm account and used their API to get the current song. Next up is creating a !songrequest command, no clue how I'm gnna do that yet... Anyways, cant wait for this to be in the official Spotify API. 👍

limex commented 8 years ago

@jj199611 I suppose you used http://www.last.fm/api/show/user.getRecentTracks and went for the track wtih nowplaying="true" ?

ghost commented 8 years ago

I just took the first item in the list instead of filtering for nowplaying="true" but either of those solutions work indeed.

gabernardone commented 8 years ago

+1 I'm anxious for this feature

cagdasdag commented 8 years ago

+1

freman commented 8 years ago

Meh, this is never going to happen, and I'm sick of not being able to skip artists/songs I don't like automatically. I'm cancelling spotify and going back to mp3s

ralapack commented 8 years ago

+1

Rich Alapack ralapack@gmail.com

On Aug 17, 2016, at 3:02 PM, Shannon Wynter notifications@github.com wrote:

Meh, this is never going to happen, and I'm sick of not being able to skip artists/songs I don't like automatically. I'm cancelling spotify and going back to mp3s

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

lachieh commented 8 years ago

@hughrawlinson @thelinmichael It'd be great if you guys could give some sort of explanation on why this can't be, won't be or hasn't been implemented yet. This is by far the most requested endpoint for the API and has been for a year and a half now.

If it's a load issue, or the potential of losing ad plays, then lock it down to premium users. There's already an authentication request required to access API endpoints which further limits load potential, and all the apps already get this information through the Spotify Connect feature so the information is there.

ghost commented 8 years ago

@hughrawlinson @thelinmichael It'd be great if you guys could give some sort of explanation on why this can't be, won't be or hasn't been implemented yet. This is by far the most requested endpoint for the API and has been for a year and a half now.

If it's a load issue, or the potential of losing ad plays, then lock it down to premium users. There's already an authentication request required to access API endpoints which further limits load potential, and all the apps already get this information through the Spotify Connect feature so the information is there.

I mean this should not be a big problem for Spotify to implement...

look at Deezer: https://api.deezer.com/user/me/history and Napster: https://api.napster.com/v2.0/me/listens

They also don't have the "current track" endpoint but at least a "listening history"

AlicanGultekin commented 8 years ago

If it's a load, whatever issue, at least it should be enabled for premium users.

ghost commented 8 years ago

@J0shuaw does either of those API's have the currently playing song in the listen history as the first item like LastFM has?

thelinmichael commented 8 years ago

@lachieh, I'll do my best to provide some context. We're a relatively small team within Spotify, and we've got a large number of stakeholders - from innovative individual third-party developers to large companies that we form strategic partnerships with. And while we iterate on the platform on a daily basis, larger changes like this one take time and long-term commitment. There are also business reasons behind prioritising features, or even building them in the first place - reasons that are not always appropriate to discuss in a public forum such as this one. So while we're extremely happy that the community is eager to build experiences based on our platform and that developers such as yourself are engaging with us to improve it, we ask for your understanding while we're at work making this happen.

If you're up for it, we're looking for backend engineers to join the team.

lachieh commented 8 years ago

@thelinmichael Thanks, appreciate the update. It's good to know that it's not completely off the table. Personally, I think this should be given a much higher priority, as the integrations this would enable would inevitably lead to a greater experience for users and more opportunities for developers and third party services. That being said, it's understandable that business arrangements dictate what you can and can't do. It's just unfortunate that those arrangements limit the platform potential.

brunorsini commented 8 years ago

Hi Michael,

Thanks for the reply! I'm building a music recommendation app pretty much based on Spotify and want to +1 the fact that this would really take the API to another level... Having to to get users to use Last.fm for this is tough, most people don't even know about it.

In any case, thanks a bunch for the update and greetings to Lisa Kleinsorge and Owen Smith, two of your colleagues who I hang out with every now and then :)

On Fri, Aug 19, 2016 at 9:05 AM, Lachlan Heywood notifications@github.com wrote:

@thelinmichael https://github.com/thelinmichael Thanks, appreciate the update. It's good to know that it's not completely off the table. Personally, I think this should be given a much higher priority, as the integrations this would enable would inevitably lead to a greater experience for users and more opportunities for developers and third party services. That being said, it's understandable that business arrangements dictate what you can and can't do. It's just unfortunate that those arrangements limit the platform potential.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/spotify/web-api/issues/12#issuecomment-241060156, or mute the thread https://github.com/notifications/unsubscribe-auth/AFwYRkz1AJ4gec-_vxRYIyn4sm5448uJks5qhdRSgaJpZM4Dysiw .

tal commented 8 years ago

@thelinmichael thanks a lot for the update. A big piece of what i'd like this api for is just to be able to save/unsave current track. And/or remove current track from current playlist. Hopefully this is something that gets worked into the roadmap.

watzon commented 8 years ago

@thelinmichael just sent in my resume :+1:

sergiotomasello commented 8 years ago

@thelinmichael is there any hope this features will be realized? This feature is critical and decisive in the choice of life or death of my service :( let us know regards

javierquevedo commented 8 years ago

+1

trunet commented 8 years ago

+1

SimoneTosato commented 8 years ago

+1

jsdario commented 8 years ago

Is there a way to obtain this info on a mobile app using native SDKs?

esdu commented 8 years ago

Please expose the current playing track!

jennykitten78 commented 8 years ago

This would be great, please do this. +1

johnverrone commented 8 years ago

+1

wellyal commented 8 years ago

Any updates about this feature?

JohnnyCrazy commented 8 years ago

@wellingtonamaralleitao If there were updates about such functionality, I'm pretty sure spotify would've posted about this :)

@thelinmichael @hughrawlinson Did you guys consider locking popular issues which generate a high amount of useless noise? I really like to get notified when something happens to one of them, but sadly my inbox contains 90% "+1" and "when will we see..." noise spam.

thelinmichael commented 8 years ago

Conversation locked to avoid spamming everyone subscribing this issue with further "+1"s. To clarify, this doesn't mean that the feature request is closed.

hughrawlinson commented 7 years ago

Very happy to report that we've just launched an endpoint to address this issue! Get Current Users Recently Played Tracks.

tal commented 7 years ago

Thats amazing, where can we find docs on the endpoint?

hughrawlinson commented 7 years ago

@tal they're available here.

EXTREMEGABEL commented 7 years ago

Nope the linked Pages return a 404

lachieh commented 7 years ago

The official docs currently returns a 404, but I'm assuming it'll live here.

Edit: Also, this is brilliant. Love it. Thanks for the update @hughrawlinson!

hughrawlinson commented 7 years ago

Looks like a bad link got cached somewhere, I'll try and hunt down the cache to invalidate it. in the mean time, here's the documentation for the endpoint

hycday commented 7 years ago

oh wow, great news !! so nice to see when companies hear out and can put in place API requests !

prestonvanloon commented 7 years ago

Can you open this back up? The endpoint referenced is for recently played (at least 30 seconds of playtime), not the currently played/listening track.

There is an opportunity for IOT devices to read the currently played track and display track information or other visuals to go alone with the currently played track.

vcanales commented 7 years ago

I'm guessing this means this is as far as this feature will go? This doesn't address the "Currently Playing" case.

hughrawlinson commented 7 years ago

@prestonvanloon sure - reopened

JonSchapiro commented 7 years ago

@devjunkORG I guess you could poll it?

Kaiser1989 commented 7 years ago

WOW! Thank you very much. One big step forward!

vcanales commented 7 years ago

@hughrawlinson thanks for reopening it!

Kaiser1989 commented 7 years ago

For those who are interested: i've already added this new feature to the spotify-web-api-java (official one isn't uptodate anymore)

https://github.com/Kaiser1989/spotify-web-api-java/tree/recent_songs

hycday commented 7 years ago

Seems that there is a "delay" when retrieving the list : Say you listened to tracks A, B, C, D, E, F, G and are now listening to track H, then when retrieving the list, you 'only' get A, B, C, D and then a bit later you will get E, then later F etc.. I have the feeling you always have a delay of 3-4 tracks.

Would be awesome if such delay would be reduced to minimum so that we could even get the current one playing (H, in this example), and maybe reducing the 'played for at least' time to maybe 5 seconds before adding it to the list.

brunorsini commented 7 years ago

Ouch! This delay would completely kill the feature I want to implement on my app : /

On Thu, Mar 2, 2017 at 12:30 PM, hycday notifications@github.com wrote:

Seems that there is a "delay" when retrieving the list : Say you listened to tracks A, B, C, D, E, F, G and are now listening to track H, then when retrieving the list, you 'only' get A, B, C, D and then a bit later you will get E, then later F etc.. I have the feeling you always have a delay of 3-4 tracks.

Would be awesome if such delay would be reduced to minimum so that we could even get the current one playing (H, in this example).

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/spotify/web-api/issues/12#issuecomment-283770890, or mute the thread https://github.com/notifications/unsubscribe-auth/AFwYRuFnxUaDVSuTpz_cc0h0yGzfqfi6ks5rhybbgaJpZM4Dysiw .

jscholes commented 7 years ago

Seems that there is a "delay" when retrieving the list : Say you listened to tracks A, B, C, D, E, F, G and are now listening to track H, then when retrieving the list, you 'only' get A, B, C, D and then a bit later you will get E, then later F etc.. I have the feeling you always have a delay of 3-4 tracks.

For what it's worth, I didn't observe this delay when testing the endpoint yesterday. New tracks were added as soon as they finished playing in my desktop client. I suppose they could've implemented the limit since then because of high demand...

tal commented 7 years ago

For what it's worth, I didn't observe this delay when testing the endpoint yesterday. New tracks were added as soon as they finished playing in my desktop client. I suppose they could've implemented the limit since then because of high demand...

I think the behavior a lot of people are wanting is it to appear in list immediately when you start playing the song.

I personally would like the behavior to work as following:

Endpoint would immediately show the track once it starts playing, but that track would only persist in history if it'd played for 30 seconds or more.

Something that would help with a lot of this is some sort of public interface into spotify connect.

Kaiser1989 commented 7 years ago

There is definitely no delay. I tested yesterday with a limit of 1. You get the last played song in the moment it stops (it has to be played for at least 30secs)

lachieh commented 7 years ago

That's good to know, though it's still not the original request for this issue. The request is for the 'currently playing' track, not the most recently finished tracks. It's a step forward, but it's still not quite real-time. Definitely appreciate all the work the Spotify team is doing on the web-api, but I'm still hanging out for the 'currently playing' endpoint.

I suggest that this thread be locked as it was before and hold out for another update.

ricardodani commented 7 years ago

There's a hack, using the lastfm scrobbling api you can get the actual playing music on the instant it was played if user's spotify connects to lastfm, of course

2017-03-02 14:32 GMT-08:00 Lachlan Heywood notifications@github.com:

That's good to know, though it's still not the original request for this issue. The request is for the 'currently playing' track, not the most recently finished tracks. It's a step forward, but it's still not quite real-time. Definitely appreciate all the work the Spotify team is doing on the web-api, but I'm still hanging out for the 'currently playing' endpoint.

On Thu, Mar 2, 2017 at 5:25 PM Kaiser1989 notifications@github.com wrote:

There is definitely no delay. I tested yesterday with a limit of 1. You get the last played song in the moment it stops (it has to be played for at least 30secs)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/spotify/web-api/issues/12#issuecomment-283802548, or mute the thread https://github.com/notifications/unsubscribe-auth/ABnBXsq6UePe_ IYdpZK9YUu4cDJinGuoks5rh0HtgaJpZM4Dysiw .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/spotify/web-api/issues/12#issuecomment-283804244, or mute the thread https://github.com/notifications/unsubscribe-auth/AAXugyBySP6BRyIE5asEgd7yLsARCGn3ks5rh0OEgaJpZM4Dysiw .

-- []`s Ricardo L. Dani http://about.me/ricardodani

brunorsini commented 7 years ago

That's what I've been using but this is a hugely prohibitive "if"...

On Thu, Mar 2, 2017 at 2:38 PM, Ricardo L. Dani notifications@github.com wrote:

There's a hack, using the lastfm scrobbling api you can get the actual playing music on the instant it was played if user's spotify connects to lastfm, of course

2017-03-02 14:32 GMT-08:00 Lachlan Heywood notifications@github.com:

That's good to know, though it's still not the original request for this issue. The request is for the 'currently playing' track, not the most recently finished tracks. It's a step forward, but it's still not quite real-time. Definitely appreciate all the work the Spotify team is doing on the web-api, but I'm still hanging out for the 'currently playing' endpoint.

On Thu, Mar 2, 2017 at 5:25 PM Kaiser1989 notifications@github.com wrote:

There is definitely no delay. I tested yesterday with a limit of 1. You get the last played song in the moment it stops (it has to be played for at least 30secs)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/spotify/web-api/issues/12#issuecomment-283802548, or mute the thread https://github.com/notifications/unsubscribe-auth/ABnBXsq6UePe_ IYdpZK9YUu4cDJinGuoks5rh0HtgaJpZM4Dysiw .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/spotify/web-api/issues/12#issuecomment-283804244, or mute the thread https://github.com/notifications/unsubscribe-auth/ AAXugyBySP6BRyIE5asEgd7yLsARCGn3ks5rh0OEgaJpZM4Dysiw .

-- []`s Ricardo L. Dani http://about.me/ricardodani

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/spotify/web-api/issues/12#issuecomment-283805706, or mute the thread https://github.com/notifications/unsubscribe-auth/AFwYRnTK_15NHvoILELz2yMxOlD7dXRBks5rh0TlgaJpZM4Dysiw .