LinkedIn Profile Reactions

Extract posts reacted to by public LinkedIn profiles, including action labels, post text, authors, timestamps, engagement counts, reaction breakdowns, attachments, and shared-post context. Batch up to 1,000 profiles and export JSON, CSV, or Excel—no LinkedIn cookies or login required.

Try it on Apify See example code

users, last 30 days: 1
runs, last 30 days: 29
runs, all time: 73
users, all time: 2

Live figures from Apify's public API, refreshed every hour.

LinkedIn Profile Reactions specifications

Platform	LinkedIn
Apify actor	`data-slayer/linkedin-profile-reactions`
Price	$2.00 per 1,000 results
Inputs	`profile_urlsmax_reactions_per_profileposted_within`
Output	39 documented fields per row
Export formats	JSON, CSV, Excel, XML, HTML
LinkedIn login or cookies	Not required
Integrations	Apify REST API, JavaScript and Python clients, n8n, Make, Zapier
Last updated	September 25, 2026 (version 1.0.6)

Run it from code

Replace the example input with your own. You need an Apify API token, which you can create in your Apify account settings.

POST /v2/acts/data-slayer~linkedin-profile-reactions/run-sync-get-dataset-items

request

curl -X POST "https://api.apify.com/v2/acts/data-slayer~linkedin-profile-reactions/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "profile_urls": [
      "https://www.linkedin.com/in/satyanadella"
    ],
    "max_reactions_per_profile": 100,
    "posted_within": "any"
  }'

each result row39 fields

{
  "reaction_id": string,
  "reacting_profile_url": string,
  "reacting_profile_identifier": string,
  "reacting_profile_name": string | null,
  "reaction_action": string | null,
  "reaction_target": string | null,
  "post_id": string | null,
  "post_urn": string | null,
  "post_url": string | null,
  "post_text": string | null,
  "post_created_at": string | null,
  "post_created_at_timestamp": integer | null,
  "post_relative_age": string | null,
  "post_is_repost": boolean | null,
  // + 25 more fields
}

Input parameters

3 parameters you can set for each run.

parameter	type	description
`profile_urls`required	array	LinkedIn Profile URLs Required. Add 1–1,000 public LinkedIn profile URLs in linkedin.com/in/… format. Regional LinkedIn hosts are accepted. Tracking parameters, fragments, and trailing slashes are removed.
`max_reactions_per_profile`	integer	Maximum reactions per profile Maximum number of unique reaction records to save for each profile. Enter 0 to fetch all available reactions, with a 100-page safety cap per profile.
`posted_within`	string	Reacted post age Only save reactions to posts published within this time window. Choose Any time to keep all available reactions. options: any, 24h, week, month, 3months, 6months, year

Output fields

Each result is one row with these 39 fields, taken from the scraper's dataset schema.

field	type	description
`reaction_id`	string	Deterministic SHA-256 identity for this profile and reacted-to post.
`reacting_profile_url`	string	Canonical LinkedIn profile URL supplied in the input.
`reacting_profile_identifier`	string	Public identifier from the canonical profile URL.
`reacting_profile_name`	string \| null	Display name parsed from the public reaction action when the action follows a recognized form.
`reaction_action`	string \| null	Public action label such as “Name likes this”. It does not claim an exact reaction subtype beyond the supplied label.
`reaction_target`	string \| null	Type of content that received the reaction, such as Post.
`post_id`	string \| null	Numeric LinkedIn post ID stored as a string for precision safety.
`post_urn`	string \| null	Source post URN, or a URN derived from an unambiguous post URL.
`post_url`	string \| null	Canonical reacted-to LinkedIn post URL with tracking parameters removed.
`post_text`	string \| null	Post text
`post_created_at`	string \| null	UTC publication timestamp of the reacted-to post. This is not a reaction timestamp.
`post_created_at_timestamp`	integer \| null	Unix timestamp in milliseconds for post_created_at.
`post_relative_age`	string \| null	Source display label such as 1d; not used for exact chronological calculations.
`post_is_repost`	boolean \| null	Post is repost
`post_is_edited`	boolean \| null	Post is edited
`total_reaction_count`	integer \| null	Aggregate reactions reported for the post at fetch time.
`post_comment_count`	integer \| null	Comment count
`post_share_count`	integer \| null	Share count
`like_reaction_count`	integer \| null	Like reactions
`praise_reaction_count`	integer \| null	Praise reactions
`empathy_reaction_count`	integer \| null	Empathy reactions
`appreciation_reaction_count`	integer \| null	Appreciation reactions
`interest_reaction_count`	integer \| null	Interest reactions
`entertainment_reaction_count`	integer \| null	Entertainment reactions
`other_reaction_count`	integer \| null	Reactions not represented by the six named columns, including any gap between the total and supplied breakdown.
`reaction_breakdown`	array	Aggregate reacted-to post reaction counts. This is not the queried profile's exact reaction subtype.
`post_author_id`	string \| null	Source author URN or ID when supplied; never inferred from a public identifier.
`post_author_identifier`	string \| null	Post author identifier
`post_author_type`	string	Post author type
`post_author_name`	string \| null	Post author name
`post_author_headline`	string \| null	Post author headline
`post_author_linkedin_url`	string \| null	Post author LinkedIn URL
`post_author_image_url`	string \| null	Current source-hosted image URL; it can expire.
`attachments`	array	Attachment objects supplied for the post, preserved without dropping source fields.
`mentions`	array	Mention objects supplied for the post, preserved without dropping source fields.
`shared_post`	object \| null	Shared-post context when supplied, preserved as a nested object.
`input_index`	integer	Zero-based position of the normalized profile URL in the input.
`reaction_index`	integer	Zero-based item order for this profile after filtering and duplicate removal.
`fetched_at`	string	UTC timestamp shared by rows from the same profile operation.

Pricing

Pay-per-event pricing, billed through your Apify account. Where plan tiers are listed, paid Apify plans get a lower price per event.

event	price	per 1,000, by Apify plan
Profile reaction result One unique reacted-to LinkedIn post written to the default dataset.	$0.002 each	$2.00 on every plan

Questions

How much does LinkedIn Profile Reactions cost?

LinkedIn Profile Reactions uses pay-per-event pricing on Apify. The main charge is $0.002 per profile reaction result, which is $2.00 per 1,000.

Do I need to log in to LinkedIn or share cookies?

No. LinkedIn Profile Reactions works without your LinkedIn login or cookies. You only need an Apify account to run it.

Can I use LinkedIn Profile Reactions through an API?

Yes. Send a POST request to the Apify API with your input and read the results as JSON, or use Apify's official clients for JavaScript and Python. The code examples on this page are ready to copy.

What data does LinkedIn Profile Reactions return?

Each result is a structured row. Its dataset schema lists 39 fields, including reaction_id, reacting_profile_url, reacting_profile_identifier, reacting_profile_name, and reaction_action.

What formats can I export?

Results are stored in an Apify dataset. You can read it through the API as JSON, or download it as CSV, Excel, XML or HTML.

LinkedIn Profile Reactions

LinkedIn Profile Reactions specifications

Run it from code

Input parameters

Output fields

Pricing

Questions

More LinkedIn scrapers

LinkedIn Profile Scraper

LinkedIn Profile Posts Scraper

LinkedIn Post Reactions

LinkedIn Profile Engagers Scraper

LinkedIn Profile Comments

LinkedIn Post Performance Scraper