Do I need a LinkedIn developer account?

No. There is no LinkedIn app, OAuth flow or app review. One InsightSocial API key works for this endpoint and every other platform, and your first 10 calls priced at 100 credits or less are free.

How do I get every result, not just the first page?

This endpoint pages. Each response carries pagination.next_cursor and pagination.has_more. Send next_cursor back unchanged as the cursor parameter and stop when has_more is false. Every page is a separate call and is charged as one.

What happens if the account is private or nothing is found?

You get an error or an empty result, and it costs 0 credits. The API reads public LinkedIn data only, so private accounts and deleted content come back as not found rather than as partial data.

Can I call the LinkedIn Post Reactions API from Claude, ChatGPT or Cursor?

Yes. Add the hosted MCP server at https://api.insightsocial.app/mcp to your AI app and sign in. The assistant finds this endpoint by name, shows its price and calls it with your credits.

GET /v1/linkedin/post/reactions

LinkedIn Post Reactions API

Returns the people who reacted to a LinkedIn post, each with their name, headline, profile URL, and the reaction they left.

Get a free API key Full API reference

100–500 credits, metered · cursor pagination · failed calls free · 10 free calls to start

curl "https://api.insightsocial.app/v1/linkedin/post/reactions?url=https%3A%2F%2Fwww.linkedin.com%2Ffeed%2Fupdate%2Furn%3Ali%3Aactivity%3A7501466755261820928" \
-H "x-api-key: $INSIGHTSOCIAL_API_KEY"

200 OKJSON

{
"success": true,
"platform": "linkedin",
"endpoint": "/v1/linkedin/post/reactions",
"schema_version": "2",
"data": {
"items": [
{
"author": {
"id": "<string>",
"username": "<string | null>",
"display_name": "<string | null>",
"avatar_url": "<string | null>",
"bio": "<string | null>",
"verified": "<boolean | null>",
"followers": "<integer | null>",
"followers_approximate": "<boolean | null>",
"following": "<integer | null>",
"posts_count": "<integer | null>",
"likes_count": "<integer | null>",
"url": "<string | null>",
"location": "<string | null>",
"external_url": "<string | null>",
"private": "<boolean | null>",
"joined_at": "<string | null>",
"last_post_at": "<string | null>",
"ext": "<object | null>"
}
}
],
"total": "<integer | null>",
"truncated": "<boolean | null>"
},
"pagination": {
"next_cursor": "<string | null>",
"has_more": "<boolean>"
},
"unavailable": [],
"credits_used": "<integer>"
}

When to use it

Use it to see who liked or praised a post, optionally filtered by type; post/comments covers the people who wrote a comment.

Parameters

Query parameters for GET /v1/linkedin/post/reactions. Send your key in the x-api-key header.

Name	Required	Description
url	Yes	Full URL of the LinkedIn post. It has to carry the post's ACTIVITY id, either https://www.linkedin.com/feed/update/urn:li:activity:<id> or https://www.linkedin.com/posts/<slug>-activity-<id>-<code>. Every endpoint that lists posts publishes the activity form as post.url, so copy that field rather than rebuilding the URL from post.id, which is not always the activity id.
page	No	1-based page number. Defaults to 1.
type	No	Filter by kind. See the allowed values.
include	No	Set to profile (one token only) to join every row to the member's profile lookup in this one call: author.followers becomes the exact count and followers_approximate reads false on every row the lookup filled, author.following is filled with the member's connection count, and the location, joined date, country, website, cover image and profile flags land where the row lacks them.
limit	No	Take the top N rows of this page (1 to 10). The page cursor still advances past the full page of 10, so the rows past your limit are skipped, not carried to the next page.
cursor	No	The pagination.next_cursor from the previous page, sent back unchanged. Omit it for the first page.

Response fields

The same unified schema every platform returns, so code written for LinkedIn works on the other eight. A field the platform did not provide is null and listed in unavailable.

Field	Type	Notes
id	string	An identifier, always a string. Never parse it as a number: several platforms use ids above 2^53.
username	string \| null
display_name	string \| null
avatar_url	string \| null
bio	string \| null
verified	boolean \| null
followers	integer \| null	A count. null when the platform does not expose it; 0 only when it is really zero.
followers_approximate	boolean \| null
following	integer \| null	A count. null when the platform does not expose it; 0 only when it is really zero.
posts_count	integer \| null	A count. null when the platform does not expose it; 0 only when it is really zero.
likes_count	integer \| null	A count. null when the platform does not expose it; 0 only when it is really zero.
url	string \| null
location	string \| null
external_url	string \| null
private	boolean \| null
joined_at	string \| null	ISO-8601 timestamp in UTC, ending in Z.
last_post_at	string \| null	ISO-8601 timestamp in UTC, ending in Z.
ext	object \| null	Platform-specific fields, snake_case.

Every field, error and example is in the LinkedIn Post Reactions API reference.

How much does the LinkedIn Post Reactions API cost?

Metered: 100–500 credits a call. The ceiling is reserved when the call starts and you are charged what it actually read.

Failed calls are free
A call that errors or finds nothing costs 0 credits.
Know the price first
Add dry_run=1 and the response quotes the call without making it. Nothing is charged.
One balance
API calls and Chrome extension exports share the same credits, on the free plan too.

See plans and credit packs How credits work