06-reference/research

LinkedIn API capabilities for a personal member account (what an agent can and can't do)

2026-10-17·research
linkedinapiagentsdistributionterms-of-service

LinkedIn API capabilities for a personal member account

Verified at primary sources 2026-10-17. Docs version current = li-lms-2026-09/10.

Bottom line

Capability table

Capability Possible? Scope Access level Source
Create text / article(link) / image / video post as member Yes w_member_social Self-serve (Share on LinkedIn) share-on-linkedin, getting-access
Document, multi-image, poll posts via /rest/posts Yes (organic) w_member_social Self-serve scope; but Posts API is documented under CMA. Unconfirmed that a Share-only app can call /rest/posts with these types posts-api
Organic carousel No - Impossible (sponsored only) posts-api
Edit (commentary only) / delete own post Yes, endpoints exist w_member_social (implied) Documented in CMA Posts API; self-serve availability unconfirmed posts-api
Create comment as member Doc conflict w_member_social ("Post, comment and like") vs Comments API page listing w_member_social_feed getting-access says self-serve; Comments API lists CMA-only scope getting-access, comments-api
Reply to a comment (nested, parentComment) Yes w_member_social_feed Restricted (CMA) comments-api
React / like Yes w_member_social (like) / w_member_social_feed (Reactions API) Same conflict as comments reactions-api
List own posts (/rest/posts?author=urn:li:person) Yes r_member_social Restricted, "approved users only" posts-api
Read comments / reactions on own posts Yes r_member_social_feed Restricted, "granted to select developers only" comments-api
Post analytics (impressions, reach, reactions, comments, reshares, saves, sends, link clicks, followers gained, profile views from post) per-post or aggregate Yes (memberCreatorPostAnalytics) r_member_postAnalytics CMA (API ≥202506); legal-entity vetting post-statistics, increasing-access
Follower count, lifetime + daily (memberFollowersCount) Yes r_member_profileAnalytics CMA (API ≥202504) follower-statistics
1st-degree connection count Yes (count only) r_1st_connections_size CMA or Advertising API increasing-access
Name/headline/photo, email Yes profile, email (OIDC) Self-serve getting-access
Home feed / other people's posts No - Impossible ("No Social Feeds"; feed read scope restricted to select developers) restricted-use-cases
DMs / messages No none listed Impossible (no permission published) getting-access
Connection invites / connection list No none listed (only count scope) Impossible increasing-access

Limits, tokens, app requirements

Terms relevant to an AI agent (human-in-the-loop)

API Terms (last revised 2022-12-13) api-terms:

User Agreement (effective 2025-11-03) §8.2 user-agreement:

Unconfirmed

  1. Whether a self-serve (Share-only) app can call /rest/socialActions/.../comments and /rest/reactions with w_member_social alone. getting-access says yes ("Post, comment and like"); the Comments/Reactions pages list only w_member_social_feed (CMA). Needs a live test.
  2. Whether /rest/posts (vs legacy /v2/ugcPosts) plus Documents/MultiImage/Poll APIs work for a Share-only app, and whether edit/delete work under w_member_social.
  3. Whether CMA still must be the only product on its app (older guidance); not stated on current pages read.
  4. Whether a solo LLC with a Page + domain would pass CMA vetting for an "Executive Management"-style personal-profile use case. The review page lists that use case, so it is not ruled out, but approval is discretionary.
  5. Developer portal product pages and app-creation form were not checked (login required).
  6. Absence of messaging/invite APIs is inferred from no permission being published, not from an explicit "not available" statement.