LinkedIn Post Reactions Scraper — No Login, No Cookies, Pay Per Result

Extract every public reactor on any LinkedIn post — names, profile URLs, headlines, profile pictures, and the exact reaction type (Like, Celebrate, Love, Support, Insightful, Funny, Curious). Clean structured JSON. No LinkedIn login required. No cookies. No browser session. No account ban risk.

The fastest, cheapest, safest way to scrape LinkedIn post reactions at scale.

---

Why this is the best LinkedIn Reactions Scraper on Apify

Most LinkedIn reaction scrapers on the market fail on at least one of these. This one nails every column.

LinkedIntel vs cookie-based scrapers:

• ✅ No LinkedIn login required — others make you paste your li_at cookie
• ✅ Zero account ban risk — others put your account at stake on every run
• ✅ Set once, runs forever — others break every 2-4 weeks when cookies expire
• ✅ Safe to use at work — others tie scraping back to your LinkedIn identity
• ✅ Cheapest pricing — $1 per 1,000 reactions, pay only for results

What you get — every reactor, every detail

For every public reaction on any LinkedIn post, this actor returns:

• Reactor identity — full name, public profile URL, member URN, current headline, profile picture URL
• Reaction type — exact LinkedIn reaction enum: LIKE, PRAISE (Celebrate), APPRECIATION (Support), EMPATHY (Love), INTEREST (Curious), ENTERTAINMENT (Funny), MAYBE (Insightful)
• Joinable IDs — activityUrn for the post and reactorMemberId for the person, both joinable across other LinkedIntel scrapers

One record per reaction. Flat JSON. Ready to drop into Airtable, Google Sheets, HubSpot, Salesforce, Pipedrive, Zapier, Make, n8n, or any webhook.

Top use cases

1. High-intent B2B lead harvesting

Reactors are higher-intent than passive viewers — they took action on a post in your problem space. Pull the thread, dedupe by company, push profile URLs into your CRM. Reaction-warmed cold outreach beats raw lists 2-4x on reply rates.

2. Buying-committee detection

When a target prospect's coworker reacts to your post, that's a signal worth Slack-pinging your AE. Set up a recurring run on a target prospect's recent posts and you've got real-time engagement intel.

3. Influencer & creator audit

Before paying a creator for a sponsored post, check who's actually reacting to their content. Real audience or paid engagement pods? Look at reactor headlines, employers, and account quality.

4. Voice-of-customer signal

Sort reactors by reactionType to surface people who tagged a post Insightful or Empathy — the strongest "this resonated" signal LinkedIn provides. That's your roadmap audience.

5. Competitive launch radar

When a competitor announces a launch, the reactor list is a free real-time focus group. Who's loyal? Who's a switcher? Who tagged a colleague (active buying committee)?

6. Conference & community ABM

Reactor threads on big industry posts are de-facto attendee lists for the conversation. Dedupe by company → ABM target list pre-warmed by topic interest.

Quick start (3 steps, 30 seconds)

Step 1 — Get the post URL

Open the post in your browser, click the timestamp under the author's name, copy the URL. Both formats work:

• https://www.linkedin.com/posts/<slug>-activity-7427761938388123648-AbCd
• https://www.linkedin.com/feed/update/urn:li:activity:7427761938388123648/

Step 2 — Run the actor

1. Click the green Start button
2. Paste one or more URLs into Post URLs (one per line)
3. Set Max Reactions Per Post to control your budget per post (default 500)
4. Click Start

Step 3 — Get your data

Results stream into the Dataset tab as the run progresses. Click Export for JSON, CSV, or Excel — or push directly to Zapier, Make, Google Sheets, Airtable, HubSpot, Salesforce, or any webhook via Apify's native integrations.

Input

Field	Type	Default	Description
postUrls	array of strings	[]	LinkedIn post URLs. Accepts feed URLs and shareable post URLs. Multiple URLs in one run are processed sequentially.
activityUrns	array of strings	[]	Numeric activity URNs (e.g. "7427761938388123648"). Use this when you already have IDs and want to skip URL parsing.
maxReactionsPerPost	integer	500	Hard cap on reactions returned per post. Lower values run faster and cost less.
proxyConfiguration	object	Apify residential	Proxy settings (defaults are correct for most users).

At least one of postUrls or activityUrns is required.

Example input

{
  "postUrls": [
    "https://www.linkedin.com/posts/example-author_topic-keyword-activity-7400000000000000000-XyZw"
  ],
  "maxReactionsPerPost": 500
}

Output

Each reaction is a single dataset record:

{
  "type": "reaction",
  "reactionType": "PRAISE",
  "reactorMemberId": "urn:li:member:123456789",
  "reactorDashUrn": "ACoAAA...",
  "fullName": "Jane Doe",
  "headline": "VP of Marketing at Example Corp",
  "profileUrl": "https://www.linkedin.com/in/ACoAAA...",
  "profilePictureUrl": "https://media.licdn.com/dms/image/...",
  "activityUrn": "urn:li:activity:7400000000000000000",
  "postUrl": "https://www.linkedin.com/posts/example-author_topic-keyword-activity-7400000000000000000-XyZw",
  "scrapedAt": "2026-05-10T16:00:00.000000+00:00"
}

