Can't re-add album via API after removing it on Amazon Music Web (PUT /me/library/albums)

Amazon Music
1

Hi Amazon Music API team / community,

I’m seeing an inconsistency between the public Amazon Music Web API library endpoints and the behavior of the Amazon Music web UI (music.amazon.co.jp). After removing an album via the web UI(/my/library), I can no longer re-add it via the public library API, even though the PUT call returns SAVED.

Environment

  • User tier: PRIME

  • Region/market: JP

Steps to Reproduce

  1. Ensure album is not currently in library.
    example:
    https://music.amazon.co.jp/albums/B0CM9HHZPD

  2. Add to library (PUT /v1/me/library/albums/{albumId}), returns SAVED.

  3. Remove the album via web UI (“Remove from library”).
    https://music.amazon.co.jp/my/albums

  4. Add to library (PUT /v1/me/library/albums/{albumId}), returns SAVED.

  5. Verify:
    GET /v1/me/library/albums?albumIds={albumId}
    or
    GET /v1/views/library/albums

Expected behavior:
The album deleted from the Web UI have been added back to the library.

Actual behavior:
The album deleted from the web UI will no longer be able to be added to the library permanently via the Add to library (PUT /v1/me/library/albums/{albumId}).

Summary of the issue

  1. Public API path works when deletion is done via API

  • PUT /v1/me/library/albums/{albumId} → response indicates saveState: "SAVED"

  • DELETE /v1/me/library/albums/{albumId}

  • Repeating PUT → DELETE → PUT works reliably (I tested with album B0CM9HHZPD).

  1. Public API breaks when deletion is done via the Amazon Music web UI

  • PUT /v1/me/library/albums/{albumId} succeeds (returns SAVED)

  • I then remove the album from the library using the Amazon Music website (music.amazon.co.jp).

  • After that, re-running PUT /v1/me/library/albums/{albumId} still returns saveState: "SAVED", but the album is not actually saved:

    • It does NOT appear in GET /v1/me/library/albums, GET /v1/views/library/albums

  • Once this happens, I cannot recover the state via the public library endpoints (it remains “not saved” from GET/Views perspective).

This behavior occurs for both albums and tracks (tracks can be saved once, but after removing via web UI, subsequent library PUT no longer results in a saved state observable via GET).

Questions

  1. Is there a known issue where PUT /me/library/albums returns SAVED but does not persist/reflect in GET /me/library/albums ?

  2. If web UI removal sets a state that blocks re-adding via public API, is there an officially supported way to clear/reset it?

Thanks for any guidance or confirmation on expected behavior / workaround.

2

Hi @sukezane,

Thank you for the detailed report. This is a known issue we’re actively tracking. I’ll update this thread once we have it resolved. Thank you for your patience!

-Vic