Unable to get LWA token for Music API - "An unknown scope was requested" for music::library:read

Amazon Music
1

Hello everyone,

I am currently working on integrating the Amazon Music API into a device and am facing an issue with the LWA authorization process. I’m hoping someone in
the community or from the Amazon team can point me in the right direction.

My Goal:
To obtain an LWA access token with Music API scopes (e.g., music::library:read) using the standard Authorization Code Grant flow.

The Problem:
When I redirect my user to the LWA authorization URL with scope=music::library:read, the process fails. After the user logs in, they are redirected to an
error page that says “400 Bad Request - An unknown scope was requested”.

What I’ve Tried:

  1. Testing the Client ID with a different scope: I tested the exact same Client ID with the Device Authorization Grant flow (/auth/O2/create/codepair)
    using scope=alexa:all. This test was successful. This proves that my Client ID is valid and active.

  2. Verifying the Authorization URL: My authorization URL is structured correctly according to the documentation:

1 https://www.amazon.com/ap/oa?client_id=[MY_CLIENT_ID]&scope=music::library:read&response_type=code&redirect_uri=[MY_REDIRECT_URI]
(My redirect_uri is correctly configured in the Security Profile’s “Allowed Return URLs”.)

My Suspicion:
Based on these tests, I strongly suspect that my Security Profile, while enabled for Alexa services, has not been provisioned or enabled for the Amazon
Music API. Therefore, the authorization server does not recognize any of the music::* scopes for my specific Client ID.

My Question:

  1. Is my suspicion correct? Is there a specific step required to enable a Security Profile for the Amazon Music API that I might have missed?
  2. Since the Music API is in a closed beta, is this a common issue for new developers, and what is the standard procedure to get the profile enabled?

Any guidance or help would be greatly appreciated. Thank you!

2

Hi!
Your suspicion is correct. In order to request the relevant scopes through LWA, your security profile has to be enabled by the Amazon Music team. Unfortunately, we are not onboarding any new clients at this time.
We hope to have an official timeline (date for a date) available early next year.
Thank you for your patience.

3

Hi Marco,

Thank you for the update.

Since you confirmed that Music API scopes must be explicitly enabled for each security profile, I would like to follow up on my earlier support request regarding this issue.

For reference, I previously submitted a support case (Case ID: 18946492741) requesting access to the Amazon Music Web API on behalf of Harman Lifestyle. We are currently integrating Amazon Music into our Harman smart speaker products and require the Music API scopes to begin development and testing.

As mentioned in my support case, our integration depends on:

  • Music metadata access

  • Library and playlist management

  • Browse, Views, and Playback APIs

Given that you indicated no new clients are being onboarded at the moment, could you please advise whether there is a separate process for OEM/ODM partners or Amazon-approved device manufacturers to request early enablement?
Since this is for an active, ongoing product development effort, we would greatly appreciate any guidance on the appropriate channel or Amazon Music contact to proceed.

Thank you again for your time and clarification. Any direction you can provide would be extremely helpful.

Best regards,
Simon
Harman Lifestyle