Amazon Music

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

Enable Amazon Music

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

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

Amazon Music specifics

• The Amazon Music API is a closed beta. MusicAPI's partner access covers library reads and writes for your listeners.
• Prime, Unlimited and HD tiers expose different catalogues. MusicAPI reads whichever the listener's account allows.

Advanced: use your own Amazon Music developer app

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

Steps for your own Amazon Music app

Your own Security Profile only lets listeners log in with Amazon. Library access still requires an Amazon Business Development agreement, which MusicAPI already holds.

1. Log in to the Amazon Developer Portal and click Create New Security Profile.

2. Click Save, open Web Settings and add this entry to Allowed Return URLs:

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

3. Copy the Client ID and Client Secret.

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