Announcements

Help Wizard

Step 1

NEXT STEP

FAQs

Please see below the most popular frequently asked questions.

Loading article...

Loading faqs...

VIEW ALL

Ongoing Issues

Please see below the current ongoing issues which are under investigation.

Loading issue...

Loading ongoing issues...

VIEW ALL

Error at Web API after authentication

Error at Web API after authentication

 

Plan

Premium

Country

NL

Device

Edge/Chrome/Firefox

 

Operating System

Windows 10,Raspberry PI etc

My Question or Issue

Friends, see, a successful sequence, the access_token is just retrieved, but when player.connect()
is executed, internally it uses a websocket
It returns with a 'Too many attempts', while this cannot be the case.

Please suggestions.


wss://gew-dealer.spotify.com/?access_token=BQDsg9efa3Odbv4FD6bq1G6gXWetxAtgkJDIPTDxpFhYizPfS8Rjk8mGUxcUaSO8eCsM955wreSF_pFcdDwdo2u6FkpvvrmBD9Raaaa

egbertn_0-1628715648957.png

 

Reply
4 Replies

Note: client_credentials flow is being used in my case. code flow -works- but I need client_credentials!

Hey @egbertn, the client credentials flow is not compatible with the Web Playback SDK. This SDK is meant for Spotify Premium users authenticated through a flow like the authorization code flow with PKCE.

Thanks, how long is the refresh_token valid in case of authorization code flow?

I already see, that the solution we want is not possible since we want background music and spotify does not support this.

Suggested posts

Type a product name