LinkedIn Company Posts Scraper: Text, Reactions & Media avatar

LinkedIn Company Posts Scraper: Text, Reactions & Media

Pricing

from $3.00 / 1,000 posts

Go to Apify Store
LinkedIn Company Posts Scraper: Text, Reactions & Media

LinkedIn Company Posts Scraper: Text, Reactions & Media

Export posts from any LinkedIn company page with no login or cookies: text, exact date, reactions, comments, images, videos, documents and links. Track competitors, brands and prospects.

Pricing

from $3.00 / 1,000 posts

Rating

0.0

(0)

Developer

Philip Kirkbride

Philip Kirkbride

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

16 hours ago

Last modified

Features

Limited permissionsMulti-tenantServer interface

Share

LinkedIn Company Posts Scraper

Turn any LinkedIn company page into a clean, exportable post feed, with no LinkedIn account or cookies needed. Get every post's text, exact publish time, reactions, comments, images, videos, documents and links, one row per post.

  • Sales and lead-generation teams: see what target accounts announce and launch.
  • Competitor and market analysts: compare posting frequency, topics and engagement across companies.
  • Social-listening and content teams: benchmark your brand's posts against peers and export them for reports.
  • Monitoring: run on a schedule with Posted after (for example 7 days) to get only new posts each time.
  • Months of posts, not just the latest few: up to 66 posts per company in one run, newest first.

Also available

The social media suite: pick the job.

ActorUse when
LinkedIn Company Posts (this Actor)What every company posts, with engagement
LinkedIn Company PagesCompany size, industry and followers
LinkedIn JobsJob posts with full descriptions
Facebook Page PostsRecent posts and reactions from any Page
Instagram PostsFull post history with captions and engagement
X (Twitter)Profiles and latest posts with views

What it returns

One row per post: stable post ID and link, company name, ID and page, post text, exact publish time (UTC, to the millisecond), reaction and comment counts, image and video links, document (PDF/carousel) links, and the external links mentioned in the post. Missing public values are null, never invented zeros. Links come without LinkedIn tracking parameters.

Input

{
"companies": [
"apify"
],
"maxPostsPerCompany": 3,
"maxItems": 3
}
FieldWhat it controls
companiesCompany URLs or slugs, such as apify; up to 100 entries.
maxPostsPerCompanyMaximum posts per company: 1–100, default 100.
maxItemsMaximum total rows: 1–10,000, default 100.
historyDepthextended (default) also collects older public company posts, up to your limits. Choose recent for only the newest posts on the company page.
postedAfterOptional. Only posts published on or after this date: an ISO date such as 2026-10-01, or a period such as 30 days, 2 weeks or 6 months. Older posts are skipped and not charged.

Sources are collected in input order. The total row limit applies across all sources. Duplicate sources and overlapping items are collected once. Run with {} for a quick sample of up to 3 real posts; the prefilled input runs the same small example. When all sources are omitted or empty, the Actor announces its small sample and records usedExample: true in OUTPUT. Empty optional fields use their usual defaults. Invalid fields end the run green with OUTPUT.status: "no_results" and a message naming the field and the fix, before anything is fetched or charged. An entry in companies that is not a company link or name is skipped (listed in OUTPUT.skippedSearches with the reason) and the rest of the list still runs; that run ends partial (as any run with a source error) and only delivered posts are charged. When no company page could be read because the list had no usable entry, or every company page is missing, the run ends green with OUTPUT.status: "no_results" and noResultsReason; only a source refusal with nothing read fails.

For as many public posts as a company offers, use {"companies":["google"],"maxPostsPerCompany":100,"maxItems":100}. Collection keeps the newest posts first and stops at your limit or the available public history. If older history becomes unavailable, recent results are retained and OUTPUT reports the source error.

For a weekly update, use {"companies":["hubspot","salesforce"],"postedAfter":"7 days"}. Collection stops as soon as a company's feed reaches posts older than the cutoff. A run with no new posts succeeds with zero rows and reports how many older posts it skipped.

Use it as an API

Read a company's newest public LinkedIn posts with reactions and media. Get the answer in JSON from one HTTPS call. Call it from an AI agent through an HTTP-capable MCP tool, or add an HTTP request step in n8n, Make, or Zapier.

curl --get 'https://automatic--linkedin-company-posts-scraper.apify.actor/' \
--header "Authorization: Bearer $APIFY_TOKEN" \
--data-urlencode url=https://www.linkedin.com/company/apify/ \
--data-urlencode limit=10

