LinkedIn Post Reactions Scraper

Extract public reaction and engagement metrics from known LinkedIn post URLs without asking users for LinkedIn cookies.

This Actor is designed for lead research, campaign monitoring, creator analytics, and AI-agent workflows that need clean JSON from public LinkedIn posts. It uses owner-managed public-data providers, tries ScrapeCreators first by default, and falls back to SociaVault when configured.

What You Get

• One reaction summary row per LinkedIn post
• Like and total reaction counts when exposed
• Comment, share, and engagement totals
• Reaction breakdowns by type when exposed by the provider
• Post author, author URL, follower count, title, text, and publish date when available
• Optional visible reactor profile rows if a provider payload includes reactor identities
• OUTPUT and RUN_SUMMARY records for automation, monitoring, and AI agents

Important Data Boundary

Public LinkedIn provider endpoints currently expose post-level reaction counts more reliably than the full list of people who reacted. The default summaries mode saves reaction metrics for each post. The reactors and both modes normalize visible reactor profile objects only when the upstream provider includes them in the public post payload.

The Actor does not use LinkedIn login cookies, does not access private posts, and does not promise private member data, emails, connections, or a complete LinkedIn-native reactions graph.

Input

Provide LinkedIn post URLs through startUrls or postUrls. Numeric activity IDs and urn:li:activity values are also accepted.

{
  "postUrls": [
    "https://www.linkedin.com/feed/update/urn:li:activity:7312345678901234567/"
  ],
  "outputMode": "summaries",
  "maxPosts": 100,
  "maxReactors": 5000
}

Output Example

{
  "recordType": "post",
  "postUrl": "https://www.linkedin.com/pulse/being-father-has-made-me-better-leader-vice-versa-austen-allred/",
  "postTitle": "Being a Father Has Made me a Better Leader, and Vice Versa",
  "postAuthorName": "Austen Allred",
  "postAuthorUrl": "https://www.linkedin.com/in/austenallred",
  "postPublishedAt": "2020-06-21T14:35:59.000+00:00",
  "likeCount": 215,
  "reactionCount": 215,
  "commentCount": 17,
  "engagementCount": 232,
  "reactorProfilesFound": 0,
  "reactorProfilesSaved": 0,
  "source": "sociavault",
  "scrapedAt": "2026-06-10T00:00:00.000Z"
}

Output Modes

• summaries: saves post-level reaction and engagement metrics. Recommended.
• reactors: saves visible reactor profile rows only when the provider exposes identities.
• both: saves both summary rows and visible reactor rows.

Provider Setup

Set at least one owner secret in Apify Console:

apify secrets add SCRAPECREATORS_API_KEY "your-key"
apify secrets add SOCIAVAULT_API_KEY "your-key"

SOCIALVAULT_API_KEY is also read for compatibility with older actors, but SOCIAVAULT_API_KEY is preferred.

Pricing

This Actor uses pay-per-event pricing:

• Actor start: $0.00005
• Post reaction summary row: $0.008
• Visible reactor profile row: $0.012

Platform usage is paid by the user. You can cap run spend with Apify's max charge settings.

Use Cases

• Measure reaction volume on LinkedIn launch posts
• Monitor thought-leader or competitor post engagement
• Enrich CRM workflows with public post engagement signals
• Track campaign performance across known LinkedIn posts
• Feed AI agents structured engagement metrics from public post URLs

Limitations

• Results depend on public/provider-visible LinkedIn data.
• Public post endpoints may return aggregate reaction counts without reactor identities.
• LinkedIn can change public page structure and provider response fields.
• Private, deleted, restricted, or login-only posts may return no data.

Support

If a public post URL returns no results, include the run ID, the input URL, selected provider order, and the RUN_SUMMARY record when reporting the issue.