Skip to content

Commit 8c651b6

Browse files
authored
Recommend use of clientid
1 parent f45239e commit 8c651b6

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/music-providers/spotify.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ Music Assistant has full support for Spotify media listing and playback.
1515

1616
## Configuration
1717
- You can only configure the Spotify provider from a device which is on the same subnet as the MA server (and not via a VPN)
18-
- Entering a personal ClientID may speed up access to the Spotify API or eliminate rate limiting if that is encountered. How to obtain a ClientID is explained [here](https://developer.spotify.com/documentation/web-api/concepts/apps). When entering the information in the various fields the only mandatory item is the REDIRECT URL which must be set to `https://music-assistant.io/callback`. Using a personal ClientID is optional
18+
- It is strongly recommended that a personal ClientID is used as this will speed up access to the Spotify API and should eliminate rate limiting. How to obtain a ClientID is explained [here](https://developer.spotify.com/documentation/web-api/concepts/apps). When entering the information in the various fields the only mandatory item is the REDIRECT URL which must be set to `https://music-assistant.io/callback`. Using a personal ClientID is optional but rate limiting and streaming errors will likely be seen in the log if it is not supplied
1919
- After deciding whether to use a personal ClientID, click on the large button AUTHENTICATE WITH SPOTIFY
2020
- A new window will open where you must allow Spotify to connect to Music Assistant
2121
- You must then come back to MA and press SAVE in the Spotify settings page. If the device you are on kills the MA frontend before this is done then the provider setup will fail (Use a different, typically non-mobile, device if this happens)

0 commit comments

Comments
 (0)