I'm using the /tracks API endpoint to retrieve song stats like playback count and favorite count. I've noticed that the playback count in the API is not the same as the one on the website.
Here's an example
I found a workaround here https://stackoverflow.com/a/36985629/287491 but it seems that using it might be against the Soundcloud ToS although I didn't find the specific article in the ToS. On top of that I'd rather not use an undocumented API as it may change or be removed without notice.
What would be the proper way to retrieve the real playback count for a track?
As You wrote the workaround is valid but it surely violates the ToS of SoundCloud!
By the side of SoundCloud there was an attempt to clean up:
http://status.soundcloud.com/post/145855742725/stats-maintenance#note-container
Your is after their update (August 3rd, 2016 ), so it is a bug. My recommendation is to ask help on the forum, (stat special part), they seem to reply in this topic little to no time.
Update: the API worked as intended on 2017.10.09.
Related
I have been making events since 2011 and I'm trying to retrieve old event covers for archival purposes. Unfortunately I can't see covers before around Feb 2013. I assume the API terms changed around then, but I fear the images are lost forever.
After some research I think the field was picture,pic,pic_big but sadly nothing is returned in Facebook API explorer. Does anyone have any ideas? I assume Facebook has just got rid of them.
Thanks, I appreciate any help
yea, the title pretty much sums it up. Is it allowed for an app to access ressources on api-v2.soundcloud.com?
Is there any documentation for it?
Relevant since I'm currently working on a soundcloud app and I just recognized that most of the calls on the websites itself are done with api-v2. The responses from the server would be extremly helpful to build some kind of infinite streaming which is the feature I like most about soundcloud.com.
I cant speak for SoundCloud, but gryzzly (a former SoundCloud engineer) stated in a previous answer:
Letting you know, that using undocumented APIs is not going in line with the our developers’ Terms of Use.
How does one block/ban one user from a SoundCloud group via REST API?
Logic:
Though not in the docs (but then again, lots of other wrong info is there), one would expect that this should work:
DEL api.soundecloud.com/groups/{id}/members/{member_id}
Note:
Taught by my previous experience, I did not venture into testing any of my ideas since there is probably no way to guess how developers got it implemented, if implemented at all.
I looked at the API documentation and it was not immediately apparent to me. Is it available via partner access?
Also, the default rolling average for sentiment seems to be 7 days. Is there an option to change this. One obvious way of doing this is parsing the firehose and some partners probably do that. I don't care for all that data or parsing it, in the unlikely scenario where I can get access to that.
The Sentiment data is only available to partners that license our API. Please touch base with us and let us know what you would like to do and about your paid product:
http://stocktwits.com/developers/contact
There currently is no option to change the rolling average, we have plans to add different time frames, as we agree this would be helpful.
We offer a financial sentiment API at Knowsis.
API docs are available here: http://knowsis.github.io
Soundcloud is incredible. Compared to all other music-oriented sites, as a computer science major and a die-hard music fan, I can assuredly say Soundcloud is a beautiful creation, in terms of both purpose and design. Onto my (rudimentary and somewhat secondary) idea:
I feel it would be beneficial for Soundcloud to have a feature which allows for reverse playback - not in terms of playing song files themselves in reverse, but in reverse chronological order. Including this option would simply be a matter of a toggleable (probably not a real word) i-- vs. i++ and an additional conditional.
Doing so would allow for users to listen through their favorites in order of oldest to newest, to understand the development of artists over time, etc. While this isn't necessarily IMPORTANT, I think it extremely utilitarian, especially when programs like iTunes offer the option to sort by date added/modified.
Answering an old post here but the behavior of SoundCloud hasn't changed so this question is still relevant in my opinion. SoundCloud playlists, including the "liked tracks" playlist, still behave the same way as today. When listening to a playlist, the player always starts with the same song: the one you first added when you created the list. The track you just recently discovered will always be played last. It's a tad annoying and there is currently no way of reversing this order.
I created a custom SoundCloud player a while ago to answer this specific issue. You can try it here: https://alexandre.abrioux.fr/sc/.
The code is open-source: https://github.com/alexandre-abrioux/soundcloud-reverse.
I hope this will help some of you. Feel free to enjoy your playlists in reverse chronological order, or even fork the project and create your own player. Cheers!
This can be done by using the created_at timestamp of the /tracks resource in the API.
Your question might better be directed at programmers.stackexchange.com as this site is more for specific code-related troubleshooting.
Like HeatherSpence said, you can use the API to construct your own player (perhaps reverse-soundcloud.com ??), or just make a playlist in whatever order you like.