# LinkedIn Company Posts Scraper (no login) (`santiagomv/linkedin-company-posts`) Actor

Scrape the recent public posts of LinkedIn company pages: text, date, likes, comments, reposts, images and links. Up to about 70 recent feed entries per company, reposts flagged. Paste URLs or slugs. No account or cookies needed.

- **URL**: https://apify.com/santiagomv/linkedin-company-posts.md
- **Developed by:** [Santiago Marcos](https://apify.com/santiagomv) (community)
- **Categories:** Social media, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.00 / 1,000 posts

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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 (no login)

Scrape the **recent public posts of LinkedIn company pages** into clean JSON: post text, date, likes, comments, reposts, images, links, and whether the entry is a repost of someone else's post.

Paste company URLs (any `linkedin.com/company/...` link) or just slugs like `stripe`. No LinkedIn account, cookies or browser needed. It saves one row per post.

> ⚠️ **Read before use.** This actor reads LinkedIn's public, logged-out company pages. LinkedIn's User Agreement restricts automated access, so using this actor **may break LinkedIn's terms**, and LinkedIn may block or restrict IPs or accounts linked to that use. **You are responsible for how you use this actor and the data it returns**, including complying with LinkedIn's terms and with data-protection laws (e.g. GDPR) in your jurisdiction. This actor is not affiliated with, endorsed by, or sponsored by LinkedIn.

### What you can use it for

- **Competitor monitoring**: schedule it daily or weekly with **Only new posts** on and get just what competitors published since the last run.
- **Content research**: see which topics and formats get the most likes and comments for companies in your space.
- **Sales signals**: spot launches, hiring pushes, funding news and events from target accounts.
- **Archiving**: keep your own copy of a company's recent public posts.

### How much it can fetch

LinkedIn's public company page shows a **recent feed of about 70 entries** (newest first) to logged-out visitors. This actor reads that feed and stops there. It does **not** fetch a company's full post history, and the exact number available varies by company and over time. If a company has posted less, you get less.

### Input

- **Companies**: one URL or slug per line. Duplicates are removed.
- **Max posts per company** (default 30, up to 70): how many of the newest feed entries to inspect per company. Reposts count toward the limit. With **Only new posts** on, entries already saved by earlier runs still count, so this is a recent-feed window, not a guaranteed number of saved rows.
- **Only new posts** (off by default) and **State store name**: turn on to skip posts saved by earlier runs. The actor remembers seen posts in a named key-value store, so use the same store name on every scheduled run. Without a store name there is nothing to remember between runs, and every run saves the full recent feed.
- **Parallel companies** (default 2, up to 5): how many companies are scraped at once.
- **Proxy**: Apify Proxy is on by default and recommended.

### Output

One row per post:

```json
{
  "postId": "7518359395844513792",
  "url": "https://www.linkedin.com/feed/update/urn:li:activity:7518359395844513792/",
  "companySlug": "posthog",
  "companyUrl": "https://www.linkedin.com/company/posthog/",
  "text": "We just shipped...",
  "publishedAt": "2026-10-20T15:55:00.000Z",
  "likes": 312,
  "comments": 18,
  "reposts": 9,
  "isRepost": false,
  "author": { "name": "PostHog", "url": "https://www.linkedin.com/company/posthog" },
  "images": ["https://media.licdn.com/dms/image/..."],
  "links": ["https://posthog.com/blog/..."],
  "scrapedAt": "2026-10-21T06:00:00.000Z"
}
```

#### Reposts

When a company reshares someone else's post, the row has `isRepost: true`. `postId` and `url` identify the company's repost, and `repostedPost` holds what is available about the original (such as its ID, URL, author and text). For a plain repost with no added commentary, the row has only `postId`, `url`, the company fields and `isRepost` at the top level; the text, author, date, counts, images and links all sit under `repostedPost`, because they describe the original post, not the company's repost. Filter on `isRepost` if you only want the company's own posts.

#### Missing fields

The actor only returns what LinkedIn shows logged-out visitors. Fields LinkedIn doesn't show are left out of the row, and lists can be empty: for example `publishedAt` when no exact date is shown, counts LinkedIn hides, or details of a repost's original. `repostedPost` is only present on reposts. Videos, documents and polls are not downloaded; the post row and its text are still saved.

### Code examples

Python, Node.js, cURL and an importable n8n workflow for this actor: https://github.com/SantiagoMV42/linkedin-jobs-scraper

### Cost

You pay **$0.001 per post saved** ($1 per 1,000 posts, the `post` event). Empty or failed requests and retries add no post charge, and neither do posts skipped by **Only new posts**. If a company's feed fails partway, the posts already saved from it stay charged. Your run's maximum cost limit is always respected.

**Only new posts** state is not transactional: overlapping runs, or a run interrupted between saving posts and updating the state store, can save or charge a post twice. Don't run jobs that share the same state store at the same time.

### Errors and limitations

- LinkedIn rate-limits busy IPs and sometimes answers with errors or a sign-in wall. The actor retries those requests a few times with a new proxy session, then gives up on that company.
- A company that can't be loaded doesn't stop the run. Failed companies are listed in the `FAILURES` record of the run's key-value store. A company can also return fewer posts than requested if LinkedIn stops serving its feed partway.
- Results depend on what LinkedIn serves at run time, and LinkedIn can change its pages at any moment, so a run may return fewer posts or fewer fields than usual.
- Only public company pages. No personal profiles, no logged-in data, no private posts.

### Related actors

- [LinkedIn Company Scraper](https://apify.com/santiagomv/linkedin-company): company details such as size, industry, HQ and followers.
- [LinkedIn Jobs Scraper](https://apify.com/santiagomv/linkedin-jobs).

### Support

Found a bug or need a field? Open an issue on the actor's Issues tab and we'll reply.

# Actor input Schema

## `companies` (type: `array`):

LinkedIn company page URLs (linkedin.com/company/...) or just the slug, e.g. 'stripe'. One per line. Duplicates are removed.

## `maxPostsPerCompany` (type: `integer`):

How many of the newest feed entries to inspect per company. Reposts count toward this limit. With 'Only new posts' on, entries saved by earlier runs still count, so fewer rows may be saved. LinkedIn's public page only shows about 70 recent entries, so 70 is the maximum.

## `onlyNewPosts` (type: `boolean`):

Skip posts already saved by earlier runs. Needs a state store name below so the actor can remember what it has seen between runs.

## `stateStoreName` (type: `string`):

Name of a key-value store that remembers which posts were already saved, e.g. 'competitor-posts'. Use the same name on every scheduled run. Only used when 'Only new posts' is on.

## `maxConcurrency` (type: `integer`):

How many companies are scraped at once. Lower values are gentler on LinkedIn and less likely to be rate-limited.

## `proxyConfiguration` (type: `object`):

Apify Proxy is recommended; LinkedIn rate-limits busy IPs.

## Actor input object example

```json
{
  "companies": [
    "stripe",
    "posthog"
  ],
  "maxPostsPerCompany": 30,
  "onlyNewPosts": false,
  "maxConcurrency": 2,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `posts` (type: `string`):

All posts saved in this run, as a table.

# 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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "companies": [
        "stripe",
        "posthog"
    ],
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("santiagomv/linkedin-company-posts").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 '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "companies": [
        "stripe",
        "posthog",
    ],
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("santiagomv/linkedin-company-posts").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": [
    "stripe",
    "posthog"
  ],
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call santiagomv/linkedin-company-posts --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,santiagomv/linkedin-company-posts"
        }
    }
}
```

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 <APIFY_API_TOKEN>` 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/yqI5yTCj2kQeH3HBL/builds/n3KELgYuF6bbFYzbJ/openapi.json