Get the comments on a LinkedIn post

Q: 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.

Q: What does it return?

A list of linkedin_comment 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.

Q: 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.

Q: Can an AI agent call it?

Yes: it is the MCP tool get_linkedin_post_comments on our MCP server, with the same parameters, answer and price. Without a key, the tool answers from the demo.

Fetch the comments on one post, up to 100 a page: each comment's text, author (name, headline, profile), published_at, like_count, reply_count and its own url, which opens the post at that comment. With comment_url, the replies to one comment. Use this to see who engages with a post and what they say.

7credits

GEThttps://api.scrapefield.com/v1/linkedin/comments

Try itno key needed7 credits on a real call · 0 here

urlone of the subject idscomment_urlone of the subject ids

https://api.scrapefield.com/v1/linkedin/comments?url=https%3A%2F%2Fwww.linkedin.com%2Fposts%2Fferrari_ferrari-activity-7513660751346184192-VA32

In 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/comments?${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` string · one of the subject ids	The post's URL, as for linkedin/post.
`comment_url` string · one of the subject ids	A comment's URL, as LinkedIn's "Copy link to comment" gives it: the replies to that comment.
`sort` string	Most relevant first, or newest first. relevance · newest
`cursor` string	The `meta.next_cursor` from the previous page. Omit for the first page.
`fresh` boolean	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_comment. 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": [
    {
      "id": "7290020740401249508",
      "url": "https://www.linkedin.com/feed/update/urn:li:activity:7243000000000000000",
      "post_urn": "urn:li:activity:7243000000000000000",
      "parent_id": null,
      "text": "Congratulations to the whole team.",
      "author": {
        "type": "person",
        "vanity_name": "karel-aydin-485179",
        "url": "https://www.linkedin.com/in/karel-aydin-485179/",
        "full_name": "Karel Aydin",
        "headline": "Data Engineer at Kestrel",
        "location": "Lisbon, Germany",
        "services": []
      },
      "published_at": "2026-09-15T00:01:11.000Z",
      "like_count": 6,
      "reply_count": 2
    },
    {
      "id": "7270855148447283108",
      "url": "https://www.linkedin.com/feed/update/urn:li:activity:7243000000000000000",
      "post_urn": "urn:li:activity:7243000000000000000",
      "parent_id": null,
      "text": "The part about the alert you kept is the useful bit. Which one was it?",
      "author": {
        "type": "person",
        "vanity_name": "tomas-novak-513413",
        "url": "https://www.linkedin.com/in/tomas-novak-513413/",
        "full_name": "Tomas Novak",
        "headline": "Founder at Ravel",
        "location": "Brooklyn, United States",
        "services": []
      },
      "published_at": "2026-09-10T08:41:55.000Z",
      "like_count": 82,
      "reply_count": 4
    }
  ],
  "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_comment`

A comment on a LinkedIn post. Named after the words LinkedIn prints, since LinkedIn has no official data API.

Field	What it is
`id` string	LinkedIn's id for the comment.
`url` URL · or null	The comment's own link, as LinkedIn's "Copy link to comment" gives it: it opens the post at this comment, and linkedin/comments and linkedin/reactions take it as `comment_url`. `null` for a reply whose link the source does not give.
`post_urn` string · or null	The post it is on, e.g. `urn:li:activity:7243…`.
`parent_id` string · or null	The comment it answers, for a reply.
`text` string · or null	The comment's text.
`author` object	Who wrote it.
`author.type` string, one of	A company page can comment and react as itself. person · company
`author.vanity_name` string · or null	The public name in the URL: after `/in/` for a person, after `/company/` for a company. `null` where LinkedIn gives only an id.
`author.url` 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…`).
`author.full_name` string · or null	The person's name, or the company's.
`author.headline` string · or null	The line under the name. For a company, LinkedIn prints its follower count here.
`author.location` string · or null	As printed. `null` in most lists.
`author.services` array of strings	What they offer, for someone found by linkedin/services. Empty in other lists.
`published_at` time, ISO 8601 UTC · or null	When it was posted. `null` when the source does not say.
`like_count` integer · or null	Reactions to the comment, all kinds together.
`reply_count` integer · or null	How many replies it has.

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 1 hour 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 comments 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 1 hour, 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_comment 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_comments on our MCP server, with the same parameters, answer and price. Without a key, the tool answers from the demo.