LinkedIn Post Details Scraper

Get full public details for a LinkedIn post URL — text, author, media, reaction and comment counts, optional video transcript, and a comments preview. Paste one post URL (or a short list) and get one clean dataset row per post. No LinkedIn login. No cookies.

Built for AI agents and content pipelines: a known URL in, structured JSON out, predictable $0.008 per saved post.

Honest reaction contract: public no-login data exposes aggregate reaction counts (reactionCount / likeCount), not who reacted and not a LIKE vs CELEBRATE vs INSIGHTFUL split. Reactor identities stay behind LinkedIn login. For commenter identities use LinkedIn Post Engagers Scraper.

What you get

Field	What it answers
text, title, headline	What was posted (full body; article title when it is a Pulse post)
authorName, authorUrl, authorFollowers	Who posted it
reactionCount, likeCount, commentCount, shareCount	How the post is performing publicly
mediaUrl, mediaUrls, thumbnailUrl, transcript	Media — video/image URLs plus transcript when LinkedIn exposes one
commentsPreview[]	Top visible comments attached to the same row (not a full thread export)
postUrl, postId, postKind, publishedAt, provider, scrapedAt	Provenance — which post, when, from which provider

Who it is for (and why it matters)

• Content and social teams — archive a specific LinkedIn post with engagement counts instead of screenshots.
• Competitive intelligence — capture a rival's announcement post, reactions, and visible comments in one record.
• Researchers and journalists — pull a citable public post body, timestamp, and author without a LinkedIn account.
• AI agents — resolve a LinkedIn URL the user pasted into a tool call into structured JSON (apify--linkedin-post-details-scraper).

When to use this Actor

• You already have a LinkedIn post, feed-update, or Pulse article URL and need the full public record.
• You need reaction counts plus post text in the same row.
• You want a cookieless, MCP-ready get-post tool rather than a search or feed crawler.

Best fit & sibling routing

• Keyword / company-feed discovery → LinkedIn Posts Scraper
• A person's recent posts by profile URL → LinkedIn Profile Posts Scraper
• People who commented (leads) → LinkedIn Post Engagers Scraper
• Reaction count summaries only → LinkedIn Post Reactions Scraper
• Full comment threads as the primary entity → LinkedIn Post Comments & Engagements Scraper

This Actor is the get-by-URL sibling: one post in, one detail row out.

Input

Field	Type	Default	Description
postUrls	array (required)	1 example URL	LinkedIn post / activity / pulse URLs, or a bare activity ID
maxPosts	integer	100	Budget cap on unique URLs processed
includeCommentsPreview	boolean	true	Attach visible comments on the post row
maxCommentsPreview	integer	10	Cap comments attached per row (0–50)
outputMode	enum	full	full or compact (shorter agent records)
providerOrder	enum	scrapecreators-first	Managed provider priority

Example input — single post URL

{
    "postUrls": [
        "https://www.linkedin.com/feed/update/urn:li:activity:7468770468041502720/"
    ]
}

Output (one row, abbreviated from a live provider payload)

{
    "postUrl": "https://www.linkedin.com/posts/microsoft_activity-7468770468041502720-mGV1",
    "postId": "7468770468041502720",
    "postKind": "video",
    "text": "Our newest AI Diffusion Report is out...",
    "publishedAt": "2026-06-05T21:07:22.617Z",
    "authorName": "Microsoft",
    "authorUrl": "https://www.linkedin.com/company/microsoft",
    "authorFollowers": 28914925,
    "reactionCount": 379,
    "likeCount": 379,
    "commentCount": 25,
    "provider": "scrapecreators",
    "scrapedAt": "2026-08-21T00:00:00.000Z"
}

You can download the dataset as JSON, CSV, Excel, or HTML. Every terminal run also writes OUTPUT and RUN_SUMMARY with outcome (COMPLETE / PARTIAL / VALID_EMPTY / INVALID_INPUT / UPSTREAM_FAILED / CONFIG_ERROR).

Workflow story: from a pasted post URL to an archive row

A competitive-intel analyst drops a rival's launch post URL into this Actor. The run starts, the managed provider chain fetches the public post, and one row lands with the full text, author, reactionCount 379, commentCount 25, video URL, and transcript. She exports JSON to her briefing doc, then (optionally) sends the same URL to LinkedIn Post Engagers Scraper when she needs the people who commented. Elapsed time is typically under 15 seconds; event cost is $0.008 plus the tiny start event and platform usage.

Why AI agents and MCP clients choose this Actor

• One required input. postUrls is the only required field.
• Predictable cost. Only saved posts are billed at $0.008.
• Structured output. Stable keys plus a published dataset schema.
• Honest outcomes. Invalid URLs → INVALID_INPUT. Deleted posts → VALID_EMPTY. Provider outage with zero rows → UPSTREAM_FAILED.

"Get the full public details and reaction counts for this LinkedIn post URL."

MCP tool name: apify--linkedin-post-details-scraper.

Pricing — Pay per event + platform usage

Event	Price	Charged when
Actor start	$0.00005	Once per run
post-scraped	$0.008	One post row saved to the dataset

A one-post run costs about $0.008 in events. Not-found posts are not billed. Platform usage is additional — see the live Pricing tab.

API example

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

Integrations and chaining

• Archive then leads: this Actor → LinkedIn Post Engagers Scraper
• Discover then details: LinkedIn Posts Scraper → feed URLs here

Best results guidance

• Use a public post URL you can open while logged out.
• Prefer one URL for agent calls; batch up to 100 for archive jobs.
• Deleted or non-post URLs are reported per-URL instead of faking a row.

Scope, data boundary & recovery

• Public, incognito-visible posts only.
• Reactions are counts, not reactor identities.
• Dual-provider fallback: ScrapeCreators /v1/linkedin/post then SociaVault /v1/scrape/linkedin/post. Owner secrets, never user API keys.

Evidence & freshness

Field shape is verified against live ScrapeCreators and SociaVault payloads for public activity and Pulse URLs: aggregate likeCount/reactionCount, commentCount, author, media, optional transcript, and visible comments. Every row carries provider and scrapedAt (ISO 8601).

Builder's note

I built this after probing both providers on a real activity URL and a Pulse article. Both return the same public post object — full text, author, media, likeCount as the reaction total, comments, and sometimes a transcript — and neither exposes who clicked Like or Celebrate. That is why this Actor is a get-post-details tool with honest reaction counts.

FAQ

Does this return who reacted? No. Public providers return reaction counts.

Is LinkedIn login required? No.

What if the post is deleted? VALID_EMPTY with zero charges when every URL is missing.

Legal

This Actor retrieves publicly available data. You are responsible for complying with LinkedIn's Terms of Service, applicable data-protection laws (GDPR/CCPA), and Apify's Exclusion Policy when using the results.