-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spotify web API authentication requirement changes #90
Comments
I'll start working on a quick fix now I'll submit through a pull request. |
Harder fix than initially thought due to architecture of JSON requests for 'DetailArtist' and 'DetailAlbum' |
#91 submitted potential fix for evaluation |
I'll take a look! |
Merged
Fixed in v0.13.3 😁 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Spotify updated web API requirements in regards to authentication. These changes were announced here on 17th Jan 2017, effective 29th May 2017 removed the ability for to make any unauthenticated calls to the API.
Currently searching appears to make unauthenticated calls to the API. A 401 error is returned with the response 'No token provided'.
Issue appears to stems from use of an old version of @jwilsson 'spotify-web-api-php' wrapper that did not include authentication token with all types of API request.
A new version of the 'spotify-web-api-php' wrapper should resolve this issue.
The text was updated successfully, but these errors were encountered: