API v2 authorization problem

[ForMiSoft]

API doesn't work even in the Tidal's web UI (please see the included screenshot bellow).
In my app I'm able to get Access Token from https://auth.tidal.com/v1/oauth2/token, but that's all we can do, everything else isn't working because there's an authentication/authorization problem on the Tidal's side.

[aliaksei-taliuk]

Hey @NendosColl, thank you for reaching out.

We are not aware of any major issues with our V2 API. Our nightly regression tests pass for all currently available endpoints.

WRT to the specific issue you are facing, the error response you are seeing is most likely correct. I.e. the access token issued to the API Explorer has probably expired.

The API Explorer doesn't refresh access tokens on your behalf, but it currently requires you to re-authorize access to your resources when the access token expires. To do this, follow these steps:

1. Press "Exit API Explorer Mode" at the top-right corner
2. Press "Authorize" button
3. Press "Logout" under the PKCE section
4. Authorize again using PKCE

We acknowledge that this process is a bit tedious, and can probably be streamlined a bit, something we will look into down the road.

[ForMiSoft]

Hey @NendosColl, thank you for reaching out.

We are not aware of any major issues with our V2 API. Our nightly regression tests pass for all currently available endpoints.

WRT to the specific issue you are facing, the error response you are seeing is most likely correct. I.e. the access token issued to the API Explorer has probably expired.

The API Explorer doesn't refresh access tokens on your behalf, but it currently requires you to re-authorize access to your resources when the access token expires. To do this, follow these steps:

1. Press "Exit API Explorer Mode" at the top-right corner
2. Press "Authorize" button
3. Press "Logout" under the PKCE section
4. Authorize again using PKCE

We acknowledge that this process is a bit tedious, and can probably be streamlined a bit, something we will look into down the road.

Hi, thank you for your response. But my problem still persists.

When I try to Authorize, there are two "Authorize" buttons (???), the right one does nothing and the left one responds with an error.

Any other ideas?

[aliaksei-taliuk]

Hi again @NendosColl ! Could you please:

1. Try to sign in into https://developer.tidal.com/
2. Go to Dashboard
3. Choose the application you're using
4. Go to App Settings
5. Ensure your app is allowed to claim these scopes (see Scopes section down below). Add 'user.read', 'entitlements.read', 'playlists.read' if not.

[ForMiSoft]

I really appreciate your help, but that wasn't the culprit.

[ForMiSoft]

Wow, I tried it again and this time it worked. I don't know if you did something but thank you very much for your help, I almost gave up.

[stefanmoro]

Glad to hear you got it working. Just another comment, I can see you have no redirect URIs configured for your app. Redirect URI is mandatory in order for you to be able to use authorization code flow in your client. Please read through the authorization documentation to learn more.

[ForMiSoft]

My joy was a little premature. Now it works in the Web UI, but my app is still getting errors when I try to obtain my playlists.

First I try to get an Access Token.

It works without a problem. Is it ok that the returned scope is empty?

Then I try to use that Access Token to get my playlists.

It responds with an error 401 - Unauthorized

Please let me know what I'm doing wrong. Should I try to use a refresh token? If yes, how can I get that refresh token from my Windows desktop app?

[ForMiSoft]

I can see you have no redirect URIs configured for your app. Redirect URI is mandatory in order for you to be able to use authorization code flow in your client.

My client is a Windows desktop app. I think that a redirect URI isn't very useful for an app that doesn't run on a web server.

[ForMiSoft]

I have a strong suspicion that there is no option in the API v2 to use its authorization flow from a Windows desktop app.

[aliaksei-taliuk]

Hi @NendosColl .

Please take a look here: https://github.com/orgs/tidal-music/discussions/6#discussioncomment-10392749

As it was mentioned there we're currently discussing the possibility to open up some of Playlist API endpoints (Public Playlists only) for the Client Credentials flow. Private playlists or '/me' information will always work only under PKCE.

Best regards,
Aliaksei