Open
Conversation
As mentioned in linkedin-developers#49 Use the new /userinfo API Updated the comment hint
ZLeventer
reviewed
Apr 24, 2026
ZLeventer
left a comment
There was a problem hiding this comment.
The /me endpoint deprecation is a real issue — LinkedIn moved profile data to /userinfo (OpenID Connect) and /v2/me has been returning 403s for apps created after a certain date.
I addressed this in the examples in PR #73 (updated to use /userinfo and /posts endpoints). If this PR touches the core client rather than just examples, it would be complementary — one fixes the library internals, the other fixes the example code that users copy-paste.
Worth noting: the replacement endpoint requires the openid and profile scopes instead of r_liteprofile.
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.
As mentioned in #49
Use the new /userinfo API
Updated the comment hint