# LinkedIn Post Reports Scraper (`khadinakbar/linkedin-post-reports-scraper`) Actor

Scrape public LinkedIn post reports from post URLs: likes, comments, author, media, and engagement rate. Use for content analytics and competitor reporting. For commenter identities, continue with linkedin-post-engagers-scraper. Returns one report per post. Charged $0.008 per report.

- **URL**: https://apify.com/khadinakbar/linkedin-post-reports-scraper.md
- **Developed by:** [Khadin Akbar](https://apify.com/khadinakbar) (community)
- **Categories:** Social media, Lead generation, MCP servers
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $8.00 / 1,000 linkedin post reports

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## LinkedIn Post Reports Scraper

Turn public LinkedIn post URLs into one engagement report per post for content strategists, agencies, and research agents. Each row includes `likeCount`, `commentCount`, `engagementRatePct`, `authorName`, `authorFollowers`, `mediaType`, and optional `commentsPreview`. No LinkedIn login or cookies.

The Actor is designed as a focused standalone workflow. Paste a post URL, get a structured public report, then export JSON, CSV, or Excel from the Dataset tab.

### Best fit for this Actor

- Benchmark competitor or client posts from a known URL list.
- Schedule the same post URLs to watch public likes and comments over time.
- Feed a compact post report into a dashboard, CRM note, or MCP agent.

For commenter identities and company enrichment, continue with [LinkedIn Post Engagers Scraper](https://apify.com/khadinakbar/linkedin-post-engagers-scraper) after you have the post URL. For keyword or company-feed discovery, start with [LinkedIn Posts Scraper](https://apify.com/khadinakbar/linkedin-posts-scraper).

### Practical scenario

A content strategist pastes a Microsoft activity URL and sets `maxPosts` to 1. The run returns one row with author `Microsoft`, public like and comment counts, an engagement rate against follower count, video media URLs, and a short comments preview. She exports CSV for the weekly client report and re-runs the same URL next week to compare growth.

### Quick start input

```json
{
  "postUrls": [
    "https://www.linkedin.com/feed/update/urn:li:activity:7468770468041502720/"
  ],
  "maxPosts": 1,
  "includeCommentsPreview": true,
  "providerOrder": "scrapecreators-first"
}
```

`postUrls` accepts `/feed/update/urn:li:activity:...`, `/posts/...activity-...`, and pulse article URLs. One unique post produces one dataset row.

### Input reference

| Field | Type | What it controls |
| --- | --- | --- |
| `postUrls` | array | Required public post URLs. Example: a LinkedIn activity URL. Max 200 unique values. |
| `maxPosts` | integer | Cap on billable reports. Default 50, max 200. Prefill 1. |
| `includeCommentsPreview` | boolean | Attach visible public comments from the same payload. Default true. |
| `maxCommentsPreview` | integer | Comment preview cap. Default 5, max 20. |
| `providerOrder` | enum | `scrapecreators-first` (default) or `sociavault-first`. |
| `maxConcurrency` | integer | Parallel post fetches. Default 2, max 5. |

### What data you receive

One dataset item is one public LinkedIn post report.

```json
{
  "postUrl": "https://www.linkedin.com/feed/update/urn:li:activity:7468770468041502720/",
  "resolvedPostUrl": "https://www.linkedin.com/posts/microsoft_activity-7468770468041502720-mGV1",
  "postId": "7468770468041502720",
  "authorName": "Microsoft",
  "authorType": "company",
  "authorFollowers": 28914839,
  "likeCount": 379,
  "commentCount": 25,
  "engagementCount": 404,
  "engagementRatePct": 0.0014,
  "mediaType": "video",
  "outcome": "OK",
  "provider": "scrapecreators",
  "scrapedAt": "2026-08-21T12:00:00.000Z"
}
```

| Field | Meaning |
| --- | --- |
| `likeCount` | Public like/reaction aggregate from the post payload. |
| `engagementRatePct` | `(likes + comments + shares) / authorFollowers * 100` when followers are present. |
| `outcome` | `OK` billed report row. |

`OUTPUT` and `RUN_SUMMARY` in the default key-value store hold `outcome`, `itemsPushed`, and `chargedEventCounts`.

Public creator impression and reach analytics stay in LinkedIn's native analytics tools. This Actor reports public engagement counts that anyone can see on the post.

### Use through the API

```bash
curl -X POST "https://api.apify.com/v2/acts/khadinakbar~linkedin-post-reports-scraper/runs" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"postUrls":["https://www.linkedin.com/feed/update/urn:li:activity:7468770468041502720/"]}'
```

Download rows as JSON, CSV, Excel, or HTML from the Dataset tab.

### Use with AI agents through Apify MCP

> Build a LinkedIn post report for this activity URL. Return authorName, likeCount, commentCount, engagementRatePct, mediaType, outcome, and provider.

Connect via <https://mcp.apify.com>. Read `OUTPUT.outcome` and `itemsPushed` to interpret empty datasets.

### Connect the workflow

- After you have post URLs, pass them to [LinkedIn Post Engagers Scraper](https://apify.com/khadinakbar/linkedin-post-engagers-scraper) when the next step is people, not counts.
- When the starting point is a keyword or company page, start with [LinkedIn Posts Scraper](https://apify.com/khadinakbar/linkedin-posts-scraper) then feed exact URLs here.

### Pricing

Pay per event plus platform usage. Confirm current event prices on the live Pricing tab; that tab is the source of truth if this page ever lags.

- `apify-actor-start`: $0.00005 per run
- `post-report`: **$0.008** per `OK` row

A one-post report is about $0.008 in result events plus a few seconds of Apify platform usage. Missing public posts finish with `VALID_EMPTY` and no `post-report` charge. Provider credits are paid by the Actor owner.

### How it works

1. Normalize and deduplicate post URLs.
2. Fetch public post JSON from ScrapeCreators, then SociaVault.
3. Normalize likes, comments, author, media, hashtags, and engagement rate.
4. Charge `post-report` only after a usable report, then write the row.

### Best results

- Provide full post or activity URLs. Keep profile and company page URLs for the posts Actor.
- Use `maxPosts: 1` for a cheap agent check, then raise the cap for batches.
- Schedule the same URLs to compare public engagement over time.
- Pair comment previews here with the engagers Actor when you need a lead list.

### Builder's note

I found that public LinkedIn post payloads already include author followers plus like and comment counts, which is enough to build a report without cookies. Impression and reach fields stay inside LinkedIn's logged-in analytics, so my goal was a cookieless public snapshot that an agent can call with one URL. ScrapeCreators and SociaVault both return that snapshot over HTTP, which keeps this Actor fast and MCP-friendly.

### Legal and responsible use

Use this Actor on public LinkedIn data you are authorized to process, follow applicable law and LinkedIn's terms, and keep the output in your own compliance workflow. This Actor is independent of LinkedIn.

Issues and feature requests: use the Actor Issues tab on Apify.

# Actor input Schema

## `postUrls` (type: `array`):

Public LinkedIn post URLs to turn into one engagement report each. Accepts activity URLs such as https://www.linkedin.com/feed/update/urn:li:activity:7468770468041502720/, posts URLs, and pulse article URLs. Up to 200 unique URLs per run; duplicates are merged. Profile and company page URLs belong in a profile or company posts scraper.

## `maxPosts` (type: `integer`):

Hard cap on billable post-report rows for this run. Default 50 keeps agent and quality-test calls small. Prefill 1 is the cheapest one-post check. Values above 200 are clamped.

## `includeCommentsPreview` (type: `boolean`):

When enabled, each report includes up to maxCommentsPreview visible public comments from the same post payload. Default true. This uses the post detail already fetched, so it does not add a second provider call. Set false when you only need counts and author fields.

## `maxCommentsPreview` (type: `integer`):

How many public comments to attach on each report row. Default 5 matches what public post payloads typically expose. Zero stores counts only. Full commenter lead lists belong in the LinkedIn Post Engagers Scraper.

## `providerOrder` (type: `string`):

Which public-data provider to try first for each post URL. Both providers return the same report shape. The second provider runs automatically when the first misses or returns an empty payload. Keep the default unless you have a reason to prefer SociaVault.

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

How many post URLs to process in parallel. Default 2 balances speed against provider rate limits. Raise to 5 for large batches. Lower to 1 when a run log shows provider rate-limit warnings.

## Actor input object example

```json
{
  "postUrls": [
    "https://www.linkedin.com/feed/update/urn:li:activity:7468770468041502720/"
  ],
  "maxPosts": 1,
  "includeCommentsPreview": true,
  "maxCommentsPreview": 5,
  "providerOrder": "scrapecreators-first",
  "maxConcurrency": 2
}
```

# Actor output Schema

## `results` (type: `string`):

Dataset items containing post text, author, likes, comments, engagement rate, media, and provider provenance.

## `summary` (type: `string`):

Compact OUTPUT record with outcome, itemsPushed, itemsFailed, chargedEventCounts, and warnings.

## `runSummary` (type: `string`):

Detailed RUN\_SUMMARY record with per-post outcomes, provider diagnostics, and billing counters.

# 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 = {
    "postUrls": [
        "https://www.linkedin.com/feed/update/urn:li:activity:7468770468041502720/"
    ],
    "maxPosts": 1,
    "includeCommentsPreview": true,
    "maxCommentsPreview": 5,
    "maxConcurrency": 2
};

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

# Prepare the Actor input
run_input = {
    "postUrls": ["https://www.linkedin.com/feed/update/urn:li:activity:7468770468041502720/"],
    "maxPosts": 1,
    "includeCommentsPreview": True,
    "maxCommentsPreview": 5,
    "maxConcurrency": 2,
}

# Run the Actor and wait for it to finish
run = client.actor("khadinakbar/linkedin-post-reports-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 '{
  "postUrls": [
    "https://www.linkedin.com/feed/update/urn:li:activity:7468770468041502720/"
  ],
  "maxPosts": 1,
  "includeCommentsPreview": true,
  "maxCommentsPreview": 5,
  "maxConcurrency": 2
}' |
apify call khadinakbar/linkedin-post-reports-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,khadinakbar/linkedin-post-reports-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 <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/hpjvj8kM7lL15ytto/builds/9dgbfKP3Y6YHY7Akm/openapi.json