Closed func0der closed 6 years ago
You didn't miss anything - retrieving links to full mp3s is not possible using the Web API. Playback of full tracks is possible using the Android and iOS SDKs though.
Why is this not possible with the Web API?
It's not possible yet, we're looking into providing a way for developers to do playback of full-length tracks over the web. Exactly how hasn't been decided.
That is actually great news. Thank you for the insight :)
I hope this will be available soon.
Thanks for pointing me to this issue - it seems like you should be able to just wrap whatever powers play.spotify.com, including the requirement that the user be logged into Spotify, and that can be a good v1.
Can't say enough how bad I'd love to use this API!
Any ideas on when this might surface? Are you talking weeks or months when you mention short term?
@thelinmichael Hey! I was wondering if there was any news on this. We would absolutely love to beta test any kind of full playback web functionality. Could be helpful on both ends so that we can report bugs, help solve issues.
+1, would love this functionality.
No news unfortunately @GabeJacobs. Definitely see the benefits of having third-party developers doing beta testing.
This a reason why Spotify Apps shouldnt havent closed until full web streaming or play button js sdk are available. Now mobile developers gets better support than desktop Den 29 okt 2015 09:38 skrev "Michael Thelin" notifications@github.com:
No news unfortunately @GabeJacobs https://github.com/GabeJacobs. Definitely see the benefits of having third-party developers doing beta testing.
— Reply to this email directly or view it on GitHub https://github.com/spotify/web-api/issues/57#issuecomment-152112828.
Is there any news if (and when) this is going to happen?
+1 Any possibility to use the Android SDK / Java on Desktop?
We havent seen any developer news since june 2015. Thats strange for a such top notch company. Are you retiring Spotify desktop entirely? The video feature announced will only be available for mobile?
onsdag 3 februari 2016 skrev Cédric Bellegarde notifications@github.com:
Really strange, that hard to add authentification on an http server?
So, if I launch wireshark, I can get track urls and play them without any authentification?
— Reply to this email directly or view it on GitHub https://github.com/spotify/web-api/issues/57#issuecomment-179191743.
Best regards, Alexander Forselius (Dr. Sounds) Musician, and programmer. http://dr-sounds.com
Github http://www.github.com/krikelin Twitter http://www.twitter.com/drsounds Spotify http://open.spotify.com/artist/2FOROU2Fdxew72QmueWSUy http://www.youtube.com/watch?v=pjdujamrcds LinkedIn http://se.linkedin.com/pub/alexander-forselius/13/b11/500/
+1, an ETA from Spotify would be great
With libspotify being discontinued, it would be great to get this capability in the web api, platforms exist outside of Android and iOS. It would also be nice to be able to do 320kbps streaming...
I feel like spotify is taking a crap on all developers, but also on users... Android and iOS are pretty well supported, but all other platforms are just barely, if at all, supported. Spotify, please provide information so developers and users know what to expect.
So is there any workaround to play full tracks on, say, a Windows 10 app? I tried repackaging the Android .jar files as .dll's, but there are some issues. Spotify really needs to get on this.
A workaround I found (not sure if it violate Spotify's conditions) is to get tracks metadatas from the Spotify API, and then get the audio from YouTube. Doesn't works on 100% of the tracks tough.
Le mar. 15 mars 2016 17:18, Shawn Beachy notifications@github.com a écrit :
So is there any workaround to play full tracks on, say, a Windows 10 app? I tried repackaging the Android .jar files as .dll's, but there are some issues. Spotify really needs to get on this.
— You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/spotify/web-api/issues/57#issuecomment-196904135
--
Vincent L.
That workaround defintely violate the TOS but the previous one seems to be interesting the repackaging of the java files into dll but I am sure it is a violation too
tisdag 15 mars 2016 skrev Vincent Lwt notifications@github.com:
A workaround I found (not sure if it violate Spotify's conditions) is to get tracks metadatas from the Spotify API, and then get the audio from YouTube. Doesn't works on 100% of the tracks tough.
Le mar. 15 mars 2016 17:18, Shawn Beachy <notifications@github.com javascript:_e(%7B%7D,'cvml','notifications@github.com');> a écrit :
So is there any workaround to play full tracks on, say, a Windows 10 app? I tried repackaging the Android .jar files as .dll's, but there are some issues. Spotify really needs to get on this.
— You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/spotify/web-api/issues/57#issuecomment-196904135
--
Vincent L.
— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/spotify/web-api/issues/57#issuecomment-196920761
Best regards, Alexander Forselius (Dr. Sounds) Musician, and programmer. http://dr-sounds.com
Github http://www.github.com/krikelin Twitter http://www.twitter.com/drsounds Spotify http://open.spotify.com/artist/2FOROU2Fdxew72QmueWSUy http://www.youtube.com/watch?v=pjdujamrcds LinkedIn http://se.linkedin.com/pub/alexander-forselius/13/b11/500/
@drsounds It very well may be. However, not to casually pass off violation of TOS, but stuff like that is gonna end up happening if Spotify doesn't give us an official way.
Yes and that might cause the entire api being shut down I am afraid
tisdag 15 mars 2016 skrev Shawn Beachy notifications@github.com:
@drsounds https://github.com/drsounds It very well may be. However, not to casually pass off violation of TOS, but stuff like that is gonna end up happening if Spotify doesn't give us an official way.
— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/spotify/web-api/issues/57#issuecomment-196922519
Best regards, Alexander Forselius (Dr. Sounds) Musician, and programmer. http://dr-sounds.com
Github http://www.github.com/krikelin Twitter http://www.twitter.com/drsounds Spotify http://open.spotify.com/artist/2FOROU2Fdxew72QmueWSUy http://www.youtube.com/watch?v=pjdujamrcds LinkedIn http://se.linkedin.com/pub/alexander-forselius/13/b11/500/
Very disappointed that 30 second previews are all we can work with. Really hope this feature gets some love from the team soon!
+1 ...
This is a sad state of affairs here. Last.FM api is also going to the ****. We have been waiting on this feature for a long time. Can we can get any information? This is apparently something all the developers are wanting, so drop the play button and let us build clients!
It seems we can get all information for a track but cannot play it!
Here are some ideas for cool features that I'd love to build, if Spotify had API playback support:
On Sat, Mar 26, 2016 at 7:27 PM, Tansu TURKOGLU notifications@github.com wrote:
It seems we can get all information for a track but cannot play it!
— You are receiving this because you commented. Reply to this email directly or view it on GitHub https://github.com/spotify/web-api/issues/57#issuecomment-201949591
This feature would allow an infinite number of new concepts for music apps, I believe that Spotify would welcome that. However "the web" can't be considered a controlled environment just as mobile platforms are. For example, the current web player has dozens of apps that record songs and save them as mp3 files, so it wouldn't make much sense to publish an API that makes this even easier.
Instead of complaining why this feature isn't available yet, we would do better by giving ideas on how to protect Spotify's content from illegitimate use. Maybe it could helps us to get it delivered sooner, who knows...
AFAIK, Netflix is successfully dealing with this by working within W3C in some drafts that will help browsers to protect media playback in general... are you guys considering something similar?!
@thelinmichael if an ETA can't be provided, we would like to know at least if currently this is low priority feature or even being considered at all.
Thanks!
+1 would like to see this feature ASAP.
I think what the problem for Spotify with this sort of feature is that they are afraid of violating someones personal privacy. Case in point, the web play button has no way to automatically play, the user has to click the play button. No one wants a website to play anything when it loads. If that is the concern, a possible solution might be:
When the user grants access to their profile to a web application, there could be a scope of: 'Allow this application to control Spotify Desktop app'. Getting consent from the user.
Using another endpoint 'clientPlay' (or something) you would pass the Oauth token and Spotify would determine authenticity, then it would just funnel the request into what open.spotify.com already does.
I doubt I'm the first one to mention this, but thought I would put it out there.
@jonknyc I came along this thread researching the API to make a party jukebox app like you mentioned. If you're interested in collaborating, feel free to send me an Email (it's in my profile).
Is this feature out yet?
My educated guess
Spotify has got in trouble with some lawsuits and also needs to be substainable, the pressure to reduce the loss and make money has increased so I think they are careful to introduce this unless times becomes better. web streaming could need negotiations with rightholders and I think they are not willing to do this right now. There is a difference between allowing web and mobile streaming and it is that a web streaming service would increase the risk that more people rips music from spotify. So I propose a JS api to the play button instead which can control spotify from the browser although the desktop client will do the playback. But this can be tricky too for business reason since they dont want people to create services like eternify was if programmatic access to playback would be possible.
A spotify connect api or a js api for play button would be very handy. But before this can be done I think some investigation must be done. And Spotify also become more substainable.
It seems like the developer platform has slowed down in its development and they focus more on increasing revenue streams with more branding options such branded playlists.
fredag 10 juni 2016 skrev Brijesh Rakholia notifications@github.com:
Is this feature out yet?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/spotify/web-api/issues/57#issuecomment-225242204, or mute the thread https://github.com/notifications/unsubscribe/AE3z1yfHiQrjA9JHitVSHdRMbZnYBGpQks5qKZw-gaJpZM4EqAUH .
Best regards, Alexander Forselius (Dr. Sounds) Musician, and programmer. http://dr-sounds.com
Github http://www.github.com/krikelin Twitter http://www.twitter.com/drsounds Spotify http://open.spotify.com/artist/2FOROU2Fdxew72QmueWSUy http://www.youtube.com/watch?v=pjdujamrcds LinkedIn http://se.linkedin.com/pub/alexander-forselius/13/b11/500/
Any updates?
People are saying the Android and iOS SDKs are better... Are you guys serious? Have you even had a look at their limited exposure on the player functions and the foreground service the player runs on at least on Android? I have been working on my project for a month until I realized that Spotify, a music company, has no way to let you play and control music properly. It's a shame. Why make any of the APIs available when all you can do is log in and browse? ...
+1
From a business stand point, if you had many third party apps playing your music without regulation, that would lose the company money because they wouldn't be able to manage advertisements or payed accounts. With one payed account hooked up to a Spotify API, a third party app could control the player at will, potentially bringing music to hundreds or thousands with just one payed account.
So how do you regulate the use of a feature like this?
You create API credits, and playing tracks cost credits. The more popular the app, the more credits that app consumes, and the larger their monthly cost. This clearly leads apps that are more popular to build and integrate their own income system. Potentially opening up relationships between Spotify and the third party app for 'built in advertising' through the already in use web-api. Bands could advertise easily on third party apps through Spotify web-api. Potentially marketing to third party apps that have a higher demographic of people who listen to that bands particular style of music.
Overall this would open up many avenues for ingenuity, business relationships, and a happier customer and developer base.
It's impossible to bring free music to hundreds or thousands through one premium account. I'm certain their API has query limitations just like any other API. You cross the quota they start to block the hose. If they don't I would be very surprised. And also, why would someone pay for a third party app when they have the source aka Spotify right there? I think that the point of Spotify APIs is to bring more users to the platform in any way possible... the apps that use the API alleviate the process or make it different, or fun, or whatever. Business to business will never work for Spotify in my opinion. Why do you think Apple is not using Spotify for music but instead made their own subscription service. It's probably more profitable to have loyal monthly subscribers...
The hole point of this issue is that there isn't a way to even play tracks using a third party api.
@crwgregory @arn95 Gotta weigh in here. We've waited for web playback for over a year now and have talked to Spotify about it in the past. First, there is no need for Spotify to do any sort of credit system. Having an full playback API for them is automatically good because it drives people to buy premium. It expands their market and allows for their brand to reach other parts of the internet.
That said, it's a security issue for them. It's also a manpower issue. As far as I know, only a few people work on the API's. We use their iOS SDK extensively and from my knowledge it does not seem like a true priority. In reality, their API is one of the few things that set them apart from their competitors and it could be the big difference that puts them above Apple Music, Tidal and Google Play.
I hope Spotify sees this thread and understands just how much they could benefit for supporting full playback on the web. This thread is proof that their are developers who are waiting to build apps that spread Spotify. If there are developers, there are customers. That should be enough of a reason to prioritize this.
@GabeJacobs
That said, it's a security issue for them. It's also a manpower issue. As far as I know, only a few people work on the API's. We use their iOS SDK extensively and from my knowledge it does not seem like a true priority. In reality, their API is one of the few things that set them apart from their competitors and it could be the big difference that puts them above Apple Music, Tidal and Google Play.
While I aggree mostly with you, I still wish there would be some more transparency relating to future and current operations. Looking at the current issue list, there are about 44 enhancements, most of them with a statement like "maybe will come at some point in the future". Considering the rather small team and propably system-restrictions, I'm pretty sure a lot of those features won't come in the next year/s. What I would like to see: A small analysis of the current open issues, considering implementability and a possible time-frame.
I hope Spotify sees this thread and understands just how much they could benefit for supporting full playback on the web. This thread is proof that their are developers who are waiting to build apps that spread Spotify. If there are developers, there are customers. That should be enough of a reason to prioritize this.
I'll second that first sentence, but considering the (dead) state of the web-api
, ios-sdk
and android-sdk
-repo, I'm very uncertain.
(I still hope they're currently working on the desktop-SDK :wink: )
This needs to be added to the API. Where is desktop-sdk
?
Was this ever implemented?
Was this ever implemented?
No.
I'm following this issue until it is implemented. My project is "on hold" until it is. In the meantime I'm deciding if I want to spend the time creating an iPhone/Android app to support playback until this is implemented.
Overall the API is great! Can't wait to see this when it comes. I trust that spotify is working hard on creating this. There seems to be a fair amount of activity with the new WebAPI.
@gordolio The Android SDK is terrible. You don't even have the ability to modify the MediaPlayer UI.
Has anyone heard of SoundCloud? LOL
SoundCloud offers jQuery API which I don't really like (I would much more prefer a vanilla js wrapped API) but it's extremely easy & quick to build your web app upon.
The only draw back of SoundCloud is that it currently has licenses with Universal Music & Warner Brother only. Sony hasn't come on board yet. But that's still roughly 50% of all major music licenses.
I wanted to created a Spotify web app but after reading this thread, I quickly realized I am better off staying with SoundCloud or host my own mp3.
@Hackya Yes. But they're two completely different things. If SoundCloud does the job for what you need that's great. But posturing it as a replacement for Spotify is like saying MSDN is a replacement for Stack Overflow; they're each good in their own way, but they are not the same thing.
@RareNCool
How can SoundCloud wep app be any different than Spotify web app other than the fact that Soptify web app does not allow full length streaming?
Can you demonstrate any test case/scenario where SoundCloud API is different from Spotify API?
Based on simple REST principles, our Web API endpoints return metadata in JSON format about artists, albums, and tracks directly from the Spotify catalogue. The API also provides access to user-related data such as playlists and music saved in a “Your Music” library, subject to user’s authorization. - sounds just like SoundCloud API to me.
https://developer.spotify.com/web-api/
Maybe there are other functionalities Spotify API provides that are not documented.
If so, please enlighten me.
@Hackya Didn't think of SoundCloud actually. Thanks! Before Spotify they were my goto for music. The only pro blem might be that it doesn't have the same amount of music as Spotify... We'll see.
@Hackya Sorry, bad wording on my part. I'm not saying that the API isn't fundamentally the same. I'm saying that 1) they don't have all the same music and 2) telling a Spotify subscriber who has cultivated their library, followings, etc. over the years, "No we can't do this with the Spotify API. But, hey! switch to SoundCloud and we can do it." isn't exactly a viable option because they simply aren't the same service. (and vice-versa for SoundCloud > Spotify) So unless you're building your app for new users only, offering one as an alternative to the other simply doesn't work.
Hey there,
I had a quick look at your Web API. It seems that there is the possiblity to get a 30 seconds preview of a song via a streaming url your a providing in the results. But I could not find the 'whole song' streaming url in there.
Did I miss something or is streaming your songs really not possible via this or any other API?
Thank you