v1/me/following getting 403s all of a sudden

[shlkm]

Context: app is > 5 years old, thousands of users, no code change recently.

For an extremely large portion of users, I'm getting a 403 Forbidden response when I hit the v1/me/following endpoint. This seems to have started yesterday and is practically happening for all users.

The app has the correct scopes, I'm 100% certain. A lot of those users have been on the app and connected Spotify for months. As I said, nothing in the app code has changed, let alone in the authorization flow.

[cjtolj]

This is still happening? Guess I was right that Spotify doesn't care, glad I got my workaround.

[senti3ntB3ing]

Same, getting the error on a friends connection to my app when I know for a fact he has it authorized (literally viewing it in his apps in his account, watched the token get stored). Works perfectly for my own accounts access token tho, just not his.

[olli408]

If someone else is out of the loop and finds this thread because of issues with the audio_features API calls failing because of 403. It's sadly because Spotify has restricted their API https://developer.spotify.com/blog/2024-11-27-changes-to-the-web-api

[daxtylos]

olli408 really really thank you i ve been trying to find a solution to fix my code that was running perfectly but suddenly stopped.If anything changes please give me a notice 🙂