Authentication
The images below are for Edge, but other browsers, especially Chromium-based should be very similar.
In order to obtain your Deezer ARL, log into https://www.deezer.com/. Then open Developer Tools, and head to the Application tab. In the sidebar, open the dropdown list for Cookies and there should be an subitem https://www.deezer.com/. Click on the subitem and to find the the arl value, which should be 192 characters long. Note that you should open the dropdown for the Cookies section, not click on it.
If you can log in with an email (not username) and password, use that directly. Qobuz id and tokens are an alternative method of authentication.
To obtain a Qobuz id and token, log into https://play.qobuz.com/ and open Developer Tools. Head over the Application tab, open the dropdown list for Local Storage and click on the subitem https://play.qobuz.com. You should then click on the localuser JSON object in the viewing window, where you can find the fields id (7 digits) and token (86 characters).
Every id and token (your user account) is tied to an app id and secret (qobuz web player values).
However, the web player changes app id/secret every once in a while. This changes the id/token for all users. Before this release, you would need to go back into the browser to get your new id/token values.
To get around this, you can now save an app id/secret alongside your id/token. Now, even if the app id/secret changes, your old id/token remains working with the old app id/secret that you saved.
TLDR: If you don't want to manually get id/token values every once in a while, press Capture Current App ID/Secret on the same day you get your id/token from the browser. Remember to hit Save.
FluentDL will automatically grab an access token from your local cookies. However, if you are not logged into the web player or there are auth issues, you may resort to developer API tokens.
This method is guaranteed to work and is more reliable.
Unfortunately, as of Feb 2026, these tokens (client ID and client secret) are only usable when you have an active Spotify Premium subscription.
An app provides the Client ID and Client Secret needed to request an access token.
To create an app, go to your Dashboard, click on the Create an app button and enter the following information:
- App Name: enter any value you wish
- App Description: enter any value you wish
- Redirect URI: Enter the value found in FluentDL settings tab under Spotify:
http://127.0.0.1:5543/callback -
- Which API/SDKs are you planning to use: select Web API
-
In order to request the access token you need to get your Client_ID and Client Secret:
- Go to the Dashboard
- Click on the name of the app you have just created
- Click on the
Settingsbutton (upper right)
The Client ID can be found here. The Client Secret can be found behind the View client secret link.
Then, you may enter these two values into FluentDL.
For more details on obtaining these tokens, visit the official documentation.
There are two ways FluentDL can access spotify:
- Official API
- Web player workaround
The second method does not require any setup and works out of the box. However, these are the downsides:
- Has a higher chance of breaking when the web player changes.
- ISRCs are not available and are looked up with third-party sources during conversions. While this is decently fast, it is another point of failure and can have rate limiting issues as they must be looked up individually per track (1000 tracks = 1000 lookups)
The official API search/playlist responses come with the ISRCs directly and also support private playlists if you setup the redirect URI. However, these are the downsides:
- Requires you to hold a Spotify premium subscription.
- You can only load playlists that you own or are a collaborator of.
If you want to load private playlists, remember to turn on the private playlist setting in the setting page under Spotify. This will attempt to use the official API to load playlists first before falling back to the web player workaround. Thus, if you already have Spotify premium, it doesn't hurt to use the official API.
