Skip to content
Skills Library
Programming · Tool integration

linkedin-api

/linkedin-api

Expert reference for the official LinkedIn API (docs snapshot 2026-10-29, API version 202610). Use for any question about LinkedIn OAuth and tokens, getting API access or an "API key", posting to LinkedIn programmatically (Posts API, images, documents, polls, comments, reactions), post and page analytics, Community Management tiers and rate limits, API versions and error codes, webhooks, data-storage and AI-use rules, plus a map of Ads, Lead Sync, Conversions, Learning, Sales Navigator, Talent and Compliance APIs.

Licence
MIT
Last repository change
28.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
11
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Expert reference for the official LinkedIn API (docs snapshot 2026-10-29, API version 202610). Use for any question about LinkedIn OAuth and tokens, getting API access or an "API key", posting to LinkedIn programmatically (Posts API, images, documents, polls, comments, reactions), post and page analytics, Community Management tiers and rate limits, API versions and error codes, webhooks, data-storage and AI-use rules, plus a map of Ads, Lead Sync, Conversions, Learning, Sales Navigator, Talent and Compliance APIs.

Triggers from the description

API key
Original author description

Expert reference for the official LinkedIn API (docs snapshot 2026-10-29, API version 202610). Use for any question about LinkedIn OAuth and tokens, getting API access or an "API key", posting to LinkedIn programmatically (Posts API, images, documents, polls, comments, reactions), post and page analytics, Community Management tiers and rate limits, API versions and error codes, webhooks, data-storage and AI-use rules, plus a map of Ads, Lead Sync, Conversions, Learning, Sales Navigator, Talent and Compliance APIs.

How it works

  1. How to use this skill
  2. Ten facts that decide most questions
  3. Related skills in this toolkit
Original SKILL.md headings · 39 lines, 575 words
SKILL.md preview
---
name: linkedin-api
description: Expert reference for the official LinkedIn API (docs snapshot 2026-10-29, API version 202610). Use for any question about LinkedIn OAuth and tokens, getting API access or an "API key", posting to LinkedIn programmatically (Posts API, images, documents, polls, comments, reactions), post and page analytics, Community Management tiers and rate limits, API versions and error codes, webhooks, data-storage and AI-use rules, plus a map of Ads, Lead Sync, Conversions, Learning, Sales Navigator, Talent and Compliance APIs.
---

# LinkedIn API knowledge

Distilled from the whole of https://learn.microsoft.com/en-us/linkedin/ (about 580 pages read on 2026-10-28/29), written in original words with the source page named in every file. LinkedIn changes this API every month, so treat numbers, limits and permission names as "true on 2026-10-29" and re-check the linked page before relying on anything that costs money, risks an account or ships to production.

## How to use this skill
1. Find the topic in the table, open that one file in `references/` (never load them all).
2. Tell the user which documentation page a fact came from.
3. If something is not covered, search `references/09-page-index.md` for the right page and read the live page. Say plainly when you could not verify.
4. Never ask the user to paste a client secret, token or password into the chat. Credentials go into their own terminal (`li-auth setup`).

| Question about... | Open |
|---|---|
| Getting access, "API key", products, scopes, OAuth flows, tokens, refresh, secrets, tiers | `references/01-access-and-auth.md` |
| Request format: base URLs, headers, Rest.li 2.0 encoding, versions, methods, errors, rate limits, webhooks | `references/02-api-mechanics.md` |
| Posting and engagement: text, image, multi-image, video, document, poll, article, reshare, edit, delete, mentions, comments, reactions | `references/03-posting-and-engagement.md` |
| Analytics: post/profile/page/follower/video numbers, notifications | `references/04-analytics.md` |
| Sign in with LinkedIn, Share on LinkedIn, plugins, Verified, Live | `references/05-sign-in-and-share.md` |
| What is allowed: restricted uses, data storage limits, AI policy, app review, Development vs Standard tier | `references/06-rules-and-policies.md` |
| Ads, Lead Sync, Conversions, Matched Audiences, Events, Learning, Sales Navigator, Talent, Compliance | `references/07-other-programs.md` |
| Something is failing | `references/08-troubleshooting.md` |
| "Where is the page about X?" | `references/09-page-index.md` |
| Version table, sunsets, recent changes, legacy-to-new API map | `references/10-versions-and-changes.md` |

