KonbiniAPI

The LinkedIn API for products and pipelines.

Retrieve supported public LinkedIn data — member and company profiles, posts, articles, and video transcripts — through REST endpoints that return one consistent response model.

Get free API keyView the docs
  • 7 supported endpoints
  • Public data only
  • Fetched at request time
GET/v1/linkedin/posts/{postId}200OK
{
  "type": "Note",
  "entityId": "7491228345121157120",
  "content": "It's a great time to tune in and stream space…",
  "published": "2026-08-06T20:26:57.743Z",
  "likeCount": 87,
  "replyCount": 3,
  "attributedTo": {
    "type": "Organization",
    "preferredUsername": "nasa",
    "followerCount": 7067788
  }
}

What you can pull from LinkedIn.

LinkedIn is the one where the useful reads are about companies and people rather than about a feed. A company page returns its description, location, employee count, and logo — the fields a CRM record needs, from a pasted URL. A member profile returns the headline, location, and a plain list of job titles and school or employer names.

Posts are covered for both members and companies, and a single post returns author, engagement counts, and its first few inline comments. Video posts carry captions when the author uploaded them, available as a separate transcript call.

Every response uses the same ActivityStreams 2.0-based model as the other supported platforms, so a LinkedIn integration reuses the parsing you already wrote. Fields specific to LinkedIn stay as documented first-class fields rather than being flattened away.

LinkedIn data
  • Public member profiles
  • Company pages with employee counts
  • Member posts and published articles
  • Company post feeds
  • Single posts with engagement counts
  • Video captions as transcripts

All 7 LinkedIn endpoints.

Grouped by what they return. Every one has its parameter contract, a request you can copy, and an example response.

Profiles

2

Member and company records — the two entry points everything else here is reached from.

Get user profileReturns profile information for a public LinkedIn member: headline, location, and a simple list of job titles and school/employer names. Fields the member…GET /v1/linkedin/users/{username}Get company pageReturns public information for a LinkedIn company page including description, location, employee count, and logo.GET /v1/linkedin/companies/{company}

Feeds

3

What a member or a company page has published: posts, and long-form articles as their own read.

Get user articlesReturns a public LinkedIn member's published articles. This endpoint is not paginated — everything available is returned in a single response.GET /v1/linkedin/users/{username}/articlesGet user postsReturns a public LinkedIn member's recent posts and shares. This endpoint is not paginated — everything available is returned in a single response.GET /v1/linkedin/users/{username}/postsGet company postsReturns recent posts from a LinkedIn company page, newest first. Use `cursor` to page through further results.GET /v1/linkedin/companies/{company}/posts

Posts

2

One post by activity id, and the WebVTT transcript when that post carries a captioned video.

Get postReturns a public LinkedIn post including author, engagement counts, and up to ~5 inline comments.GET /v1/linkedin/posts/{postId}Get post video transcriptLinkedIn API: Returns the caption/transcript for a video post, when the post carries captions. Returns 404 if the post has no video or no captions.GET /v1/linkedin/posts/{postId}/transcript

How the calls fit together.

Few LinkedIn jobs are a single request. Most are two or three chained, each call keyed by an id the one before it returned.

Enrich a company record

Resolve the company page from its URL slug, then read its recent posts for current activity.

  1. 1Get company page/v1/linkedin/companies/{company}
  2. 2Get company posts/v1/linkedin/companies/{company}/posts

Read a member’s output

Take the profile, then their posts and long-form articles as two separate reads.

  1. 1Get user profile/v1/linkedin/users/{username}
  2. 2Get user posts/v1/linkedin/users/{username}/posts
  3. 3Get user articles/v1/linkedin/users/{username}/articles

Get the text of a video post

Fetch the post for its author and counts, then its transcript when the video carries captions.

  1. 1Get post/v1/linkedin/posts/{postId}
  2. 2Get post video transcript/v1/linkedin/posts/{postId}/transcript

What shapes your LinkedIn integration.

Page sizes, ordering, and what the platform itself withholds — the details that decide how you build, settled before you write a line of code.

01Member-restricted fields are omitted
A member can restrict parts of their profile. Those fields are absent from the response rather than empty, so read defensively and do not treat a missing field as a zero.
02Member posts and articles are not paginated
Both endpoints return everything available in one response. There is no cursor, and no way to ask for more than the platform exposes.
03Transcripts need a video with captions
The transcript endpoint returns the caption track of a video post. It returns 404 when the post has no video, or has video with no captions.
04A post carries only its first comments
A single post includes up to roughly five inline comments. There is no separate endpoint that pages the rest of a thread.
Read the LinkedIn referenceMake your first request

Other platforms

Build on LinkedIn data.

Get a free API key and call any of these endpoints in minutes. No credit card required.

Get free API keyLinkedIn reference