Browsable JSON objects may expose additional dynamic endpoints, but those endpoints should not be regarded as fixed or permanent. This endpoint acts as a root node connecting all other items in a tree-like hierarchy. It is important to emphasize the key way the Device API differs from standard Restful APIs: rather than providing multiple fixed endpoints for different resources, most resources are retrieved starting from a single endpoint. If a particular HTTP resource is unavailable, the API responds with an appropriate error message. Each object provides a local or remote reference (URI), which the application should follow if the user selects the item associated with it. Some of these are playable, like tracks and stations others are nested nodes representing categories or playlists still others are unique types of nodes with special functions. Your application then parses these objects and displays them as interface items to the user. This document contains objects representing one or more branches or ‘nodes’ of a tree. When a user selects a browsable item on the client device, the API sends an HTTP resource GET request to retrieve a JSON object document. As the user browses Amazon Music content, items such as playlists, stations, and tracks are represented by corresponding JSON objects. The Amazon Music Device API uses a REST-like model.

Also, this API does not support all the features that are supported by first-party (1P) Amazon Music applications.

In general, avoid making assumptions about how the service will behave based on observations of how the service behaves at a particular time because Amazon may make changes to the service that invalidate those assumptions. Important: Aspects of this service that are not specified in this document are not guaranteed in any way and may change in the future.

Amazon music player device