Send the same fields as a JSON object with POST /. Results are in data. See GET /openapi.json for the request and response definitions.

Pricing

$0.003 per delivered post ($3.00 per 1,000) plus $0.005 per run start. One post is one dataset row. The start fee is charged per GB of memory, rounded up with a minimum of one; the default 512 MB run is one start event. Failed and skipped sources produce no charged rows. A result or charge limit can reduce the number of delivered rows.

Example at 512 MBRowsCost
Console prefill3$0.01
One run delivering 100 rows100$0.31
One run delivering 1,000 rows1,000$3.01

Costs include one start and are rounded to the nearest cent.

Output example

{
"id": "7527032524418531328",
"urn": "urn:li:activity:7527032524418531328",
"url": "https://www.linkedin.com/posts/apify_rising-stars-nov-vol-1-activity-7527032524418531328--FAj",
"company": "Apify",
"companyId": "10608457",
"companyUrl": "https://www.linkedin.com/company/apify/",
"text": "Half of Black Friday is prices pretending to be discounts. Three new Actors in Apify Store to tell the difference:\n\n🏷️ Idealo Price Data API by PricePirate: Track Black Friday prices across 6 European markets by EAN, name, or URL.\n\n📈 TikTok Shop Shops & Live Scraper by legrassy: See which TikTok Shop sellers and live streams drive the most sales.\n\n🛍️ Shopify Store Leads Database by Insane Developer: Build a Black Friday outreach list from 950K Shopify stores, emails included.\n\nWe highlight new standout Actors every other Friday. Build something great - it might be next. Link in comments ↓",
"postedAt": "2026-11-13T15:39:59.323Z",
"postedAtRaw": "2026-11-13T15:39:59.322Z",
"postedAtSource": "post_id",
"postedAtIsEstimated": false,
"reactions": 6,
"comments": 2,
"mediaUrls": [
"https://media.licdn.com/dms/image/v2/D4E10AQGZLtEl9qkvZA/ads-document-cover-images_480/B4EaHVkGg5IgAw-/0/1794584376542?e=2147483647&v=beta&t=SmmZMbEvdCbjsMgD2THJftauH5DIxcNWz52slWcF3jg",
"https://media.licdn.com/dms/image/v2/D4E10AQGZLtEl9qkvZA/ads-document-cover-images_480/B4EaHVkGg5IgAw-/1/1794584376542?e=2147483647&v=beta&t=ibEXN-ThGeHsOGBFP6x0VwrW7MYsferQnp9tlDUzxg8",
"https://media.licdn.com/dms/image/v2/D4E10AQGZLtEl9qkvZA/ads-document-cover-images_480/B4EaHVkGg5IgAw-/2/1794584376542?e=2147483647&v=beta&t=Duv-_RkpycjkiG-1PKG22aWI1qsNWQphRDXKD0f6-p0"
],
"documentUrls": [
"https://media.licdn.com/dms/document/pl/v2/D4E10AQGZLtEl9qkvZA/ads-document-master-manifest/B4EaHVkGg5IgBI-/0/1794584382731?e=2147483647&v=beta&t=SjNwdKUBu0L3ZMRBKK6TrBgwfYo5cPlL4H647O78UKU",
"https://www.linkedin.com/feed/update/urn:li:ugcPost:7527032523407671298"
],
"articleUrls": [],
"authorName": "Apify",
"authorUrl": "https://cz.linkedin.com/company/apify",
"scrapedAt": "2026-11-13T17:21:00Z"
}

Exports

Download the dataset as JSON, CSV or Excel. OUTPUT contains the run summary, sample indicator, source coverage and errors.

Good to know

  • Measured posts per company with the default extended depth: 40 Apify, 66 Google and 14 Microsoft. With historyDepth: "recent": 6, 10 and 4. These are observed counts, not a full-history guarantee; your post limits always apply.
  • Extended history keeps original company posts and excludes reshares, matching recent results. Available history varies by company.
  • Public data only; private, deleted and unavailable pages produce a specific source error. Other successful companies are kept.
  • Publish times are exact and marked postedAtSource: post_id; postedAtRaw keeps the date or label shown on the page. In the rare case a post has no usable ID, the time is estimated from the page label and marked postedAtSource: relative_estimate and postedAtIsEstimated: true.
  • With postedAfter, posts without a readable date are skipped. Share counts are not shown on public pages and are not included.
  • Media links can expire. Each run is independent; there is no saved state between runs.

Your feedback

Found a bug, or need a field or filter we don't have yet? Open an issue on this Actor's Issues tab. We read every issue and use them to decide what to build next.