mirror of
https://github.com/jwilsson/spotify-web-api-php.git
synced 2026-04-26 23:45:49 +03:00
[GH-ISSUE #264] Access type with mode "Client Credentials" #191
Labels
No labels
bug
docs
enhancement
enhancement
enhancement
feedback wanted
good first issue
help wanted
help wanted
help wanted
invalid
pull-request
question
question
upstream
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotify-web-api-php#191
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @j3-solutions on GitHub (Jul 17, 2023).
Original GitHub issue: https://github.com/jwilsson/spotify-web-api-php/issues/264
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!
@jwilsson commented on GitHub (Jul 17, 2023):
Hey!
Yes, the client credentials authorization mode is supported in the library 😄 Check out the docs on it here.
@johnanortega commented on GitHub (Jul 18, 2023):
Hi!.
Oh, thank you. I apologize for not having read all the documentation properly :-(