Just as an FYI to everyone, Spotify does not allow any "commercialization" of their APi's / Platform. (Learned this the hard way when I released my Spotify app for $.99 on the app store).
> With a user’s permission, developers can now access user profile information including playlists,
This is awesome news! The last time I tried to write something for Spotify to front-load my last.fm (I know I'm late to the game) account but couldn't get access to the playlists. Going to have to check this out when I get some time.
What I'd really love (and have looked for in the past) is a way to automatically push a song over to a specific spotify playlist every time I tag a song on shazam (thinking like an IFTTT recipe). It looks like that might be possible with this new api.
I had a quick look, but to play a track, all I can see is a 30 second preview. Am I missing something, or can you not get the track data from this API?
> EDIT: Should've read the first subtitle... "Our Web API lets your applications fetch data from the Spotify music catalog and manage user’s playlists."
Streaming is only available through libspotify or the beta SDK on IOS. Rumors from #spotify on freenode indicate that the SDK for other platforms is still being worked on. But once it ships it will provide a minimal lib for streaming and the web API will do everything else.
I really like Spotify and I love that they're making this API available. But we just saw netflix shutting down their API. Are Spotify committed to keeping this around, or will they just shut it off in a few months when it becomes too much of a pain to manage?
I think they hope the API will be used to drive subscriptions to their service. If that ends up being the case, they'll probably keep it around. Of course, nobody can look into the future and see what will happen. Building a business around a public API like this would probably not be a smart move... yet.
Is there an (easy to use) Spotify plugin to let my office-mates vote on or suggest songs to play next? I know there are some hacky solutions, but this new Web API seems like it should make that a lot easier.
Would it kill them to fix some of the bugs in the desktop application first? You can't even sort search results any more. This is apparently marked as a "not now" concern. A lot of premium customers are deeply unsatisfied with the way Spotify handled their latest update.
Personally this is great timing for some of the features I'm needing to develop http://Listen2EDM.com further. I'm sure that music discovery, and the music community in general, will greatly benefit from this!
This sounds great, indeed. With a listening history on last.fm that reaches back to early 2009, I always thought it would be great to have a service to use the last.fm data to build dynamic playlists for spotify.
Populate a http://developer.echonest.com/docs/v4/tasteprofile.html with the listening history and you can use it for dynamic playlisting using the spotify catalog. That is as long as echonest matches the song metadata to an id.
It doesn't seem possible to delete a playlist or remove tracks from one :( Other than that it's pretty great, maybe I can automate my playlist management now :)
Same conclusion we also had in https://github.com/mopidy/pyspotify/issues/139 when looking at if we should move away from libspotify in favor of the new web API. For now I would stick with libspotify wrappers until a more complete version of the API comes out.
Basically, you write a simple dbus app that listens for the appropriate song-changed signals from Spotify, and then do with that as you wish. This might not be as easy on Mac or Windows though, as I've only ever used it on Linux.
You could have spent the 5 minutes on their website that I did to find the endpoint reference which shows that yes, you can get to quite a bit of the API without authenticating:
Probably just long enough for them to make a too-polite-to-be-ironic "thank you for using our development environment" blog post where they shut it down and shunt what's left to a private API for the apps they're currently trying to acquire.
Insane. I was speaking about Spotify API about an hour ago on IRC, Google'd around, found this, disregarded it (how new can it be?) and now it's at the top of HN.
This keeps happening to me, with docker release, with deis, with vagrant, so many things I talk about and then I look at hn and they're there, just waiting for me.
This happens so often, we all say here to check HN after we discuss something, because there will no doubt be a link ready for us. Starting to wonder if this is actually just a news feed where you see what you need to see.
No code of course, just name-hoarding. FOSS can be really ugly sometimes.