CODEWITHSUNDEEP
iossoundcloud
Oren
Oren

Reputation: 5103

Did SoundCloud API just change without notice?

I have an app using SoundCloud's search service (tracks.json). It used to work fine but now all of a sudden it's crashing 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'm either getting an array returned, or a dictionary with the array inside a "collection" key. The result is inconsistent. I first assumed they were in the middle of a deployment but it's been like this for about 12 hours and still the same. I've also further discovered the following:

  1. West coast users are getting the dictionary
  2. West coast users making the same call over http (not https) get an array
  3. East coast users are getting an array over https (unsure of http)

I noticed this blog post by their devs: https://developers.soundcloud.com/blog/offset-pagination-deprecated However that post doesn't mention anything about the response format changing. It also looks like that changed should have happened 2 months ago.

Is this just a bug on their part? Are they in the middle of a deployment? Anyone else seeing this? Is the response expected to be a dictionary now?

UPDATE:

This problem seems to be explicitly tied to searching for that URL. If I move the parameters around the response changes. This isn't a local caching issue since I confirmed the problem from someone else as well. My best guess is SoundCloud rolled something back but this URL is cached either by our ISP or SC itself.

Upvotes: 4

Views: 268

Answers (2)

eugeneK
eugeneK

Reputation: 11136

Try to remove .json from the request. Seem to work for me.

Upvotes: 0

Oren
Oren

Reputation: 5103

It looks like SoundCloud just messed up because now I'm seeing the change rolled back. It took a while for the cache to clear though and reach all our users. This isn't the first time SC changed their API schema on us with little to zero notice. I have very little confidence that this won't happen again so I'll be wrapping their service inside a dummy one that we can fix behind the scenes without an app update.

Very disappointing that they've remained completely silent on this issue. I see no mention of any API changes, bad-deployments, etc on their twitter feed: https://twitter.com/SoundCloudDev

Upvotes: 2

Related Questions