Social Fetch
Get API key
LinkedIn hub

LinkedIn Post API

Pass a public LinkedIn post or article permalink and get structured JSON — body text, author, reactions, comments — without scraping the feed yourself.

GET /v1/linkedin/posts

1 credit per successful request.

Try in playgroundFull API docs

About this endpoint

Brand monitoring and content pipelines often start from a single LinkedIn permalink someone pasted into Slack or a CRM, not a search query. You need the public body, who wrote it, reaction and comment counts, and maybe a few top-level comments. Rolling your own fetch means fighting login walls and markup that LinkedIn reshuffles without notice.

`GET /v1/linkedin/posts` takes one `url` query param: a public post or article permalink. Branch on `data.lookupStatus` before you write — `found` vs `not_found`. When found, `data.post` carries `contentType` (`post` or `article`), the resolved `url`, plus title, headline, description, and `publishedAt` when LinkedIn exposes them. `data.author` has name, profile URL, avatar, and followers when public. `data.metrics` covers reactions and comments. The payload can also include top-level `comments` and `relatedArticles` from the same author when those blocks are available.

This route is a single-item lookup by permalink. Keyword discovery uses `GET /v1/linkedin/posts/search`. Spoken audio from a post uses `GET /v1/linkedin/posts/transcript`. Company feed pagination uses `GET /v1/linkedin/companies/posts`. Pricing is 1 credit per successful request; trust `meta.creditsCharged` on the response.

LinkedIn Post API FAQ

How do I fetch a LinkedIn post or article via API?

Call `GET /v1/linkedin/posts` with your Social Fetch API key (`x-api-key`) and a public post or article `url` query param. Read `data.lookupStatus` and `data.post` in the JSON response. Full parameters are in the API docs.

How much does the LinkedIn Post API cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged — that field is the billing source of truth.

What URL format does the LinkedIn post endpoint accept?

Pass a public LinkedIn post or article permalink (the share URL you open in a browser). Person `/in/…` pages belong on `GET /v1/linkedin/profiles`. Company pages belong on `GET /v1/linkedin/companies`.

What fields does the LinkedIn post response include?

When `lookupStatus` is `found`, you get `post` (contentType, url, title, headline, description, publishedAt), `author` (name, profileUrl, avatarUrl, followers), `metrics` (reactions, comments), plus optional top-level `comments` and `relatedArticles` when LinkedIn shows them publicly.

LinkedIn post lookup vs search vs transcript?

Use `GET /v1/linkedin/posts` when you already have a permalink. Use `GET /v1/linkedin/posts/search` to find posts by keyword with cursor pagination. Use `GET /v1/linkedin/posts/transcript` when you need spoken text from the post media.

Does this endpoint return posts and long-form articles?

Yes. `data.post.contentType` is `post` or `article` so you can branch on feed-style updates vs long-form LinkedIn articles in the same response shape.

What happens when a LinkedIn post URL is not found?

The call returns a typed `lookupStatus` of `not_found` with no post card to upsert. Keep `meta.requestId` if you need to retry or escalate that row.

Other LinkedIn endpoints