LinkedIn Post Scraper

Collect structured details from known public LinkedIn post and article URLs in bounded batches. You can also inspect eligible posts exposed on a requested public profile, company, or topic landing page. Each run is limited to 50 public page requests; source pages are inspected once, and the Actor does not paginate or crawl post history. Results are saved as flat dataset rows for analysis, research, and content workflows.

Features

• Accepts individual post, long-form article, profile, company, and topic URLs.
• Supports bounded batches within a run-wide limit of 50 public page requests.
• Inspects one current public landing page for each profile, company, or topic source; it does not paginate or crawl post history.
• Keeps profile and company discovery tied to posts attributed to that requested source; topic pages can contain multiple authors, but every selected post must belong to the requested topic page.
• Collects visible author, text, date, engagement, image, hashtag, and comment-preview fields when present.
• Supports a per-source selection limit for profile, company, and topic pages.
• Removes duplicate URLs before collection and duplicate posts before saving.
• Saves each verified result progressively.
• Uses logged-out requests without LinkedIn account credentials, cookies, or authentication data.
• Stops the run when public access becomes restricted instead of continuing to request more pages.
• Writes a final OUTPUT summary with request, saved-post, and skipped-post counts.

Public visibility varies by page, post type, location, and time. A requested field can be null or empty when it is not present in the public page data.

Input

Field	Type	Required	Description
urls	string array	Yes	One to 50 supported public LinkedIn HTTPS URLs. The complete input must also fit the 50-request run budget described below.
limitPerSource	integer	No	Maximum eligible posts selected from one public profile, company, or topic landing page. Range: 1–25. Default: 10. This is not a promised row count and does not enable pagination. Direct post and article URLs ignore this setting.

Supported URL forms include:

• https://www.linkedin.com/posts/...-activity-...-...
• https://www.linkedin.com/feed/update/urn:li:activity:...
• https://www.linkedin.com/pulse/...
• https://www.linkedin.com/in/...
• https://www.linkedin.com/company/...
• https://www.linkedin.com/top-content/...

Run capacity and source scope

The Actor validates a conservative request estimate before collection starts:

direct post/article URLs + source URLs × (1 + limitPerSource) ≤ 50

A direct post or article URL reserves one public page request. Each profile, company, or topic URL reserves one request for its landing page plus up to limitPerSource post-page requests. Canonical duplicate inputs are counted once.

Examples:

• 50 unique direct post or article URLs fit the run limit.
• With the default limitPerSource of 10, each source reserves 11 requests. Four source-only inputs fit; five would reserve 55 and are rejected before collection.
• With limitPerSource set to 25, one source reserves 26 requests; two would reserve 52 and are rejected before collection.

These are request-budget estimates, not promised result counts. A source input inspects eligible post links exposed in one current public landing-page response only; it does not paginate or crawl that source's post history.

Example input:

{
  "urls": [
    "https://www.linkedin.com/posts/microsoft_worktrendindex-activity-7457369463198437376-3F4k"
  ],
  "limitPerSource": 10
}

The Actor validates the complete input before making a page request. Unsupported page types, non-HTTPS addresses, unknown fields, and inputs whose conservative estimate exceeds 50 public page requests are rejected without creating paid failure rows.

Output

Each dataset row represents one saved public post or article. Common fields include:

• inputUrl, postUrl, urn
• authorName, authorProfileUrl, authorType, authorFollowerCount
• postHeadline, postText, postedAt
• reactionsCount, commentsCount
• imageUrl, imageAlt
• hashtags, commentsPreview
• extractedAt, extractionWarnings

Example output row:

{
  "inputUrl": "https://www.linkedin.com/posts/example_activity-1234567890123456789-abcd",
  "postUrl": "https://www.linkedin.com/posts/example_activity-1234567890123456789-abcd",
  "urn": "urn:li:activity:1234567890123456789",
  "succeeded": true,
  "error": null,
  "extractedAt": "2026-07-12T00:00:00.000Z",
  "authorName": "Example Organization",
  "authorProfileUrl": "https://www.linkedin.com/company/example",
  "authorType": "company",
  "authorFollowerCount": null,
  "postHeadline": "Example public post",
  "postText": "Example public post text.",
  "postedAt": "2026-07-01T09:00:00.000Z",
  "reactionsCount": 42,
  "commentsCount": 3,
  "imageUrl": null,
  "imageAlt": null,
  "hashtags": [],
  "commentsPreview": []
}

The key-value store record named OUTPUT contains the run status and counts. Dataset rows are created only for posts that pass identity and output checks. Pages that cannot be used are reflected in the summary instead of being saved as paid failure rows.

How to Use

1. Add one or more supported direct post, article, profile, company, or topic URLs.
2. For source pages, keep the default per-source limit or choose a value from 1 to 25, then confirm the input fits the request-budget examples above.
3. Start the Actor.
4. Open the dataset for post rows and OUTPUT for the final run summary.

For sensitive or changing sources, begin with one known direct post URL. Large or repeated tests can increase the chance that public access becomes unavailable.

FAQ

Does this Actor use my LinkedIn account?

No. The input does not accept account credentials, cookies, or authentication tokens. The Actor only attempts supported pages in a logged-out context.

Why did I receive fewer posts than the limit?

The limit is a maximum, not a promise. A page may expose fewer eligible public posts, profile or company items not attributed to that source are excluded, duplicate posts may be removed, or collection may stop early when public access changes. Profile results with valid dates are selected newest first; company and topic results retain the structured order exposed by their public page.

Why are some fields empty?

Only fields present in the supported public page data are saved. Counts, images, follower information, article text, and comment previews are not present on every page.

What happens if access is restricted?

The Actor stops further page requests, keeps any rows already saved, and explains the outcome in OUTPUT. A zero-result terminal stop is reported as a failed run; a run with saved rows is reported as partial.

Does commentsPreview contain every comment?

No. It contains up to ten comments visible in the supported page data. commentsCount, when present, is the count shown by that page and can differ from the preview length.

Can I use search-result or hashtag-feed URLs?

No. Search results, hashtag feeds, authenticated activity feeds, and company post-feed views are not supported inputs.

Does this Actor paginate through post history?

No. Profile, company, and topic inputs inspect eligible post links exposed on one current public landing page. For a larger collection of already-known posts or articles, provide their direct URLs in bounded runs that fit the 50-request limit.

More Actors

Explore more Futurize Rush Actors on Apify.

Disclaimer

This Actor is an independent product and is not affiliated with, endorsed by, or connected to LinkedIn. It collects data available on supported public pages at run time. Public availability and page structure can change without notice. You are responsible for using the output in accordance with LinkedIn's terms, applicable laws, privacy requirements, and the rights of content owners. Do not use the Actor to collect private, restricted, or authenticated content.

---

LinkedIn Post Scraper | public LinkedIn posts | social media research | content analysis | Apify Actor | OpenClaw | Claude Code | Gemini | Antigravity | Codex | ChatGPT