Full field reference

Field	Type	Description
reactionType	string	LinkedIn reaction enum: LIKE, PRAISE (Celebrate), APPRECIATION (Support), EMPATHY (Love), INTEREST (Curious), ENTERTAINMENT (Funny), MAYBE (Insightful)
reactorMemberId	string	LinkedIn member URN (urn:li:member:NNN) — joinable across LinkedIntel actors
reactorDashUrn	string	LinkedIn dash URN (the ACoAA... hashed format) — usable in advanced LinkedIn API calls
fullName	string	Display name
headline	string	Public LinkedIn headline at time of scrape
profileUrl	string	Public profile URL — pipe into LinkedIn Profile Scraper for enrichment
profilePictureUrl	string	Profile photo CDN URL
activityUrn	string	Parent post URN — joinable with comments and post-info datasets
postUrl	string	The input URL you provided
scrapedAt	string (ISO 8601)	When the record was collected

A final summary record is also pushed at the end of every run with totalReactions, postsSuccessful, postsFailed, postsTotal.

Pricing — pay only for results

$1.00 per 1,000 reactions. Pay-per-result.

• ✅ No subscription
• ✅ No base fee
• ✅ No charge for failed runs
• ✅ No charge for empty / private / deleted posts (you get a clean diagnostic record)
• ✅ Apify's free tier ($5/month platform credit) gets you ~5,000 free reactions to start

The cheapest LinkedIn reactions scraper on Apify Store, period. Most competitors charge $5-15 per 1,000 results, often with a base fee on top.

Combine with other LinkedIn actors

Build a complete LinkedIn intelligence pipeline by chaining this with sibling scrapers:

• Pipe profileUrl into the LinkedIn Profile Scraper to enrich every reactor with full firmographic data
• Pipe activityUrn into the LinkedIn Post Comments Scraper to combine reactions and comments for the same post
• Pipe reactorMemberId into the LinkedIn Profile Reactions Scraper to see what else those reactors react to across LinkedIn

FAQ

Do I need a LinkedIn account?

No. This is the killer feature. The actor does not log in to LinkedIn, does not use your session, does not touch your account. It reads the public reactor list that anyone can view without signing in.

Will my LinkedIn account get banned?

No — because we never use it. Cookie-based scrapers risk your account every run. This actor doesn't.

How fast is it?

1-10 seconds per post depending on reaction volume. Posts with thousands of reactions paginate automatically. You can queue 50+ posts in one run.

What if the post is private, deleted, or members-only?

The actor returns a clean diagnostic record for that URL and continues with the next post — it never crashes mid-batch.

Why is profileUrl an obfuscated /in/ACoAA… URL instead of the vanity username?

Public LinkedIn reactor data only exposes the dash-URN format of profile URLs. The link works (clicking it opens the right profile), but if you need the vanity slug (/in/janedoe), pipe profileUrl into the LinkedIn Profile Scraper which returns the canonical URL.

Can I filter by reaction type at scrape time?

Not in v1.0 — every reaction is returned. Filter post-scrape by the reactionType field in your destination (Google Sheets formula, Airtable filter, SQL WHERE). Server-side filtering is on the roadmap for v1.1.

Can I scrape Pulse articles?

Not yet. LinkedIn Pulse articles use a different content type. The actor returns a clear "not supported" diagnostic if you pass a Pulse URL — no charge incurred. Pass a regular feed post URL instead.

Can I integrate with Zapier / Make / n8n / HubSpot?

Yes — Apify integrates natively with all of them, plus Salesforce, Airtable, Google Sheets, and any webhook-compatible tool.

Does this work in countries outside the US / EU?

Yes. The actor uses Apify's residential proxy network and works with public LinkedIn posts from anywhere LinkedIn is accessible.

Can AI agents pay for and run this actor?

Yes — Agent Payments (x402 / USDC) are enabled. AI agents can pay per run in stablecoin without a human in the loop.

Legal & compliance

• Extracts publicly available data only — no logins, no access-control bypass, no private content
• You are responsible for complying with LinkedIn's Terms of Service, GDPR (EU), CCPA (California), and other applicable laws
• The output may include names, public profile URLs, and public headlines. Under GDPR, a lawful basis (legitimate interest, consent) may be required before outbound use
• This actor is not affiliated with, endorsed by, or sponsored by LinkedIn Corporation or Microsoft Corporation. "LinkedIn" is a registered trademark of LinkedIn Corporation

Changelog

v1.0.0 — 2026-05-10

• Initial release
• Cookieless architecture — zero account-ban risk
• Returns 7 distinct reaction types per record
• Supports linkedin.com/feed/update/... and linkedin.com/posts/... URL formats
• Clean diagnostic records for empty posts, Pulse articles, and unsupported URL formats
• Native Apify integrations + Agent Payments (x402 / USDC)

Support

Questions, feature requests, or bug reports? Open an issue on the actor's Issues tab. We respond within 24 hours.

Like this actor? Leave a review on the Apify Store — it helps other LinkedIn data teams find it.