We have been using the SoundCloud API and it suddenly stopped working earlier this week; it now return a "Not Found" message. Nothing changed on our side as far we know, so we are wondering if there are some known changes to the API that would require code change?
Here's an example of the URL we are using to access the API: https://api-v2.soundcloud.com/explore/Popular+Music?client_id=d2791ef3c22de81af61b4915a654b2e2&cb=1462986650375-9904013473612631
This is used within Javascript code for a new tab extension for Chrome on Windows.
The docs do not mention api-v2 endpoints.
Unless otherwise specified, the base URL for API endpoints is:
https://api.soundcloud.com
Try changing the base URL; if you're using the JS SDK, make sure you have the latest version of it.
Looks like api-v2 is an undocumented, internal version of SoundCloud API.
There is even a quote from the developers (emphasis mine):
Letting you know, that using undocumented APIs is not going in line with the our developers’ Terms of Use. I'd also not recommend building anything on top of it, as it is very much subject to change.
So there you go. It's possible that this endpoint changes, there's no documentation publicly available, you're not supposed to use it anyway and you're breaking ToS if you do, even though SoundCloud doesn't seem to be feeling bloodthirsty. What's important is to understand there's no official support for it (aka "will break everything you did at any moment").