Source for every API claim: [[06-reference/research/2026-10-17-linkedin-api-capabilities-personal-member]] (checked at learn.microsoft.com and linkedin.com/legal on 2026-10-17).
Access tiers: Self-serve = "Share on LinkedIn" product, any dev app (needs a LinkedIn Page associated). CMA = Community Management API, legal organization only (business email, verified domain, Page super admin), reviewed case by case; "Executive Management" use case covers a person's own profile. None = no API exists.
Features (from his messages: create, engage, monitor; partner not bot)
| # | Feature | API route | Tier | Gap filler |
|---|---|---|---|---|
| C1 | Draft the daily post (Ship 30) | n/a (drafting) | - | - |
| C2 | He approves with one tap, Ray publishes | Posts API, w_member_social | Self-serve | - |
| C3 | Image / video posts | Images/Videos API | Self-serve | - |
| C4 | Document (PDF carousel) and poll posts | /rest/posts + Documents API | Unconfirmed for self-serve (test) | he posts |
| C5 | Edit or delete a post | Posts API | Unconfirmed for self-serve | he edits |
| E1 | See new comments on his posts | r_member_social_feed | CMA | browser read |
| E2 | Reply to a comment on his post (he approves each) | w_member_social_feed (nested) | CMA | browser |
| E3 | Comment on someone else's post he shares | Comments API; docs conflict w_member_social vs _feed | Test | browser / he posts |
| E4 | Like comments / posts | Reactions API, same conflict | Test | skip |
| E5 | Read a post he shares (text, comments) | none (no feed access) | None | browser read |
| E6 | DMs, connection invites | none | None | he does it (Ray drafts) |
| M1 | Per-post impressions, reach, reactions, comments, saves, link clicks | memberCreatorPostAnalytics, r_member_postAnalytics | CMA | browser read of analytics page |
| M2 | Follower growth (daily) | memberFollowersCount, r_member_profileAnalytics | CMA | browser read |
| M3 | Weekly "what worked" note | built on M1/M2 | - | - |
| M4 | Published-vs-draft diff (writing rules loop) | list own posts, r_member_social | CMA | browser read |
Rules that bound the design
- API Terms §3.1(26): no "automate posting". Every post and reply waits for his explicit approval; nothing on a schedule without it.
- API Terms §3.1(4): pre-filled content needs a clear notice and must be editable (approval page shows the text and lets him edit).
- User Agreement §8.2 items 2 and 13 name browser plug-ins, scraping, and automated "create, comment on, like" directly. The browser route is inside that wording, not a gray zone. Enforcement mostly targets volume, but the risk sits on his main account.
- CMA stores member social activity 48h max: Ray keeps derived weekly numbers, not raw pulls (confirm the analytics carve-out on approval).
- Self-serve tokens last 60 days with no refresh token: re-consent every ~2 months (one tap if logged in).
Recommended path (Ray, awaiting his read)
- Create a dev app tied to a Ray Data Co Page, one OAuth grant: unlocks C2/C3 now (this is the open HQ decision 2026-09-04-linkedin-write-rail-oauth-unblock).
- Day one test: does self-serve allow comments (E3), docs/polls (C4), edit (C5)?
- Apply for CMA under the RDCO LLC, Executive Management use case: unlocks E1, E2, M1, M2, M4. LinkedIn's call; weeks, not days.
- Until CMA: browser for READING only (E1, E5, M1), low volume, he posts replies himself or Ray types it in and he taps Reply. Ray does not click post/like through the browser unless he accepts that risk explicitly.