chore: LinkedIn plugin uses deprecated UGC Posts API -- migrate to Community Management API #249
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
The LinkedIn plugin uses the UGC Posts API (
/v2/ugcPosts) which LinkedIn has deprecated in favor of the Community Management API (/rest/posts).Current endpoints:
POST https://api.linkedin.com/v2/ugcPosts(publish)DELETE https://api.linkedin.com/v2/ugcPosts/{id}(delete)GET https://api.linkedin.com/v2/me(validate)LinkedIn's migration path:
POST https://api.linkedin.com/rest/postswith versioned headers (LinkedIn-Version: 202401)DELETE https://api.linkedin.com/rest/posts/{urn}GET https://api.linkedin.com/v2/userinfo(OpenID Connect)Changes needed
/rest/postswith new payload format/rest/posts/{urn}LinkedIn-Versionheader to all requests/rest/images)Impact
source/packages/plg_mokosuitecross_linkedin/src/Extension/LinkedinService.phpBranch created:
feature/249-chore-linkedin-plugin-uses-deprecated-ug