> **For coding agents and LLMs:** This is one page from the Social Fetch docs (markdown export). For curated orientation and workflow guidance, start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for agent onboarding and crawl rules, use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for the full endpoint list with links to pages like this one, use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt); for one platform's parameters and curls, use [`/llms-{platform}.txt`](https://www.socialfetch.dev/llms-tiktok.txt); use [`/llms.json`](https://www.socialfetch.dev/llms.json) when you need structured JSON for tool registration.

## This page

- **On-site (HTML):** [https://www.socialfetch.dev/docs/api/v2/linkedin](https://www.socialfetch.dev/docs/api/v2/linkedin)
- **Markdown (.mdx) URL:** [https://www.socialfetch.dev/docs/api/v2/linkedin.mdx](https://www.socialfetch.dev/docs/api/v2/linkedin.mdx)

## API base URL and authentication

- **API origin (from OpenAPI `servers`):** `https://api.socialfetch.dev`
- **Authentication:** send `x-api-key: sfk_...` on `/v1/**` and `/v2/**` routes unless the operation is explicitly anonymous (check OpenAPI `security`, the [API reference hub](https://www.socialfetch.dev/docs/api.mdx), [`/llms.txt`](https://www.socialfetch.dev/llms.txt), or [`/llms.json`](https://www.socialfetch.dev/llms.json) for each route).
- **OpenAPI JSON:** [https://www.socialfetch.dev/openapi.json](https://www.socialfetch.dev/openapi.json)

## Recommended docs entrypoints (this site)

- [Documentation overview](https://www.socialfetch.dev/docs.mdx) — top-level orientation (markdown).
- [Quickstart](https://www.socialfetch.dev/docs/quickstart.mdx) — authenticate with `x-api-key`, validate auth with `whoami`, and understand the JSON envelope.
- [SDK](https://www.socialfetch.dev/docs/sdk.mdx) — official TypeScript SDK guide, including `SocialFetchClient`, `Result`, and `unwrap()`.
- [Capability matrix](https://www.socialfetch.dev/docs/capability-matrix.mdx) — every operation with identifiers, pagination, outcomes, media download, credits, and its SDK method. Generated from OpenAPI, so use it for route selection instead of scanning individual pages.
- [Recipes](https://www.socialfetch.dev/docs/recipes.mdx) — copyable workflows (brand monitoring, transcripts, Ad Library, creator scoring, Reddit research) with credit callouts and SDK examples.
- [Integrations](https://www.socialfetch.dev/docs/integrations.mdx) — MCP for AI clients, n8n verified node, Apify Store Actors, Make custom app, SDK, and REST API connection paths.
- [MCP product page](https://www.socialfetch.dev/mcp) — hosted MCP overview, OAuth, Skills install.
- [MCP integration](https://www.socialfetch.dev/docs/integrations/mcp.mdx) — hosted `/mcp` server, OAuth, Cursor/VS Code/Claude install snippets, 232 endpoint tools, plus docs_search/docs_read for implementation help.
- [n8n integration](https://www.socialfetch.dev/docs/integrations/n8n.mdx) — install `n8n-nodes-socialfetch`, credentials, and workflow examples.
- [Apify integration](https://www.socialfetch.dev/docs/integrations/apify.mdx) — Store Actors under @social-fetch, PPE billing, dataset export, and quick start.
- [Make integration](https://www.socialfetch.dev/docs/integrations/make.mdx) — custom app modules for Make scenarios, API key credentials, and module catalog.
- [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt) — every documented operation with a direct link to that route's agent-readable markdown page (prefer this over parsing OpenAPI).
- [`/llms-{platform}.txt`](https://www.socialfetch.dev/llms-tiktok.txt) — per-platform endpoint files generated from OpenAPI (parameters, credits, curls).
- [`/agents.txt`](https://www.socialfetch.dev/agents.txt) — agent crawl/onboarding file with capabilities, auth rules, and allowlist.
- [`/llms.json`](https://www.socialfetch.dev/llms.json) — structured machine-readable operation inventory with parameter names, pagination, outcomes, credits, and SDK mapping.
- [API reference hub](https://www.socialfetch.dev/docs/api.mdx) — human-friendly index of operations with links into generated pages.
- [Errors](https://www.socialfetch.dev/docs/errors.mdx) — shared error envelope and HTTP status guidance.
- [Credits](https://www.socialfetch.dev/docs/credits.mdx) — metering, `402`, and planning batch jobs.
- Outcome semantics such as `found`, `not_found`, and `private` are documented in [Errors](https://www.socialfetch.dev/docs/errors.mdx) and on operation pages when present in the OpenAPI contract.

## Markdown docs convention

- Every docs page has a markdown twin: append **`.mdx`** to the docs pathname (for example `/docs/quickstart` → `/docs/quickstart.mdx`).
- Agents that send `Accept: text/markdown` on `/docs/**` HTML URLs may receive markdown directly (same URL, `Vary: Accept`).
- Published blog posts use the same convention: `/blog/{slug}` → `/blog/{slug}.mdx`, or `Accept: text/markdown` on the HTML URL (`Vary: Accept`).

---
# LinkedIn API reference (https://www.socialfetch.dev/docs/api/v2/linkedin)

Social Fetch's LinkedIn tag is a set of `GET /v2/linkedin/...` routes. Pass a handle, entity ID, organization ID, job ID, URL, or search query and get `{ data, meta }` with `meta.requestId` and `meta.creditsCharged`. Authenticate with `x-api-key` only — no LinkedIn partner app or member login.

These pages are generated from the public OpenAPI spec. Product overview, examples, and FAQs live on the [LinkedIn scraper API hub](/platforms/linkedin). Older `/v1/linkedin` integrations: [v1 to v2 migration](/docs/api/v1/linkedin/migration).

  Most LinkedIn v2 routes are **3 credits** per completed lookup, and paginated calls bill **each page**. Exceptions: a single organization by numeric ID is **6**, organization resolve is **3** (including a verified miss), organization URL batches are **up to 9 per completed URL**, and job search is **6** per page. Person and job URL batches are **3 per completed URL**. Trust `meta.creditsCharged`.

## Identifiers

These IDs are not interchangeable. Treat every ID as a **string**.

| You have                            | Use this field                  | Shape                                   |
| ----------------------------------- | ------------------------------- | --------------------------------------- |
| `linkedin.com/in/jane-doe`          | `handle` = `jane-doe`           | Public slug                             |
| A prior person lookup               | `entityId`                      | Opaque, often `ACo…`                    |
| `linkedin.com/company/stripe`       | `slug` = `stripe`, then resolve | Public slug                             |
| Company or school page ID           | `id` or `organizationId`        | Digits, as a string                     |
| `linkedin.com/jobs/view/4468687278` | `jobId`                         | Digits, as a string                     |
| A post from a feed                  | `activityId`                    | Digits; `urn:li:activity:…` is stripped |

`entityId` is the stable person token — not the vanity handle, and not an organization or job ID. Read it from [`GET /v2/linkedin/profiles`](/docs/api/v2/linkedin/profiles/get) (`data.profile.entityId`) or [`GET /v2/linkedin/people/resolve`](/docs/api/v2/linkedin/people/resolve/get) (`data.identity.entityId`). People-section routes require it in the path. On the profile route, send `handle` or `entityId`, not both.

Resolve a company slug with [`GET /v2/linkedin/organizations/resolve`](/docs/api/v2/linkedin/organizations/resolve/get) before organization section routes.

## Profiles and people

- [LinkedIn profile](/docs/api/v2/linkedin/profiles/get) — `GET /v2/linkedin/profiles` — one person by handle or entity ID.

- [Profile batch](/docs/api/v2/linkedin/profiles/batch/get) — `GET /v2/linkedin/profiles/batch` — up to 50 profile URLs.

- [Resolve person](/docs/api/v2/linkedin/people/resolve/get) — `GET /v2/linkedin/people/resolve` — handle to entity ID.

- [Profile posts](/docs/api/v2/linkedin/people/entityId/posts/get) — `GET /v2/linkedin/people/{entityId}/posts` — that person's feed.

- [Profile comments](/docs/api/v2/linkedin/people/entityId/comments/get) — `GET /v2/linkedin/people/{entityId}/comments` — comments they wrote.

- [Employment history](/docs/api/v2/linkedin/people/entityId/employment-history/get) — `GET /v2/linkedin/people/{entityId}/employment-history` — roles grouped by organization.

- [Recommendations](/docs/api/v2/linkedin/people/entityId/recommendations/get) — `GET /v2/linkedin/people/{entityId}/recommendations` — recommendations written for them.

- [Interests](/docs/api/v2/linkedin/people/entityId/interests/get) — `GET /v2/linkedin/people/{entityId}/interests` — followed companies, newsletters, and people.

- [Similar people](/docs/api/v2/linkedin/people/entityId/similar/get) — `GET /v2/linkedin/people/{entityId}/similar` — similar public profiles.

## Organizations

- [Organization](/docs/api/v2/linkedin/organizations/get) — `GET /v2/linkedin/organizations` — one page by numeric ID.

- [Organization batch](/docs/api/v2/linkedin/organizations/batch/get) — `GET /v2/linkedin/organizations/batch` — up to 50 organization URLs.

- [Resolve organization](/docs/api/v2/linkedin/organizations/resolve/get) — `GET /v2/linkedin/organizations/resolve` — slug to numeric ID.

- [Organization posts](/docs/api/v2/linkedin/organizations/organizationId/posts/get) — `GET /v2/linkedin/organizations/{organizationId}/posts` — company or school feed.

- [Organization jobs](/docs/api/v2/linkedin/organizations/jobs/get) — `GET /v2/linkedin/organizations/jobs` — open jobs for one or more org IDs.

- [Headcount](/docs/api/v2/linkedin/organizations/organizationId/headcount/get) — `GET /v2/linkedin/organizations/{organizationId}/headcount` — employee-count signal.

- [Affiliated organizations](/docs/api/v2/linkedin/organizations/organizationId/affiliated/get) — `GET /v2/linkedin/organizations/{organizationId}/affiliated` — related pages.

- [Similar organizations](/docs/api/v2/linkedin/organizations/organizationId/similar/get) — `GET /v2/linkedin/organizations/{organizationId}/similar` — similar pages.

## Jobs

- [Job](/docs/api/v2/linkedin/jobs/jobId/get) — `GET /v2/linkedin/jobs/{jobId}` — one posting by numeric ID.

- [Job batch](/docs/api/v2/linkedin/jobs/batch/get) — `GET /v2/linkedin/jobs/batch` — up to 50 job URLs.

- [Hiring team](/docs/api/v2/linkedin/jobs/jobId/hiring-team/get) — `GET /v2/linkedin/jobs/{jobId}/hiring-team` — listed recruiters and hiring managers.

- [Related jobs](/docs/api/v2/linkedin/jobs/jobId/related-views/get) — `GET /v2/linkedin/jobs/{jobId}/related-views` — jobs people also view.

- [Similar jobs](/docs/api/v2/linkedin/jobs/jobId/similar/get) — `GET /v2/linkedin/jobs/{jobId}/similar` — similar postings.

## Activities

- [Activity](/docs/api/v2/linkedin/activities/activityId/get) — `GET /v2/linkedin/activities/{activityId}` — one post or share.

- [Activity comments](/docs/api/v2/linkedin/activities/activityId/comments/get) — `GET /v2/linkedin/activities/{activityId}/comments` — replies on that post.

- [Activity reactions](/docs/api/v2/linkedin/activities/activityId/reactions/get) — `GET /v2/linkedin/activities/{activityId}/reactions` — who reacted.

## Search

- [Search people](/docs/api/v2/linkedin/people/search/get) — `GET /v2/linkedin/people/search` — people by keyword.

- [Search organizations](/docs/api/v2/linkedin/organizations/search/get) — `GET /v2/linkedin/organizations/search` — companies and schools by keyword.

- [Search jobs](/docs/api/v2/linkedin/jobs/search/get) — `GET /v2/linkedin/jobs/search` — jobs by keyword.

## Related

* [LinkedIn scraper API hub](/platforms/linkedin) — coverage, FAQs, and credit notes
* [How to scrape LinkedIn data](/guides/how-to-scrape-linkedin-data)
* [LinkedIn v1 to v2 migration](/docs/api/v1/linkedin/migration)
* [Best LinkedIn data APIs](/blog/best-linkedin-data-apis-2026)
* [Free LinkedIn profile viewer](/tools/linkedin-profile-viewer)
* [API reference](/docs/api) — all platforms