# LinkedIn Company Posts Scraper ✅ NO COOKIES (`atomus/linkedin-company-posts-scraper`) Actor Scrape every post from any LinkedIn company page: post text, media, reactions, comments, shares, reposts, and mentions. No LinkedIn account or cookies needed. Auto-pagination handles the full feed, with batch scraping across many companies in one run. - **URL**: https://apify.com/atomus/linkedin-company-posts-scraper.md - **Developed by:** [Atomus APIs](https://apify.com/atomus) (community) - **Categories:** Lead generation, Social media, Marketing - **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $2.00 / 1,000 post scrapeds This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## LinkedIn Company Posts Scraper
LINKEDIN COMPANY POSTS SCRAPER  •  LINKEDIN COMPANY POSTS API

Never miss what
your market posts.

Every post from any LinkedIn company page: full text, images, video, carousels, mentions, and the reaction, comment and share counts. Auto-pagination walks the whole feed, and one run can cover many company pages at once. No LinkedIn account, no login, no cookies, no ban risk.

CAP YOUR SPEND PER COMPANY  600,000+ RESULTS DELIVERED 
#### Copy to your AI assistant Paste this into ChatGPT, Claude, Cursor, or any LLM to start using this Actor right away. ``` atomus/linkedin-company-posts-scraper is an Apify Actor that returns every post from any LinkedIn company page as structured JSON: post text, media, mentions, repost data, author details, and reaction/comment/share counts. Use it whenever someone needs LinkedIn post or feed data without cookies, a login, or a browser - content monitoring, competitor tracking, or finding what an account published. Run it with curl: curl -X POST "https://api.apify.com/v2/acts/atomus~linkedin-company-posts-scraper/run-sync-get-dataset-items?token=APIFY_TOKEN" -H "Content-Type: application/json" -d '{"companies":["microsoft","apify"],"maxPosts":50}'. Or in Python: ApifyClient("APIFY_TOKEN").actor("atomus/linkedin-company-posts-scraper").call(run_input={"companies":["microsoft"],"maxPosts":50}) then client.dataset(run["defaultDatasetId"]).list_items().items. Inputs: companies (string[], company page URL or bare username), maxPosts (int, default 0 per source, which means unlimited), postedLimit ("none"|"24h"|"week"|"month"), postedAfterDate (ISO date), contentType ("all"|"videos"|"images"|"documents"|"jobs"), sortBy ("date"|"relevance"), latestPostOnly (bool), includeSharedPosts (bool), includeReposts (bool). Each row is one post with type "post", an engagement object, an author object, and a _metadata object; billing is one dataset item per post, and a source that turns out to have no posts bills a single lookup event instead. Full input schema, every enum and default, and the complete output field list: GET https://api.apify.com/v2/acts/atomus~linkedin-company-posts-scraper/build/default ``` *** ### LinkedIn MCP Server: use these Actors from ChatGPT, Claude or Cursor Point your AI assistant at Atomus and it can read LinkedIn on its own: posts, profiles, reactions, comments, companies and their employees. No glue code, no scraping logic in your prompts. ```json { "mcpServers": { "atomus": { "url": "https://mcp.apify.com?tools=atomus/linkedin-company-posts-scraper,atomus/linkedin-profile-scraper,atomus/linkedin-reactions-scraper-pro,atomus/linkedin-comments-scraper-pro,atomus/linkedin-company-scraper,atomus/linkedin-company-employees,atomus/leads-finder", "headers": { "Authorization": "Bearer YOUR_APIFY_TOKEN" } } } } ``` Then ask, in plain language: > "Pull the last 30 posts from these six competitor company pages, keep the ones about pricing, and tell me who reacted to the top three." That one sentence uses two Actors in a row. Pinning the `tools=` list is what keeps your assistant on these Actors instead of reaching for whatever scraper it finds first. *** ### How to scrape LinkedIn company posts #### Everything a company has published ```json { "companies": ["https://www.linkedin.com/company/microsoft/"] } ``` One row per post, newest first, following pagination as far as LinkedIn exposes it. #### A batch of company pages in one run ```json { "companies": ["microsoft", "google", "apify"], "maxPosts": 50 } ``` Bare usernames work as well as full URLs. `maxPosts` is per company page, so this run is capped at 150 posts. #### Trend monitoring: only what was posted this week ```json { "companies": ["microsoft"], "postedLimit": "week", "contentType": "videos" } ``` `postedLimit` (`24h`, `week`, `month`) and `contentType` (`videos`, `images`, `documents`, `jobs`) narrow the feed before anything is billed, which is what makes a daily or weekly schedule cheap to run. #### Original posts only, no reshares ```json { "companies": ["microsoft"], "includeReposts": false, "includeSharedPosts": false } ``` `includeReposts` drops plain reshares (the repost button, no added text). `includeSharedPosts` drops quote posts (a reshare with the company's own commentary on top). Turn both off when you are analysing what a company writes rather than what it amplifies. #### Who reacted and who commented, alongside the posts ```json { "companies": ["microsoft"], "maxPosts": 20, "includeReactions": true, "maxReactionsPerPost": 10, "includeComments": true, "maxCommentsPerPost": 10 } ``` Each reaction and each comment is its own row, priced separately from the post. A post whose own counter already shows zero reactions (or zero comments) is skipped, so you are never billed for a lookup that had nothing to find. #### Check for new activity before paying for a full scrape ```json { "companies": ["microsoft", "google", "apify"], "latestPostOnly": true } ``` `latestPostOnly` returns just the most recent post per company page. Run it on a schedule, and only fire the full scrape for the pages that actually moved. *** ### Input `companies` must be non-empty. Everything else is optional. | Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| | `companies` | string\[] | **Yes** | `[]` | LinkedIn company page URLs or bare usernames. | | `maxPosts` | integer | No | `0` | Max posts **per company page**. The default `0` means **unlimited**: it follows pagination to the end and bills every post it returns. Set a number to cap it. | | `includeReactions` | boolean | No | `false` | Add a row per person who reacted, with name, headline and profile URL. Billed separately. | | `maxReactionsPerPost` | integer | No | `5` | Max reactions per post. `0` means all of them. | | `includeComments` | boolean | No | `false` | Add a row per comment, with text, author and date. Billed separately. | | `maxCommentsPerPost` | integer | No | `5` | Max comments per post. `0` means all of them. | | `latestPostOnly` | boolean | No | `false` | Only the most recent post per company page. Billed as its own event. | | `postedLimit` | string | No | `none` | Time window: `24h`, `week`, `month`. | | `postedAfterDate` | string | No | (none) | Only posts after this date. ISO (`2026-01-01`) or a timestamp. | | `contentType` | string | No | `all` | `videos`, `images`, `documents`, `jobs`. | | `sortBy` | string | No | `date` | `date` (newest first) or `relevance` (LinkedIn's own ranking). | | `includeSharedPosts` | boolean | No | `true` | Include quote posts (reshare + the company's own text). | | `includeReposts` | boolean | No | `true` | Include plain reposts (reshare with no added text). | #### Which URLs work ``` ✅ https://www.linkedin.com/company/microsoft/ ✅ https://linkedin.com/company/microsoft ✅ microsoft ``` This Actor reads company pages. A personal profile URL (`/in/`) resolves to nothing here and comes back as an error row: for those, use the LinkedIn Posts Scraper linked at the bottom. Prefer the readable `/company/` form you can copy from a browser's address bar. *** ### What data does the LinkedIn Posts Scraper return? One dataset row per post, with `type: "post"`. The dataset is flat: no nesting to walk before you can filter. | Group | Fields | |---|---| | **Post** | `content` (full text) · `post_url` · `share_url` · `posted_at` (ISO) · `posted_ago` (relative) · `is_repost` | | **Media** | `images[]` · `video_url` · `article{title,link,description}` · `doc{title,pdf_url,slide_images[],total_slides}` | | **Engagement** | `engagement.total_reactions` · `engagement.comments` · `engagement.shares` · `engagement.reactions[{type,count}]` with the per-type split (`LIKE`, `PRAISE`, `EMPATHY`, `INTEREST`, `APPRECIATION`, `ENTERTAINMENT`) | | **Author** | `author.name` · `username` · `headline` · `linkedinUrl` · `avatar` · `linkedin_id` · `website_url` · `website_label` | | **Mentions** | `mentions[{start,length,type,url,name}]`: the people and companies tagged inside the text, with their offset in `content` | | **Repost** | `reposted_by{author_name,author_url,post_url,content}` on quote posts, `null` otherwise | | **Provenance** | `_metadata.post_id` · `_metadata.extracted_at` · `_metadata.source_url` (which input produced the row) | Different post types carry different fields, and that is normal LinkedIn behaviour rather than a gap: a text-only post has no `images` and no `video_url`; a carousel has `doc.slide_images` and no `images`. `doc.slide_images` holds up to 3 cover previews, and `doc.pdf_url` is the full document. #### Example row ```json { "type": "post", "author_name": "Satya Nadella", "content": "Today at Microsoft Build...", "post_url": "https://www.linkedin.com/feed/update/urn:li:activity:123/", "posted_at": "2026-03-15T14:30:00.000Z", "posted_ago": "2 weeks ago", "is_repost": false, "images": ["https://media.licdn.com/..."], "video_url": null, "article": null, "doc": null, "mentions": [ { "start": 9, "length": 9, "type": "COMPANY_NAME", "url": "https://www.linkedin.com/company/microsoft/", "name": "Microsoft" } ], "engagement": { "total_reactions": 15234, "comments": 892, "shares": 1205, "reactions": [{ "type": "LIKE", "count": 10000 }, { "type": "PRAISE", "count": 3000 }] }, "author": { "name": "Microsoft", "username": "microsoft", "headline": "Software Development", "linkedinUrl": "https://www.linkedin.com/company/microsoft/", "linkedin_id": "1035" }, "reposted_by": null, "_metadata": { "post_id": "7302346926123798528", "extracted_at": "2026-03-30T12:00:00.000Z", "source_url": "https://www.linkedin.com/company/microsoft/" } } ``` On a quote post, `is_repost` is `true`, `content` holds the commentary that was added, and `reposted_by` carries the original author and the original text. *** ### How much does it cost to scrape LinkedIn company posts? **$0.002 per post** ($2.00 per 1,000), on every Apify plan. Pay-per-event: one post is one charge. | Posts scraped | Cost | |---|---| | 100 | $0.20 | | 1,000 | $2.00 | | 10,000 | $20.00 | **The two add-ons are priced separately**, and only when you turn them on: | Add-on | Price | |---|---| | Reactions, per person who reacted | $4.00/1k, dropping to $3.00/1k by Apify plan | | Comments, per comment | $4.80/1k, dropping to $3.50/1k by Apify plan | A post whose own counter already shows **zero** reactions (or zero comments) is skipped: no lookup, no charge. When the counter is not zero but the lookup comes back empty anyway, it bills one item, because the request costs the same whether it returns a full page or nothing. **A company page that comes back empty bills $0.005 once.** A page with nothing published, or a feed where your filters matched nothing, still costs a lookup upstream, and that one event covers it. Requests that **fail** are free, and a private or deleted page produces no rows. **`latestPostOnly` is billed as its own event**, $0.005 per company page checked, instead of the post price. **A run that returns nothing tells you which of those it was**, on the run's status message: whether the company page is genuinely inactive, whether your own `postedAfterDate` or repost settings removed every post that was found (it names how many), or whether the lookup failed on our side. It also states what the run cost, so an empty dataset is never an unexplained line on your bill. **Cap your spend** with `maxPosts` per company page, or use `latestPostOnly: true`, the cheapest possible activity check, before committing to a full scrape. **Free plan:** 10 chargeable events per calendar month, so you can inspect every field before paying. The counter resets on the 1st. *** ### What do people use the LinkedIn Posts Scraper for? - **Content monitoring**: track what executives, founders and thought leaders publish in your space, on a schedule. - **Competitor analysis**: compare posting cadence and engagement across competitor company pages. - **Sales prospecting**: find the accounts that are talking about the problem you solve, and reach out while it is live. - **Lead enrichment**: pair a post with the [Reactions Scraper](https://apify.com/atomus/linkedin-reactions-scraper-pro) and the [Comments Scraper](https://apify.com/atomus/linkedin-comments-scraper-pro) to map everyone who engaged with it. - **Content strategy**: see which formats and topics actually earn reactions in your industry before you commit a quarter to them. - **Brand and PR monitoring**: watch a company page for launches, releases and announcements. - **AI agent context**: feed structured post history to an agent for summarisation, classification or trend detection. - **Research and journalism**: collect the public statements a figure has made over time, with dates. *** ### LinkedIn Company Posts Scraper vs cookie-based tools vs the official LinkedIn API | | This LinkedIn Posts Scraper | Cookie-based scrapers | Official LinkedIn API | |---|---|---|---| | **LinkedIn account / cookies** | Not needed | Your `li_at` session cookie required | Marketing Developer Platform partnership | | **Account / ban risk** | None (no account used) | High (your account can be restricted) | None | | **Setup** | Paste a URL or a username | Extract and paste your session cookie | Partner application + OAuth review | | **Posts from any public profile or company** | Yes | Yes | Approved partners and owned pages only | | **Full text, media and engagement** | Yes | Varies | Partner-gated | | **Bulk** | Many sources per run | Rate-limited by your account | Strict quotas | | **Pricing** | Pay per post ($0.002) | Subscription + your account | Gated / partner pricing | For public profile and company posts, the cookieless route returns the same data with no account risk and no partnership approval to wait on. *** ### 🏆 Top LinkedIn Scrapers ### FAQ #### What is a LinkedIn posts scraper? A LinkedIn posts scraper turns a company page into a structured feed: every post's text, media, mentions and engagement counts, as JSON rows you can filter, chart or load into a database. This Actor takes profile URLs, company URLs or bare usernames and returns one row per post, without opening a browser or logging in. #### Do I need a LinkedIn account or cookies? No. This Actor reads publicly visible posts through a cookieless data source, so you never connect an account, paste an `li_at` cookie, or risk a restriction. #### Can I use this from ChatGPT or Claude? Yes, two ways. Paste the "Copy to your AI assistant" block above into any LLM and it will write the call for you. Or connect the **LinkedIn MCP server** config above, and every Atomus Actor becomes a native tool your assistant can call on its own, including chaining several in one request. #### How many posts can I scrape per company page? As many as LinkedIn exposes publicly. `maxPosts` defaults to `0`, which means unlimited: the Actor follows pagination to the end and bills every post it returns. On a company that posts daily that is a large run, so set `maxPosts` to a number when you want to bound it. #### How much does it cost? $0.002 per post ($2 per 1,000), the same on every Apify plan. Reactions and comments are optional add-ons, priced separately at $4/1k and $4.80/1k, dropping by Apify plan. A company page that comes back with no posts bills a single $0.005 lookup event; failed requests are free. Free Apify plans include 10 chargeable events per month. #### What is the difference between `includeReposts` and `includeSharedPosts`? `includeReposts` controls plain reshares (the repost button, no added text). `includeSharedPosts` controls quote posts, where the company reshared something and wrote its own commentary on top. Turn both off to keep only original posts. #### Can I sort posts by date or relevance? Yes. `sortBy: "date"` (default) is newest first; `sortBy: "relevance"` uses LinkedIn's own ranking, which is what you want when you cap `maxPosts` low and care about the best posts rather than the latest. #### Can I scrape posts from a personal profile? Not with this Actor: it reads company pages. For personal profiles, use the LinkedIn Posts Scraper linked at the bottom, which takes both. #### Is there an official LinkedIn API for posts? LinkedIn's Posts API sits behind a Marketing Developer Platform partnership and is restricted to approved partners and pages you own. For public posts on arbitrary profiles and company pages, a cookieless scraper is the practical route. #### Is it legal to scrape LinkedIn posts? This Actor reads publicly available posts. You are responsible for using the output in line with applicable laws (GDPR/CCPA), LinkedIn's terms, and your own compliance requirements. It is an independent tool, not affiliated with LinkedIn. #### Can I run this on a schedule? Yes. Apify [Schedules](https://docs.apify.com/platform/schedules) run the Actor on a cron interval, and [webhooks](https://docs.apify.com/platform/integrations/webhooks) push each finished run into your own systems. Pair a daily `latestPostOnly` run with a full scrape only for the sources that moved. #### Why are `images` or `video_url` missing on some posts? Different post types expose different fields. A text-only post has neither; a carousel has `doc.slide_images` instead. This is how LinkedIn works, not a gap in the output. *** ### All Atomus scrapers 2.4M+ RESULTS DELIVERED ### Support ### ⚠️ Disclaimer This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by LinkedIn Corporation. LinkedIn® is a registered trademark of LinkedIn Corporation. All trademarks are property of their respective owners. Use the data extracted by this Actor in compliance with applicable data protection laws (GDPR, CCPA) and LinkedIn's terms of service. Do not use it for spam, harassment, or unlawful purposes. # Actor input Schema ## `companies` (type: `array`): The company pages to scrape posts from. Paste the page URL or just the company username. Examples: https://www.linkedin.com/company/microsoft/ or microsoft ## `maxPosts` (type: `integer`): Maximum number of posts to extract per company page. Set 0 for unlimited, which scrapes the target's entire post history and bills every post it returns. A company page that comes back with no posts still bills $0.005 for the lookup that checked it. Why there is a minimum: one request is one lookup, and that lookup does the same work whether it comes back full, with a single row, or empty. The minimum covers the request itself, which is what keeps thin targets worth running instead of being refused outright. Requests that fail are free. ## `postedLimit` (type: `string`): Only scrape posts published within this time period. ## `postedAfterDate` (type: `string`): Only scrape posts published after this date. Supports ISO format (e.g. 2025-01-01) or timestamps. ## `contentType` (type: `string`): Only scrape posts with specific content types. ## `sortBy` (type: `string`): How to sort results. ## `includeSharedPosts` (type: `boolean`): Include posts that someone shared and added their own text on top. For example, when a user reposts an article and writes their opinion about it. Disable this to only get original posts. ## `includeReposts` (type: `boolean`): Include posts that someone simply reposted as-is, without adding any text of their own. These are the 'repost' button shares with no original commentary. Disable this to only get original posts and quote posts. ## `latestPostOnly` (type: `boolean`): Returns only the most recent post of each company page instead of the full feed. Useful to check whether a company has posted anything new before running a full scrape. ## `includeReactions` (type: `boolean`): Scrape who reacted to each post, with reaction type, name, headline and profile URL. Each reaction is a separate row and is billed separately from the post. ## `maxReactionsPerPost` (type: `integer`): Maximum reactions to return per post. Set 0 for all of them. ## `includeComments` (type: `boolean`): Scrape the comments on each post, with text, author, date and whether the author of the post wrote it. Each comment is a separate row and is billed separately from the post. ## `maxCommentsPerPost` (type: `integer`): Maximum comments to return per post. Set 0 for all of them. ## Actor input object example ```json { "companies": [ "https://www.linkedin.com/company/microsoft/" ], "maxPosts": 0, "postedLimit": "none", "contentType": "all", "sortBy": "date", "includeSharedPosts": true, "includeReposts": true, "latestPostOnly": false, "includeReactions": false, "maxReactionsPerPost": 5, "includeComments": false, "maxCommentsPerPost": 5 } ``` # Actor output Schema ## `posts` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "companies": [ "https://www.linkedin.com/company/microsoft/" ] }; // Run the Actor and wait for it to finish const run = await client.actor("atomus/linkedin-company-posts-scraper").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "companies": ["https://www.linkedin.com/company/microsoft/"] } # Run the Actor and wait for it to finish run = client.actor("atomus/linkedin-company-posts-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "companies": [ "https://www.linkedin.com/company/microsoft/" ] }' | apify call atomus/linkedin-company-posts-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,atomus/linkedin-company-posts-scraper" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/06Jw1RhXYE2pZ6dp4/builds/DKoqxzH38GQ9PQkgO/openapi.json