LinkedIn Reactions
Reactors on any post. Full profile data per reactor.
per event $0.004
What it does
Returns every person who reacted to a given LinkedIn post, with full profile data per reactor. Useful for engagement-based prospecting, audience analysis, and converting post engagement into outbound lists.
Input
Request body
| Field | Type | Description | |
|---|---|---|---|
| posts | string[] | required | LinkedIn post URLs to extract reactions from. |
| maxReactions | number | optional | Max reactions per post. Default: unlimited. |
Output
Reaction object
| Field | Type | Description | |
|---|---|---|---|
| reactionType | string | required | LIKE, CELEBRATE, SUPPORT, LOVE, INSIGHTFUL, or FUNNY. |
| reactor | object | required | Full profile of the reactor — name, headline, profileUrl, company. |
| reactedAt | ISO date | optional | When the reaction was made, if available. |
| postUrn | string | required | URN of the post that was reacted to. |
Example request
curl -X POST \
"https://api.apify.com/v2/acts/E9scDfvTXSpc1bFNE/runs?token=YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"posts": ["https://www.linkedin.com/feed/update/urn:li:activity:..."]
}' Features
- Auto-pagination — all reactions returned, no cursor handling on your side.
- Full profile per reactor — headline, current company, profile URL included by default.
- Classified errors — every error is tagged
client(your input/access) ortransient(our side or upstream), so your retry logic stays clean. - No LinkedIn account — zero account-burning risk.
Errors & limits
INVALID_INPUT— malformed post URL.POST_NOT_FOUND— post is private, deleted, or you don't have access.RATE_LIMITED— temporary throttle; retry with backoff.
Changelog
- 1.0.37 — every error is now tagged
clientortransientin the response body. - 1.0.36 — reactor company field added.
AT SCALE
Running high volumes?
Skip the marketplace tiers and get unit pricing scoped to your real call volume — direct line to the team that runs the pipeline.
Get volume pricing