Updated examples get_profile
and create_posts
in line with new API
#60
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.
The current examples use the
/me
endpoint and try to identify the profile by the following URN string:f"urn:li:person:{me_response.entity['id']}
.However, I found that even though I have a valid 3-legged-token with the necessary scopes enabled, I was getting an error.
I believe that the most recent changes to the LinkedIn API require the following changes:
/userinfo
GET endpoint instead of/me
me_response.entity['sub']
instead ofme_response.entity['id']
There are some further differences in the names of the fields returned by the
userinfo
andme
endpoints, which are reflected in the proposed changes in the exampleget_profile.py
.