Fix API v2 parse response bodies correctly #66
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Here is the link to the new documentation: https://docs.microsoft.com/en-us/linkedin/consumer/integrations/self-serve/sign-in-with-linkedin?context=linkedin/consumer/context The api request now has to be: `GET https://api.linkedin.com/v2/me` It does not accept parameters any longer and the only scope that are valid are nor r_liteprofile and r_emailaddress which also requires its own api call
Tested it and it works. The details of waht is returned (which could be greatly improved upon) is documented here: https://developer.linkedin.com/docs/ref/v2/media-migration
CatalinaMoisuc
changed the title
Author
|
Seems that there is already a PR opened, including the same fix and upgrading to the v2 APIs: #63 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
@G-T-P has already contributed with this PR #61
He has changed the APIs to be on Linkedin V2, but the response bodies were not parsed correctly.