LinkedIn Post Reactions
Pricing
from $1.50 / 1,000 post reaction results
LinkedIn Post Reactions
Extract people and entities that reacted to public LinkedIn posts. Get reaction type, name, headline, LinkedIn URL, IDs, and timestamps in clean JSON or CSV—no cookies or LinkedIn login required.
Pricing
from $1.50 / 1,000 post reaction results
Rating
0.0
(0)
Developer
Data Slayer
Maintained by CommunityActor stats
0
Bookmarked
10
Total users
4
Monthly active users
6 days ago
Last modified
Categories
Share
Paste one or many public LinkedIn post URLs and get one structured row per reaction — reaction type, reactor name, headline, LinkedIn URL, and ID. No cookies, no login, no LinkedIn account risk.
Cookieless · Fresh data · No LinkedIn login or account risk.
Watch the demo
Video tutorial coming soon.
What you get
Every reaction row uses the same flat schema:
| Field | Type | Description |
|---|---|---|
post_url | string | Normalized LinkedIn post URL requested in the input. |
post_id | string | Numeric LinkedIn post ID stored as a string to prevent precision loss. |
reaction_urn | string or null | Derived LinkedIn reaction URN when the required identifiers are available. |
reaction_type | string | LIKE, PRAISE, EMPATHY, APPRECIATION, INTEREST, or ENTERTAINMENT. |
reactor_entity_type | string | person, company, or unknown. |
reactor_name | string or null | Display name returned for the reactor. |
reactor_headline | string or null | LinkedIn headline or position when available. |
reactor_linkedin_url | string or null | LinkedIn URL returned for the person or company. |
reactor_id | string or null | Encoded LinkedIn profile or company identifier. |
reactor_image_url | string or null | Valid media image URL when available. |
input_index | integer | Zero-based position of the post URL in the normalized input. |
reaction_index | integer | Zero-based reaction order for that post after filtering and deduplication. |
fetched_at | string | UTC retrieval timestamp in ISO 8601 format. |
All fields are always present. Unavailable optional values are null in JSON and empty cells in CSV.
Reaction types
The output uses LinkedIn's stable reaction categories:
| Output value | LinkedIn label |
|---|---|
LIKE | Like |
PRAISE | Celebrate |
EMPATHY | Support |
APPRECIATION | Love |
INTEREST | Insightful |
ENTERTAINMENT | Funny |
Output example
{"post_url": "https://www.linkedin.com/feed/update/urn:li:activity:7408723748973056001","post_id": "7408723748973056001","reaction_urn": "urn:li:fsd_reaction:(urn:li:fsd_profile:ACoAAExampleProfileId,urn:li:activity:7408723748973056001,0)","reaction_type": "LIKE","reactor_entity_type": "person","reactor_name": "Example Person","reactor_headline": "Growth Marketing Lead","reactor_linkedin_url": "https://www.linkedin.com/in/ACoAAExampleProfileId","reactor_id": "ACoAAExampleProfileId","reactor_image_url": null,"input_index": 0,"reaction_index": 0,"fetched_at": "2026-07-25T10:00:00Z"}
Download results as JSON, JSONL, CSV, Excel, XML, or HTML table data from the Apify dataset.
Input
| Field | Required | Default | Description |
|---|---|---|---|
post_urls | Yes | — | Add 1–1,000 LinkedIn post URLs. Supported formats include /posts/...-activity-..., /posts/...-ugcPost-..., and /feed/update/urn:li:activity:.... Comment URLs are not supported. |
max_reactions_per_post | No | 100 | Maximum matching reactions saved per post. Use 0 to request all available reactions, with a 100-page safety cap. |
reaction_types | No | ["ALL"] | Keep every supported reaction type or select one or more specific types. |
Filters are applied before max_reactions_per_post, so the maximum counts matching saved reactions rather than discarded reaction types.
How to use it
- Add one or more public LinkedIn post URLs under LinkedIn Post URLs.
- Keep the default maximum of 100 reactions per post or choose another limit.
- Keep All reaction types or select the reactions you need.
- Click Start and open the Dataset tab when the run finishes.
The maximum is an upper bound, not a guaranteed result count. The actor stops when it reaches your limit or when the available source reactions are exhausted.
Use cases
- Build a list of people who engaged with a campaign, announcement, or thought-leadership post
- Compare reaction types across posts for audience and content analysis
- Research public engagement on industry, company, or competitor posts
- Export reactor data to spreadsheets, CRM workflows, dashboards, or enrichment pipelines
- Monitor selected posts on a schedule and compare reaction datasets over time
- Feed structured LinkedIn reaction data into internal tools, AI agents, or analytics systems
Pricing
This actor charges per reaction result saved (pay-per-event). The current price per result is shown on the actor's Pricing tab — there is no subscription and no minimum. Use max_reactions_per_post to cap exactly how many reactions a run can request per post.
Integrations
- API — trigger runs and fetch results programmatically
- Scheduling — monitor posts on a recurring basis
- Webhooks — get notified when a run completes
- Make and Zapier — connect to 1,000+ apps without code
- Google Sheets — pipe results directly into a spreadsheet
- MCP — use this actor as a tool inside Claude, Cursor, or any MCP-compatible AI agent
JavaScript example:
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: process.env.APIFY_TOKEN });const run = await client.actor('data-slayer/linkedin-post-reactions').call({post_urls: ['https://www.linkedin.com/feed/update/urn:li:activity:7408723748973056001',],max_reactions_per_post: 100,reaction_types: ['ALL'],});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(items);
Other LinkedIn Actors by data-slayer
| Actor | What it does |
|---|---|
| LinkedIn Post Performance Scraper | Likes, comments, shares and reaction breakdown for any post |
| LinkedIn Post Engagers Scraper | Everyone who engaged with a post — commenters, reactors, reposters |
| LinkedIn Post Comments Scraper | Every comment on a post, with commenter profiles |
| LinkedIn Post Reposts Scraper | Everyone who reposted or shared a post |
| LinkedIn Profile Posts Scraper | Recent posts from a profile, with engagement metrics |
| LinkedIn Profile Scraper | Full profile data from any LinkedIn profile URL |
| LinkedIn Profile Engagers Scraper | Everyone who engaged across a profile's recent posts, ranked by engagement |
| LinkedIn Profile Reactions Scraper | Reactions a profile left on other people's posts |
| LinkedIn Profile Comments Scraper | Comments a profile left on other people's posts |
| LinkedIn Company Scraper | Full company profile data |
| LinkedIn Company Posts Scraper | Recent posts from any company page |
| LinkedIn People Search (ICP) | Find people by title, seniority, function, company, location |
| LinkedIn Company Search (ICP) | Find companies by industry, size, location and tech stack |
| LinkedIn Company Employees | Employees at a company, filtered by title, seniority and function |
| LinkedIn Job Scraper | Full details for LinkedIn job postings |
| LinkedIn Job Change Tracker | People who recently changed jobs |
Which LinkedIn actor should I use?
| I have… | And I want… | Use |
|---|---|---|
| A post URL | Everyone who reacted | LinkedIn Post Reactions Scraper |
| A post URL | Everyone who engaged (commenters + reactors + reposters) | LinkedIn Post Engagers Scraper |
| A post URL | Likes, comments, shares & reaction breakdown | LinkedIn Post Performance Scraper |
| A post URL | Everyone who commented | LinkedIn Post Comments Scraper |
| A post URL | Everyone who reposted | LinkedIn Post Reposts Scraper |
| Profile URL(s) | Their recent posts & engagement | LinkedIn Profile Posts Scraper |
| A profile URL | Reactions they left on others' posts | LinkedIn Profile Reactions Scraper |
Example tasks
Ready-made configurations you can run as-is, each with its own guide:
- Get everyone who reacted to a post
- Capture reactions on multiple posts at once
- Find 'interest' reactors on a thought-leadership post
FAQ
Do I need a LinkedIn account, cookie, or login?
No. The input contains only post URLs and optional result controls. The actor does not ask for LinkedIn credentials or session cookies.
Can I process multiple LinkedIn posts in one run?
Yes. Add up to 1,000 supported post URLs to post_urls. Duplicate normalized URLs are removed before processing.
Can I filter by reaction type?
Yes. Choose Like, Celebrate, Support, Love, Insightful, Funny, or all supported reaction types. Multiple specific types can be selected.
Does the actor return every reaction on a post?
Not necessarily. It returns the reactions exposed by the source until the selected maximum or source exhaustion is reached. The maximum is not a completeness guarantee.
Why is reactor_image_url sometimes null?
The field is kept only when the source returns a valid media image URL. A LinkedIn profile page is not an image, so it is intentionally converted to null rather than mislabeled.
Can I export reactions to CSV or Excel?
Yes. Open the run's Dataset tab and choose CSV, Excel, JSON, or another Apify-supported export format.
What happens if one URL fails in a batch?
The actor continues with the remaining URLs. Check the RUN_SUMMARY in the key-value store for the status, counts, and safe error details for every input URL.
Does it scrape reactions on LinkedIn comments?
No. This actor accepts supported LinkedIn post URLs only; comment URLs are rejected.
Limits and data notes
- The actor extracts reactions available through its public-data source. It cannot guarantee every reaction visible on LinkedIn.
max_reactions_per_postis an upper bound. A post may return fewer reactions when the source is exhausted or exposes fewer records.- Public, deleted, restricted, private, or region-limited posts can return no results or an error.
- Encoded LinkedIn profile URLs may be returned instead of vanity profile URLs.
- This actor does not open or enrich individual LinkedIn profiles — it returns reaction-level data only.
- Reactions are deduplicated by post ID and reactor ID and emitted in normalized input order, then source order.
- A value of
0formax_reactions_per_postrequests all available pages with a 100-page safety cap per post. - This independent actor is not affiliated with or endorsed by LinkedIn Corporation.
Feedback and support
Use the actor's Issues tab for bug reports, questions, or feature requests. Include the run ID, a non-sensitive example input, the expected result, and what happened.
Related actors
More from the same portfolio. Apify only auto-recommends actors in the same category, so here are the rest of ours: