Get who reacted to a LinkedIn post
Fetch who reacted to one post, up to 100 a page: each person's or company page's name, headline and link, and which reaction. With comment_url, who reacted to one comment. LinkedIn lists people who react by member id, so actor.url is usually a member-id link (/in/ACoAA…) with vanity_name null; linkedin/profile takes it.
https://api.scrapefield.com/v1/linkedin/reactionshttps://api.scrapefield.com/v1/linkedin/reactions?url=https%3A%2F%2Fwww.linkedin.com%2Fposts%2Fferrari_ferrari-activity-7513660751346184192-VA32In your code
const params = new URLSearchParams({
"url": "https://www.linkedin.com/feed/update/urn:li:activity:7243000000000000000"
});
const res = await fetch(`https://api.scrapefield.com/v1/linkedin/reactions?${params}`, {
headers: { Authorization: `Bearer ${process.env.SCRAPEFIELD_KEY}` },
});
const { data, meta } = await res.json();
console.log(data, meta.credits_charged);Parameters
| Parameter | What it does |
|---|---|
url | The post's URL, as for linkedin/post. |
comment_url | A comment's URL: who reacted to that comment. |
cursor | The meta.next_cursor from the previous page. Omit for the first page. |
fresh | Skip the cache and fetch now. Charged normally. Not available on trial credits — buy any pack to unlock it. default false |
Response
Returns an array of linkedin_reaction. This is the demo’s answer, the one the playground above returns, in full rather than abbreviated — including the fields that come back null, because a field is null when the platform does not show it and you should know which ones those are before you build on them. A call with your key returns the account you ask for.
{
"data": [
{
"kind": "like",
"actor": {
"type": "person",
"vanity_name": null,
"url": "https://www.linkedin.com/in/ACoAA-6ZjSKcdkYW3EH-NAb0_Bzz2J2ByST2qeY/",
"full_name": "Sofia Ferrari",
"headline": "Backend Engineer at Northbank",
"location": null,
"services": []
}
},
{
"kind": "funny",
"actor": {
"type": "person",
"vanity_name": null,
"url": "https://www.linkedin.com/in/ACoAALuri8GciiuLE3n-mwslzqUsTYax80tB5vh/",
"full_name": "Petr Aydin",
"headline": "Founder at Ravel",
"location": null,
"services": []
}
}
],
"meta": {
"request_id": "req_7f3ac1e94b2d40f8a1c6e5d2",
"credits_charged": 7,
"credits_remaining": 74218,
"cached": false,
"fetched_at": "2026-09-20T09:12:03Z",
"next_cursor": "eyJwIjoxLCJzIjoiYTNmOSJ9"
}
}Fields of linkedin_reaction
A reaction to a LinkedIn post: who, and which. Named after the words LinkedIn prints, since LinkedIn has no official data API.
| Field | What it is |
|---|---|
kind | As LinkedIn's reaction menu names them. null for a kind it adds later.like · celebrate · support · love · insightful · funny |
actor | Who reacted: a person, or a company page. |
actor.type | A company page can comment and react as itself. person · company |
actor.vanity_name | The public name in the URL: after /in/ for a person, after /company/ for a company. null where LinkedIn gives only an id. |
actor.url | Their page. Where LinkedIn lists a person by member id, as it does a post's reactors, this is a member-id link (/in/ACoAA…). |
actor.full_name | The person's name, or the company's. |
actor.headline | The line under the name. For a company, LinkedIn prints its follower count here. |
actor.location | As printed. null in most lists. |
actor.services | What they offer, for someone found by linkedin/services. Empty in other lists. |
What it costs
7 credits per successful call, whether we fetch it or serve it from cache — you pay for the answer, not for how we produced it. Responses are cached for 3 hours and a cached one tells you when the data was actually fetched. A call we fail costs 0 and is refunded automatically.
On the smallest pack that is $5.46 per 1,000 calls; on the largest, $3.08. The full table.
Questions
How much does the LinkedIn post reactions API cost?
7 credits a call: $5.46 per 1,000 calls on the smallest pack and $3.08 on the largest. A call that fails costs nothing, and the refund is automatic. A cached answer costs the same as a fresh one. Credits are bought in packs and never expire; there is no subscription.
Do I need a LinkedIn account, a login or cookies?
No. You need a key from us and nothing from LinkedIn. We never take a customer's login, cookies or session, at any price, and no account of yours is ever at risk.
Can I try it without signing up?
Yes. Add demo=true and leave the key out, or press Send request in the playground on this page. The demo answers with a real answer about Ferrari, captured once a week, in exactly the shape a live call returns, whatever you ask, and charges nothing.
How fresh is the data?
An answer is kept for up to 3 hours, and a cached one says when it was fetched, in meta.fetched_at. Add fresh=true to fetch it again now, at the same price; it needs any purchase, not the trial.
What does it return?
A list of linkedin_reaction objects. Its fields are named after the words LinkedIn prints, since LinkedIn has no official data API. A field is null when LinkedIn does not show it, never missing. Every field is described on this page.
How do I get more than one page?
Pass meta.next_cursor back as cursor, and stop when it is null. Each page is a call, priced the same. A cursor lasts as long as the answer it belongs to is cached.
Can an AI agent call it?
Yes: it is the MCP tool get_linkedin_post_reactions on our MCP server, with the same parameters, answer and price. Without a key, the tool answers from the demo.