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
- Self-serve gets you write-only. "Share on LinkedIn" grants
w_member_social= post, comment, like as the member. No read scope for your own posts, comments, or analytics comes with it. - Everything read-side (comments on your posts, post analytics, follower counts) sits behind the Community Management API (CMA), which is "only available to registered legal organizations for commercial use cases only", needs a verified business email (personal emails fail), a verified org website/domain, and the app verified by that org's LinkedIn Page super admin. A solo founder with a personal-only setup does not qualify; an LLC with a Page and domain might, at LinkedIn's discretion.
- API Terms §3.1(26) forbids using the APIs "to automate posting on the LinkedIn Services." Human-approves-each-item is the defensible pattern; scheduled/unattended posting is not.
- Browser automation is prohibited by User Agreement §8.2 items 2 and 13.
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
- Posting rate limit (Share on LinkedIn): 150 requests/day per member, 100,000/day per app (UTC). share-on-linkedin
- CMA Development tier: 500 calls/app/24h, 100 calls/member/24h, no BATCH_GET, webhooks off; must finish integration within 12 months. Standard tier needs screencast + review. increasing-access
- Tokens: access tokens are 60 days. Programmatic refresh tokens (365 days) are "available for a limited set of partners" / "approved MDP partners"; self-serve apps re-run the OAuth flow (consent screen skipped if member is still logged in and token unexpired). authorization-code-flow, programmatic-refresh-tokens
- LinkedIn Page: "API Products available to individual developers must have a default page associated with them"; Page super admin approves within 30 days. So expect to need a Page even for Share on LinkedIn. help a548360
- Data storage (CMA): member social activity data max 48h, most profile data 24h; display only within the app. restricted-use-cases
Terms relevant to an AI agent (human-in-the-loop)
API Terms (last revised 2022-12-13) api-terms:
- §3.1(26): do not "Use the Content or the APIs to automate posting on the LinkedIn Services."
- §3.1(4): do not "Pre-fill content for a User (such as in a form) unless you provide a clear and prominent notice"; users must be able to edit pre-filled content. Read: AI-drafted text the member reviews, edits, and submits is the permitted shape.
- §3.1(3): do not "Request or publish information impersonating a Member."
- §4.3: refresh stored profile data only "when the Member is actually using your Application and not on an automated schedule."
- §3.1(24): no "scraping, crawling, spidering or using any other technology or software to access LinkedIn content outside the APIs."
User Agreement (effective 2025-11-03) §8.2 user-agreement:
- Item 2: "Develop, support or use software, devices, scripts, robots or any other means or processes (such as crawlers, browser plugins and add-ons or any other technology) to scrape or copy the Services, including profiles and other data from the Services;"
- Item 13: "Use bots or other unauthorized automated methods to access the Services, add or download contacts, send or redirect messages, create, comment on, like, share, or re-share posts, or otherwise drive inauthentic engagement;"
Unconfirmed
- Whether a self-serve (Share-only) app can call
/rest/socialActions/.../commentsand/rest/reactionswithw_member_socialalone. getting-access says yes ("Post, comment and like"); the Comments/Reactions pages list onlyw_member_social_feed(CMA). Needs a live test. - Whether
/rest/posts(vs legacy/v2/ugcPosts) plus Documents/MultiImage/Poll APIs work for a Share-only app, and whether edit/delete work underw_member_social. - Whether CMA still must be the only product on its app (older guidance); not stated on current pages read.
- 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.
- Developer portal product pages and app-creation form were not checked (login required).
- Absence of messaging/invite APIs is inferred from no permission being published, not from an explicit "not available" statement.