I have an application using the SoundCloud search service (tracks.json). It worked fine, but now it suddenly crashed for some of our users.
This is the call I'm making:
https://api.soundcloud.com/tracks.json?consumer_key=[YOUR_KEY†&q=music&filter=streamable&order=default&limit=50
I either get the returned array, or a dictionary with an array inside the "collection". The result is incompatible. At first I assumed that they were in the middle of deployment, but that was something like this for 12 hours and anyway. I also found the following:
- West Coast Users Receive Dictionary
- West coast users who make the same call via http (not https) get an array
- East coast users get an array over https (unsure of http)
I noticed this blog post by their developers:
https://developers.soundcloud.com/blog/offset-pagination-deprecated
However, this post does not say anything about changing the response format. It seems that the change was supposed to happen 2 months ago.
Is this just a mistake on their part? Are they in the middle of deployment? Has anyone else seen this? Is a dictionary response expected now?
UPDATE:
This problem is clearly related to finding this url. If I move the parameters around the response changes. This is not a local caching problem, as I confirmed this problem with someone else as well. My best guess is that SoundCloud is crawling something, but this URL is cached by either our ISP or SC.