## Ten facts that decide most questions
1. **There is no "LinkedIn API key".** You create a developer *app* (client ID + client secret), then each person signs in with OAuth 2.0 and the app receives an access token (60 days).
2. **Fastest path to posting from your own software:** add the open products "Share on LinkedIn" (`w_member_social`) and "Sign in with LinkedIn using OpenID Connect" (`openid profile`) to an app. No review needed.
3. **Reading post numbers** needs the Community Management API (scope `r_member_postAnalytics`): reviewed, Development tier first, and it **must be the only product on its own app**.
4. **Two base paths:** `https://api.linkedin.com/rest/` (versioned, needs `Linkedin-Version: YYYYMM` and `X-Restli-Protocol-Version: 2.0.0`) and the older `/v2/`. Latest version is `202610`; each version lives 12 months.
5. **Development tier limits:** 500 calls/app/day and 100 calls/member/day, no BATCH_GET, 12 months to apply for Standard or access is removed. Limits reset at midnight UTC.
6. **Member post analytics is one post and one metric per call.** No batching. Page (organization) share statistics can take several posts in one call.
7. **Reading other people's posts or comments is not possible** (`r_member_social` is closed to everyone).
8. **Posting returns 201 with an empty body;** the new post id is in the `x-restli-id` header.
9. **Stored data has clocks:** members' social activity 48 hours, other members' profile data 24 hours, Page reporting data one year.
10. **AI rules:** LinkedIn recommends no automated posting of AI-written content without a person involved and prohibits using API-retrieved member content as AI input except in narrow cases. Build an approval step. See `references/06-rules-and-policies.md`.

## Related skills in this toolkit
`linkedin-api-setup` (guided credentials), `linkedin-publisher` (post with approval), `linkedin-writer`, `linkedin-post-check`, `linkedin-comments`, `linkedin-planner`, `linkedin-analytics`.
Files in this package (11)
  • SKILL.md 5 KB
  • references/01-access-and-auth.md 10 KB
  • references/02-api-mechanics.md 11 KB
  • references/03-posting-and-engagement.md 13 KB
  • references/04-analytics.md 6 KB
  • references/05-sign-in-and-share.md 4 KB
  • references/06-rules-and-policies.md 8 KB
  • references/07-other-programs.md 6 KB
  • references/08-troubleshooting.md 6 KB
  • references/09-page-index.md 76 KB
  • references/10-versions-and-changes.md 5 KB

Versions

RepositoryScoreLicence
This page · phoenixDatasolutions/Linkedin-Automation90MIT
ericrisco/rsc-harness100MIT

Database snapshot: 13.11.2026 · package version a6dcf4829fb6 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100linkedin-api-setup
    Guided, step-by-step setup to connect Claude to LinkedIn's official API - create a LinkedIn Page and developer app, add the right products, get the client ID and secret (the "API key"), sign in with OAuth, and make a first safe test post. Use when someone says "set up LinkedIn…
  • 100linkedin-webhooks
    Receive and verify LinkedIn webhooks. Use when setting up LinkedIn webhook handlers, completing the challengeCode endpoint validation, debugging X-LI-Signature verification, or handling LEAD_ACTION (Lead Sync) and ORGANIZATION_SOCIAL_ACTION_NOTIFICATIONS (Community Management) events.
  • 100linkedin-analytics
    Read and interpret LinkedIn post numbers (views, reactions, comments, reposts, followers) through the official analytics API while staying inside the daily call limit, and turn them into decisions. Use for "how did my LinkedIn post do", "LinkedIn analytics", "which posts…
  • 100x-api
    X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.
  • 100int-linkedin
    Query LinkedIn API — profile info, posts (when approved), org stats. Supports multi-account via OAuth. Use when user asks about LinkedIn metrics, LinkedIn profile, LinkedIn posts, or any reference to LinkedIn analytics.
  • 100linkedin-marketing
    Create, optimize, and automate LinkedIn content for personal branding, lead generation, and B2B marketing. Use when someone asks to "write a LinkedIn post", "grow on LinkedIn", "LinkedIn content strategy", "LinkedIn API integration", "automate LinkedIn posting", "LinkedIn…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.