Over the last 100 years we have dialed into radio stations at home, on the road, or in the office to access a curated mix of top hits delivered to us by our favorite DJ. With more and more of our daily activities taking place online, we find our source of music now comes from a mix of our mobile phones, our desktop computers and the radio - and is available to us whenever we need it. The amount of music available today is endless. The music scene has never been so vibrant. A proliferation of production tools at low cost and the ease at which an artist can share their sounds, gives everyone the opportunity to share their work at any time, with only a few clicks.
Keeping this in mind, we set out to determine: How can we bring a radio like experience to SoundCloud that would enable you to tune-in and lean back?
With more than 125 million tracks from over 12 million creators heard each month on our platform, SoundCloud is uniquely positioned to offer listeners a full spectrum of music discovery.
Classic hits, the latest releases, gems from underground talent and the best of what’s up-and-coming – all in one place.
How can you make great content discoverable and available at ease? How can you create a unique experience for every single user?
We previously introduced new playlist representations. The compact representation returns only the playlist itself without any of the tracks. For most users, this is preferable – the compact representation significantly reduces the size of the JSON payload for large playlists and provides faster API response times.
Beginning July 15, 2016, all queries using the
q parameter will only return this compact representation for playlists. Other playlist representations will no longer be available when using the
The new SDK improves stream security and content uploading functionality, and modernizes the technology stack.
The original version of the…
At SoundCloud, we’re building an ecosystem where creativity thrives. Developers are an important part of that ecosystem. We’re continually inspired by how you use the SoundCloud API to support creators and listeners in innovative ways.
Requests for playlists have always included the full track objects contained within. This representation may be convenient for playlists with ten or twenty tracks but can cause problems for playlists that contain hundreds or thousands of tracks. Requesting such large playlists could result in requests that take a long time to respond and that eventually timeout.
Today, we introduce two new representations for the
If you add
representation=compact to a playlist request, the request will
In October 2014, Apple announced
that all submissions to the App Store must include
To ease this transition we have built a sample app that demonstrates how to authorize a user via OAuth using only built-in…
The SoundCloud API will be dropping support for offset-based pagination on March 2, 2015, in favor of linked partitioning.
To page through a JSON response, pass the
parameter along with your request and it will return a collection, along with a
next_href property if there are additional results. To fetch the
next page of results, simply follow that URI. If the response does not contain
next_href property, you have reached the end of the results.
You can read more about linked partitioning in the Pagination section of our HTTP API Guide…
In previous blog posts, we discussed how SoundCloud has been moving towards a microservice architecture. Soon we had hundreds of services, with many thousand instances running and changing at the same time. With our existing monitoring set-up, mostly based on StatsD and Graphite, we ran into a number of serious limitations. What we really needed was a system with the following features:
All of these features existed in various systems. However, we could not identify a system that combined them all until a colleague started an ambitious pet project in 2012 that aimed to do so. Shortly thereafter, we decided to develop it into SoundCloud’s monitoring system: Prometheus was born.
The SoundCloud API will be dropping support for Extensible Markup Language (XML) responses. XML will be phased out on the following schedule:
Acceptheader. This default will be changed to JSON on December 1, 2014.
/tracks.xml) or an
Accept: application/xmlheader — will continue to be supported until December 15, 2014. After that point, only JSON responses will be supported.