Restrictions: explicit using client credentials

[fallobst22]

Since recently, when using an access token obtained via the client credentials flows, using the v1/tracks/{id} Endpoint for a song which is marked as explicit returns the following data when supplying a market parameter:

Spoiler

...
"is_playable": false,
"restrictions": {
    "reason": "explicit"
},
...

When using a token obtained via a different flow, eg implicit, the response for an identical requests is as expected, with is_playable: true and no restrictions key.

How can i avoid this behavior? I could not find any information about this change in the api documentation.

[Hubo]

Hey @fallobst22, help's here!

Hmm, let's see what could be happening here. Could you check if your Spotify account settings allow explicit songs to be played? You can check this in the Preferences in your Spotify app. Let me know how you get on!

Have a great day,

Hubo

[fallobst22]

Hello and thanks for trying to help!

Playing explicit songs is enabled in the account in which the app is registered.