Spotify 
Section titled “Spotify ”Music Assistant has full support for Spotify media listing and playback.
NOTE
A Spotify Premium account is required for this music source. Free accounts will not work.
NOTE
Spotify has made it clear to third party products that lossless support is not to be persued.
Features
Section titled “Features”| Subscription FREE | No |
| Self-Hosted Local Media | No |
| Media Types Supported | Artists, Albums, Tracks, Playlists, Podcasts, Audiobooks |
| Recommendations Supported | No |
| Lyrics Supported | No |
| Radio Mode | Yes |
| Maximum Stream Quality | Lossy, OGG Vorbis (320kbps) |
| Login Method | OAuth |
- Searching the Spotify catalogue is possible
- Items in your Spotify library (including the Liked Songs playlist) will be added to the Library in Music Assistant
- Adding an item from Spotify to the Music Assistant Library will also add it to “Your Library” in Spotify
- Marking an item as a favourite in Music Assistant will also add it to the MA Library and “Your Library” in Spotify
- Multiple Spotify accounts can be added. All playlists from all accounts will be shown. If a playlist is selected for playback the source Spotify account will be used
Configuration
Section titled “Configuration”- The Spotify source can only be configured from a device which is on the same subnet as the MA server (and not via a VPN)
- Configuration is done with an OAuth callback. Clicking on the AUTHENTICATE WITH SPOTIFY button will open a new tab where permission can be given for MA to access the logged in account
- Once the intial authentication is done a new option will appear towards the bottom of the view titled
Developer Token. It is advantageous to add a personal Client ID as this will speed up access to the Spotify API and should eliminate rate limiting. How to obtain a Client ID is explained here. When entering the information in the various fields the only mandatory item is the REDIRECT URL which must be set tohttps://music-assistant.io/callback. Using a personal Client ID is optional but rate limiting and streaming errors may be seen in the log if it is not supplied - If a personal Client ID is added then click on the large button AUTHENTICATE DEVELOPER SESSION
- Finally the SAVE button must be pressed on the Spotify settings page. If the device being used kills the MA frontend before this is done then the source setup will fail (Use a different, typically non-mobile, device if this happens)
Settings
Section titled “Settings”Refer to the Library Import Control settings.
Known Issues / Notes
Section titled “Known Issues / Notes”- Due to restrictions with Spotify’s API, only Spotify Premium accounts are supported (including Duo and Family). Free accounts will not work
- Upon first saving of the source a check is done for Audiobook support within the account. If the check is successful then additional Audiobook related options will be seen when revisiting the source’s settings
- After adding the developer token there is then two sessions created to a single spotify source and MA routes the requests appropriately. For example, playlists are requested via the MA global token (which is rate limited but allows playlist retrieval) while other items are retrieved via the dev token. Search is done using the dev token by default as otherwise it is very slow. Playing and browsing playlists is routed through the global token to the originating source (useful when multiple Spotify accounts are added)
- The Spotify API does not support the provision of recommendations
- The Spotify API does not return genre information