Catch additional prams in user details response #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When the access token has more scope of access, the user details endpoint will return additional data than catch in the function userDetails.
Additional params includes following
Also we can use these details to check if the user has premium account.
Response of user details request when access token has more scopes including following
stdClass object {
birthdate => (string) 1984-03-23
country => (string) GB
display_name => null
email => (string) [email protected]
external_urls => stdClass object {
spotify => (string) https://open.spotify.com/user/xxx
}
followers => stdClass object {
href => null
total => (int) 0
}
href => (string) https://api.spotify.com/v1/users/xxx
id => (string) xxx
images => array(1) (
[0] => stdClass object {
height => null
url => (string) https://profile-images.scdn.co/images/userprofile/default/xxx
width => null
}
)
product => (string) premium
type => (string) user
uri => (string) spotify:user:xxx
}