Who Me Too'd this topic

Restrictions: explicit using client credentials

Casual Listener

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:


"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.

Who Me Too'd this topic