topic Re: Invalid Token Scopes (Web Playback SDK) in Spotify for Developers

Invalid Token Scopes (Web Playback SDK)

temlabs — Wed, 30 Oct 2024 11:20:11 GMT

Plan

Premium

Country

My Question or Issue
I'm able to successfully generate an access token for the following scopes:
playlist-read-private streaming app-remote-control user-modify-playback-state user-read-playback-state user-read-recently-played user-read-private

However, when using said access token in the web playback SDK, I consistently get an "Invalid token scopes" when attempting playback.

The access token looks like the following:
BQBLSGZxJxOlIcI_yxo_shQzuMeZD_1Qz66XcOXJ8iz0Q7uErq-qcJ_AiC2JJwc37by3z4uscjhsfQWAg7OxCW1ENdsnwvTvknYBletZI84uIG0PAy7hTZhObFiINdv4tAxMTJQZgQxMj0B_SubF4X4g61m_PNkWPpoDbKBL-VHGCu7FSJcdJQizWh0mpdXZX0tWLhrAPd0yRgFqE3HwOsvY6GtT7aRW

And i'm even able to transfer playback to my device and get the device ID.

I'm at a complete loss as to what's wrong - any help would be massively appreciated!

Re: Invalid Token Scopes (Web Playback SDK)

tomjaimz — Wed, 30 Oct 2024 14:07:50 GMT

For playback you only really need the streaming and user-read-private scopes, and you have both of those. Your scopes as listed are correct, have you re-authenticated your user (got entirely new tokens - access and refresh) since you updated your scopes? When you get a token it helps to save all the token data somewhere, as the token response itself will also show the scopes of the token.

Re: Invalid Token Scopes (Web Playback SDK)

tomjaimz — Wed, 30 Oct 2024 14:13:30 GMT

Oh, actually you are missing user-read-email I think that's also required.

Re: Invalid Token Scopes (Web Playback SDK)

temlabs — Wed, 30 Oct 2024 20:50:14 GMT

Hey! I was so looking forward to telling you this was the solution, but unfortunately not - the issue persists with the added user-red-email scope. I can confirm that all of the scopes are being applied, based off the response from the token endpoint.

What's so strange is that I get a 204 response, when I use my access token to call the play endpoint with the web API, but I get either "Playback error" or "Invalid token scopes" (or both) from the Web Playback SDK. Do you have anymore thoughts? What could I show you to make this easier?

Re: Invalid Token Scopes (Web Playback SDK)

tomjaimz — Wed, 30 Oct 2024 22:41:29 GMT

I would have to see your code to understand what's happening for you. I can replicate getting an authentication error of "Invalid token scopes" if I'm missing all three of the needed scopes, but with them it does not give an error.

Did you definitely create a new token by going through the authentication process after adding the user-read-email scope?

Re: Invalid Token Scopes (Web Playback SDK)

temlabs — Thu, 31 Oct 2024 09:55:08 GMT

Thanks tomjaimz,

I've sent you a pm with links to code. We can share anything discovered back here if it'll help someone else. And yes, definitely.

Re: Invalid Token Scopes (Web Playback SDK)

manikanta20 — Mon, 23 Jun 2025 04:40:34 GMT

Hello tomjaimz

i am also facing the same issue

'user-read-private',

'playlist-read-private',

'playlist-read-collaborative',

'streaming',

'user-read-birthdate',

'user-read-email'

these are scopes i have but still it is showing