Updated examples get_profile and create_posts in line with new API#60
Open
clockworkpc wants to merge 1 commit intolinkedin-developers:mainfrom
Open
Updated examples get_profile and create_posts in line with new API#60clockworkpc wants to merge 1 commit intolinkedin-developers:mainfrom
get_profile and create_posts in line with new API#60clockworkpc wants to merge 1 commit intolinkedin-developers:mainfrom
Conversation
Author
|
I also wrote a tidier script that focuses on the new API: |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
/meendpoint 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:
/userinfoGET endpoint instead of/meme_response.entity['sub']instead ofme_response.entity['id']There are some further differences in the names of the fields returned by the
userinfoandmeendpoints, which are reflected in the proposed changes in the exampleget_profile.py.