API Changes

[kingosticks]

Soundcloud devs seem to be alive! They've made / are making some API changes which look like they will impact us. The API docs have moved here. The old endpoints still seem to work as of now. They also seem to be doing something to pagination and it sounds like the default response format is going to change.

[djmattyg007]

How does this affect the PRs that @Laurentww has submitted recently?

[kingosticks]

I've only looked at the rate limit one. Only the image one seems to hit the official API and that's restricted to the tracks endpoint which I don't think changed. Looks like it's mostly the /me/foo endpoints.

[Laurentww]

Adding images (#121) still uses the official API, as the standard app client id doesn't return rate errors here. Though, #121 could be improved as well by first attempting with the publicly obtained client id and reversing to the standard app client id on failure.

As far as I can see, no pagination calls are made and the current API call uris are up to date.

[kingosticks]

More api changes coming https://developers.soundcloud.com/blog/security-updates-api

[dreamlayers]

It seems the security related changes prevent mopidy-soundcloud from working now, as explained in https://stackoverflow.com/questions/68459401/soundcloud-api-authentication-always-throws-401-unauthorized

[bretonium]

looks like it. I am constantly getting mopidy[7898]: ERROR [SoundCloudBackend-6] mopidy_soundcloud.soundcloud Invalid "auth_token" used for SoundCloud authentication!

[bretonium]

According to soundcloud/api#151, this will not be fixed. Soundcloud api can now be used only together with a service that will issue a token. The tokens also need to be refreshed, since they are now time-limited.

Can mopidy provide an API endpoint that the clients could use to fetch the tokens? Is there anything similar in mopidy already?

[kingosticks]

Yes, Mopidy-Spotify works this way (utilising https://github.com/adamcik/oauthclientbridge hosted at auth.mopidy.com). We should be able to re-use that here also. Although I am not sure who controls Mopidy's soundcloud app and if they would need to update anything in the account settings, maybe it is @adamcik ?

Although they (Soundcloud) maybe need to sort out their CORS issues also (from soundcloud/api#151).

[adamcik]

I don't think I have access to the oauth things for this account. However, I did play with using the bridge for SoundCloud and it worked at the time.

So if we can recover the old account or get new credentials we should be good to go.

Perhaps check with @tkem if he has access?

But, ideally we should have this attached to a non-personal account like we've done for Spotify if at all possible.

[tkem]

@adamcik Well, sorry, no access.

[bretonium]

The current client_id was added in 2013 by @dz0ny

[kingosticks]

As far as I know there's still no way to get new soundcloud credentials (facepalm) but if the authorization flow worked previously as is, maybe we don't need to hunt down the owner (although it'd be nice to sort that too).

[adamcik]

That was with the old flow that got / is getting removed, so won't work :( Checked https://soundcloud.com/you/apps and I don't have anything setup myself.

[kingosticks]

@dz0ny has access and can provide he secret (is that all we need @adamcik) but everything else is locked out and can't be changed. This includes the callback URL but hopefully that isn't a show-stopper for us.

[adamcik]

That should be workable with the id + secret