Skip to main content

Spotify

MusicAPI holds the Spotify 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 Spotify developer account, and you never store Spotify tokens.

Enable Spotify​

  1. Open the MusicAPI Developer Dashboard and go to Integrations.
  2. Mark Spotify as Enabled so listeners see it as an option.
  3. Use the Test Spotify 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 Spotify​

To open the Spotify 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.

Spotify specifics​

  • Spotify shows "MusicAPI wants to access your data" style consent copy with your business name and logo, taken from your dashboard account.
  • Podcast and audiobook objects are out of scope. Only tracks, albums, artists and playlists are read or written.
  • Since February 2026 Spotify's own Development Mode is capped at 5 users and needs a Premium account. That limit does not apply to listeners authorising through MusicAPI.

Advanced: use your own Spotify developer app​

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

Steps for your own Spotify app

  1. Log in to the Spotify for Developers Dashboard and click Create an App.

  2. Set the Redirect URI to exactly:

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

  3. Open the app's Settings page and copy the Client ID and Client Secret.

Spotify API Credentials

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