LinkedIn All-in-One Scraper

Search LinkedIn posts by keyword, scrape posts from profiles, companies and groups, pull the people who reacted or commented, and fetch profile details — all in a single actor.

Features

• Post Search — Search any LinkedIn post by keywords, with filters by company, author, date range and content type
• Profile Posts — Extract posts from one or more LinkedIn profiles
• Company Posts — Extract posts from one or more LinkedIn company pages
• Group Posts — Extract posts from LinkedIn groups
• Post Detail — Get full details for specific posts by URL
• Post Reactions — Who reacted to a post, with name, position and profile URL
• Profile Reactions — What a person reacted to, even when they never post themselves
• Profile Comments — Where a person comments, and what they said
• Profile Details — Identity, headline, current position and follower counts, optionally with full experience, education and skills
• No cookies or LinkedIn account required
• Real-time data
• Automatic pagination

Input

Field	Type	Description
mode	string	post-search, profile-posts, company-posts, group-posts, post-detail, post-reactions, profile-reactions, profile-comments or profile-detail
search	string	Keywords (post-search only)
profileUrls	array	LinkedIn profile URLs
companyUrls	array	LinkedIn company page URLs
groupUrls	array	LinkedIn group URLs or numeric IDs (group-posts only)
postUrls	array	LinkedIn post URLs (post-detail and post-reactions)
profileDepth	string	basic or full (profile-detail only)
postedLimit	string	Filter by recency: 24h, week, month (post-search only)
sortBy	string	relevance or date (post-search only)
contentType	string	videos, images, documents, etc. (post-search only)
maxPosts	integer	Max results to extract (0 = unlimited, default: 100)

Output

Every mode writes to the same dataset, and the source field says which mode produced each row. The dataset has a table view per result type: Posts, Reactions, Comments and Profiles.

A post

{
  "postId": "urn:li:activity:1234567890",
  "url": "https://www.linkedin.com/posts/...",
  "content": "Post text content...",
  "postedAt": "2026-01-15T10:00:00.000Z",
  "postedTimestamp": 1768471200000,
  "author": { "id": "...", "name": "John Doe", "url": "https://www.linkedin.com/in/johndoe/", "avatar": "https://..." },
  "engagement": { "likes": 142, "comments": 23, "shares": 8, "reactions": 156 },
  "media": { "images": ["https://..."], "video": null },
  "article": null,
  "isRepost": false,
  "repostedBy": null,
  "source": "post-search"
}

A reaction on a post — who reacted

{
  "reactionId": "urn:li:fsd_reaction:(...)",
  "reactionType": "LIKE",
  "postId": "urn:li:ugcPost:1234567890",
  "author": {
    "id": "...",
    "name": "Jane Roe",
    "url": "https://www.linkedin.com/in/janeroe",
    "position": "Head of Data",
    "avatar": "https://..."
  },
  "source": "post-reactions"
}

A reaction by a person — what they reacted to

This mode answers a different question, so it returns different fields: the reaction type is spelled out in action, and the post that was reacted to comes attached.

{
  "reactionId": "7489674966439845888",
  "action": "Jane Roe likes this",
  "url": "https://www.linkedin.com/feed/update/urn:li:activity:7489674966439845888",
  "postedAt": "2026-08-02T13:34:23.431Z",
  "postedTimestamp": 1785677663431,
  "postId": "7489674966439845888",
  "author": { "id": "...", "name": null, "url": "https://www.linkedin.com/in/janeroe", "position": null, "avatar": "https://..." },
  "post": { "postId": "...", "content": "...", "author": { "name": "Example Corp" }, "engagement": { "likes": 186 } },
  "source": "profile-reactions"
}

A comment

{
  "commentId": "7487260948903288832",
  "url": "https://www.linkedin.com/feed/update/...",
  "content": "Great point about...",
  "postedAt": "2026-01-16T09:12:00.000Z",
  "postedTimestamp": 1768554720000,
  "postId": "urn:li:ugcPost:1234567890",
  "author": { "id": "...", "name": "Jane Roe", "url": "https://...", "position": "CTO", "avatar": "https://..." },
  "engagement": { "likes": 4, "comments": 1, "shares": 0, "reactions": 10 },
  "contributed": false,
  "edited": false,
  "post": { "postId": "...", "content": "...", "author": { "name": "Example Corp" } },
  "source": "profile-comments"
}

A profile

{
  "profileId": "ACoAAA...",
  "publicIdentifier": "johndoe",
  "url": "https://www.linkedin.com/in/johndoe",
  "name": "John Doe",
  "headline": "VP of Engineering",
  "about": "...",
  "location": { "linkedinText": "Santiago, Chile" },
  "currentPosition": [{ "companyName": "Example Corp" }],
  "followerCount": 12345,
  "connectionsCount": 500,
  "verified": true,
  "source": "profile-detail"
}

With profileDepth: "full" the profile also carries experience, education, skills, certifications and languages.

Example Inputs

Search posts by keyword

{
  "mode": "post-search",
  "search": "artificial intelligence startup",
  "postedLimit": "week",
  "sortBy": "date",
  "maxPosts": 50
}

Posts from a profile

{
  "mode": "profile-posts",
  "profileUrls": ["https://www.linkedin.com/in/satyanadella/"],
  "maxPosts": 50
}

Who reacted to a post

{
  "mode": "post-reactions",
  "postUrls": ["https://www.linkedin.com/posts/username_activity-1234567890-abcd"],
  "maxPosts": 200
}

What a person reacted to

{
  "mode": "profile-reactions",
  "profileUrls": ["https://www.linkedin.com/in/satyanadella/"],
  "maxPosts": 100
}

Profile details, full

{
  "mode": "profile-detail",
  "profileUrls": ["https://www.linkedin.com/in/satyanadella/"],
  "profileDepth": "full"
}

Pricing

Results are priced by what they cost to collect, so a list of posts is far cheaper per row than a full profile. Posts, reactions and comments bill one post, reaction or comment event each; profiles bill profile-basic or profile-full depending on the depth you choose. Set Max total charge on the run to cap what a single run can spend — the actor stops when it reaches that limit.