LinkedIn Post Reactions Scraper

Pricing

Rating

Developer

Actor stats

Categories

Share

Scrape the complete list of people who reacted to any LinkedIn post. For each reactor you get their name, headline, profile URL, and the reaction type (like, celebrate, love, support, insightful, funny, curious).

What you get

For every person who reacted to a post:

Input

Accepted post URL formats

• https://www.linkedin.com/feed/update/urn:li:activity:7234567890123456789/
• https://www.linkedin.com/posts/username_slug-7234567890123456789-xxxx/
• urn:li:activity:7234567890123456789
• 7234567890123456789 (bare activity ID)

Getting your LinkedIn cookie

1. Log in to LinkedIn in your browser
2. Open DevTools → Application → Cookies → www.linkedin.com
3. Copy the value of li_at

For best results, export all cookies as a JSON array using a browser extension like EditThisCookie or Cookie-Editor.

Output example

{
"reactorName":"Jane Doe",
"reactorProfileUrl":"https://www.linkedin.com/in/janedoe",
"reactorHeadline":"Senior Engineer at Acme Corp",
"reactionType":"like",
"postUrl":"https://www.linkedin.com/feed/update/urn:li:activity:7234567890123456789/",
"postId":"7234567890123456789",
"inputPostUrl":"https://www.linkedin.com/feed/update/urn:li:activity:7234567890123456789/",
"scrapedAt":"2025-01-15T10:30:00+00:00"
}

Reaction types

Use cases

• Lead generation — Find everyone who engaged with a competitor's or thought leader's post
• Community analysis — Understand who your post resonates with
• Recruiting — Identify professionals who reacted to industry content
• Market research — Discover interested buyers for specific topics
• Influencer outreach — Build contact lists of engaged LinkedIn users

Notes

• LinkedIn limits visible reactors to approximately 1,000 per post (regardless of total shown)
• A valid LinkedIn session cookie (li_at) is required — the scraper cannot work without authentication
• Residential proxy is recommended but not required for small runs
• Rate limiting is handled automatically with exponential backoff

FAQ

How many reactors can I scrape per post? LinkedIn's API exposes up to approximately 1,000 reactors. The actor stops when it reaches the LinkedIn-reported total or your configured maxReactorsPerPost limit.

Do I need a LinkedIn Premium account? No. A standard LinkedIn account with a valid session cookie is sufficient.

Will LinkedIn detect this scraper? The actor uses LinkedIn's own internal Voyager API, the same API that powers the LinkedIn web app. However, excessive scraping or very high rate requests may trigger rate limiting. The actor automatically backs off when rate limited.

Can I filter by reaction type? Yes. Use the reactionTypeFilter input to include only specific reaction types (e.g., only like and insightful). Leave it empty to get all reaction types.

How fresh is the data? Data is fetched live from LinkedIn at run time, so it reflects the current state of reactions on the post.

Explore the rest of the LinkedIn suite

Need a different LinkedIn surface? Pair this actor with any of the others in the LinkedIn Suite — all published under the same publisher and built to share the same cookie format and output conventions.

All actors share the same cookie input format (plain li_at OR full cookies JSON array) and the same omit-empty output convention.