Currently, if I'm not mistaken, the use of the project would be based solely on the 'authorization code flow' client authorization mode, focused on third-party usage from a web environment using a browser with the account usage acceptance window.
I've been thinking about forking the project to include the 'client credentials' authorization mode in order to implement an API that relies on calls to Spotify through your project. This way, there would be no need to use third-party account login windows (since only the developer's account would be used) and the RefreshToken would not be necessary at any time.
Have you considered including this mode in the project?
Hello!.
Currently, if I'm not mistaken, the use of the project would be based solely on the 'authorization code flow' client authorization mode, focused on third-party usage from a web environment using a browser with the account usage acceptance window.
I've been thinking about forking the project to include the 'client credentials' authorization mode in order to implement an API that relies on calls to Spotify through your project. This way, there would be no need to use third-party account login windows (since only the developer's account would be used) and the RefreshToken would not be necessary at any time.
Have you considered including this mode in the project?
Thank you and congratulations on the project!