Is a persistent user-scoped token possible?

alsoalistair — Thu, 30 Dec 2021 01:26:14 GMT

Hey everyone, I am building a feature on my website that would render my top ten played songs from the Get User's Top Items endpoint. Right now it's working fine with my Bearer hardcoded as an environment variable, however, as soon as that expires my app completely breaks. I was curious as to if there was something similar to Twitter that will allow an app to be scoped to a user (the user that creates the application) however the tokens don't expire and are server to server only (so no OAuth flow).

I noticed the client credentials flow https://developer.spotify.com/documentation/general/guides/authorization/client-credentials/ existed, but it has a heavy emphasis on not having any user scope so naturally I haven't given this a go.

Thank you and happy new year.

Re: Is a persistent user-scoped token possible?

Peter_Schorn — Sat, 01 Jan 2022 22:40:05 GMT

The Authorization Code Flow and the Authorization Code Flow with Proof Key for Code Exchange both allow you to authorize with a specific user ("user-scoped token"). You can then refresh this token every hour without any user input. In that sense, the authorization never expires. Just read the authorization guide.

topic Is a persistent user-scoped token possible? in Spotify for Developers

Is a persistent user-scoped token possible?

Re: Is a persistent user-scoped token possible?