Skip to main content

SoundCloud

MusicAPI holds the SoundCloud credentials used to authenticate your listeners. They are used solely to facilitate music transfers a listener has authorised, the same way FreeYourMusic works. You do not need a SoundCloud developer account, and you never store SoundCloud tokens.

Enable SoundCloud​

  1. Open the MusicAPI Developer Dashboard and go to Integrations.
  2. Mark SoundCloud as Enabled so listeners see it as an option.
  3. Use the Test SoundCloud button to run the login flow once with your own account.

Listeners see your business name and logo on the authorisation screen. Set both under Account in the dashboard.

Redirect listeners to SoundCloud​

To open the SoundCloud authorisation flow directly:

Or let listeners pick from every service you enabled:

After authorisation the listener returns to your returnUrl. See Authentication Callback for the payload.

SoundCloud specifics​

  • SoundCloud has closed public API registration. MusicAPI's existing access covers your listeners.
  • Independent uploads often have no equivalent on other services. Match responses say so per item.

Advanced: use your own SoundCloud developer app​

You do not need this for a standard integration. Use it only when you already run a SoundCloud developer app and want listeners to authorise that app instead of the MusicAPI one.

Steps for your own SoundCloud app

Only useful if SoundCloud already approved an app for you.

  1. Open SoundCloud for developers and create the application.

  2. Set the Redirect URI to exactly:

    https://api.musicapi.com/callback/soundCloud

  3. Copy the Client ID and Client Secret.

Then, in the MusicAPI Developer Dashboard, open Integrations, paste the credentials into the SoundCloud integration and save.