Check if Users Follow Playlist API doesn’t work

[itsuygi]

The API endpoint for checking if a user follows a playlist doesn’t work as expected.

My target was checking if a user follows my playlist.

I tried it using scopes & accounts service however the response was always false unless I check if the token owner follows a playlist.

For example, I can only get true if the current user (token owner) follows a playlist. When I want to check if somebody else follows, the response is always false.

Also, I tried this with the both web player’s and developer access token with Postman but they both didn’t work.

So, I made a glitch website using Spotify’s github repo for authorizing and using the api. However even with accounts service, the response was always false.

Is this api deprecated? If it doesn't, It should be fixed.

The Scopes I use: playlist-read-private user-read-private playlist-modify-private playlist-read-collaborative playlist-modify-public user-follow-read user-read-private

[Ximzend]

Did you add the users to your app's allowlist? - https://developer.spotify.com/documentation/web-api/concepts/quota-modes

[itsuygi]

No, I didn’t. I want to check if they follow my playlist. So I should add them?

[Ximzend]

For testing purposes, yes. To make it public, you should request a quota extension.

[itsuygi]

I’ve added my other account to allowlist however even if I follow my playlist, I can’t see it from my main. Only thing changed was I could access the API from my other account.

[Ximzend]

Then I misunderstood your question. You can only check if the authenticated user follows a playlist.

[itsuygi]

Well, this doesn’t make sense. Then why the endpoints wants userids? Spotify seems they keep ignoring this endpoint and not touchs it. I think it just works when you add the followed playlist to your profile

[Ximzend]

You're right. This behaviour and what I said doesn't make sense. (I think I mixed up the documentation of a different API.)

This API doesn't require authorization scopes, so it must support client credentials, without the need of the authorization of the user.