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 Comments Replies 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/comments/replies

LinkedIn Post Comments Replies API

Q: How much does the LinkedIn Post Comments Replies API cost?

50 credits per successful call. A call that errors or finds nothing costs 0 credits, and an answer from the shared cache costs 2. Pro's 10,000 monthly credits cover about 200 calls at 50 credits each. Add dry_run=1 to see the price of a call without making it.

Returns the replies under one LinkedIn comment, each with the replier's name, reply text, reaction and reply counts, and timestamps.

Get a free API key Full API reference

50 credits a call · cursor pagination · failed calls free · 10 free calls to start

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

200 OKJSON

{
"success": true,
"platform": "linkedin",
"endpoint": "/v1/linkedin/post/comments/replies",
"schema_version": "2",
"data": {
"items": [
{
"comment": {
"id": "<string>",
"url": "<string | null>",
"parent_id": "<string | null>",
"post_id": "<string | null>",
"text": "<string | null>",
"author": {
"id": "<string | null>",
"username": "<string | null>",
"display_name": "<string | null>",
"avatar_url": "<string | null>",
"verified": "<boolean | null>"
},
"engagement": {
"likes": "<integer | null>",
"replies": "<integer | null>"
},
"flags": {
"pinned": "<boolean | null>",
"deleted": "<boolean>"
},
"published_at": "<string | null>",
"language": "<string | null>",
"replies": "<array | null>",
"ext": "<object | null>"
}
}
]
},
"pagination": {
"next_cursor": "<string | null>",
"has_more": "<boolean>"
},
"unavailable": [],
"credits_used": "<integer>"
}

When to use it

Use it after post/comments: pass that comment's comment_id together with the post url to expand a single thread.

Parameters

Query parameters for GET /v1/linkedin/post/comments/replies. 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.
comment_id	Yes	The parent comment's comment.id from /v1/linkedin/post/comments, or its comment.ext.urn (urn:li:comment:(ugcPost:<post>,<comment>)).
cursor	No	LinkedIn cursor.

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.
url	string \| null
parent_id	string \| null	An identifier, always a string. Never parse it as a number: several platforms use ids above 2^53.
post_id	string \| null	An identifier, always a string. Never parse it as a number: several platforms use ids above 2^53.
text	string \| null
author.id	string \| null
author.username	string \| null
author.display_name	string \| null
author.avatar_url	string \| null
author.verified	boolean \| null
engagement.likes	integer \| null	A count. null when the platform does not expose it; 0 only when it is really zero.
engagement.replies	integer \| null	A count. null when the platform does not expose it; 0 only when it is really zero.
flags.pinned	boolean \| null
flags.deleted	boolean
published_at	string \| null	ISO-8601 timestamp in UTC, ending in Z.
language	string \| null	The content's language as the platform states it, e.g. en, pt-BR. Detected languages come later (§7.1).
replies	array \| null
ext	object \| null	Platform-specific fields, snake_case.

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

How much does the LinkedIn Post Comments Replies API cost?

50 credits per successful call.

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