LinkedIn API

LinkedIn Comment reactions API

List who reacted to a comment on a LinkedIn post - reactor name, profile URL, job title, and reaction type, 100 per page.

POST/v1/run/linkedin.comment_reactions
Uptime
100.00%
30d · 1 call
Requests
1
30d
Response
1.4s
median · 30d

Pricing

LinkedIn Comment reactions API pricing

Providers
Hedgehog1 served100.00% uptime1270ms p50$2.60/1k reqflat
You pay
$26.00
$2.60/1k req, only for what you use. No monthly plan.
Your first 38 requests are free with the $0.10 starting balance.

Try it

Get LinkedIn comment reactions in one request

Open in
Get a free key
Sample response
Free runs return only the first 3 results. Fund a key to get the full response.
{
  "data": {
    "items": [
      {
        "actor": {
          "id": "a1b2c3d4",
          "image": "https://example.com/image.jpg",
          "linkedinUrl": "https://example.com/page",
          "name": "Example title",
          "position": "example"
        },
        "commentUrn": "example",
        "id": "a1b2c3d4",
        "reactionType": "general"
      }
    ],
    "page": 29,
    "totalPages": 12500,
    "totalResults": 12500
  },
  "found": true,
  "reason": "not_found"
}

Full parameter and response reference - every field, type, and example for this endpoint.

Reference

One request, one response shape.

Every field you send and every field you get back, each with a real example.

Last verified 2026-10-23 · uptime and latency measured over 30d

Request body

JSON, posted to this endpoint.

  • urlstring

    https://www.linkedin.com/feed/update/urn:li:activity:7510715600319467520?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7510715600319467520%2C7510768837462745088%29&dashCommentUrn=urn%3Ali%3Afsd_comment%3A%287510768837462745088%2Curn%3Ali%3Aactivity%3A7510715600319467520%29

    LinkedIn comment URL, as returned in the url field of linkedin.post_comments or copied with "Copy link to comment" (a /feed/update/... link carrying commentUrn and dashCommentUrn). A post URL without dashCommentUrn, or a reply's URL (carrying replyUrn), is refused as invalid input, with no charge.

  • pageinteger

    Which page of up to 100 reactions to return, starting at 1 (default 1). Each page is billed as one request; totalPages in the response says how many there are.

You send. A small JSON body. The values shown are examples to replace with your own.

Response

JSON, one example value per field.

actordata.items[].actor

The reactor - the person or company that reacted.

  • idstring

    LinkedIn member or company id of the reactor. Populated whenever the provider has data for the entity.

  • imagestring

    Profile picture URL of the reactor.

  • linkedinUrlstring

    Canonical LinkedIn profile or company URL of the reactor. Populated whenever the provider has data for the entity.

  • namestring

    Full name of the reactor (or company name). Populated whenever the provider has data for the entity.

  • positionstring

    Reactor's current job title / headline (or follower count for a company). Populated whenever the provider has data for the entity.

each itemdata.items[]

Reactions on the comment, one record per reactor, newest first.

  • commentUrnstring

    LinkedIn URN of the comment that was reacted to, naming its post and the comment id (e.g. urn:li:comment:(activity:7510715600319467520,7510768837462745088)).

  • idstring

    LinkedIn identifier of the reaction.

  • reactionTypestring

    Reaction kind (e.g. LIKE, PRAISE, EMPATHY, INTEREST, APPRECIATION, ENTERTAINMENT).

datadata

The comment reactions result, or null when not found.

  • pageinteger

    The page this response holds, starting at 1.

  • totalPagesinteger

    How many pages of up to 100 reactions the comment has.

  • totalResultsinteger

    How many reactions the comment has in total, across every page.

top level
  • foundboolean

    Whether the comment was found with at least one reaction on the requested page.

  • reason"not_found"

    Present only when `found` is false, and says why there is no result. `not_found`: the source states the target does not exist, or returned nothing for it. A `found: false` answer is a successful call, not an error, and `costUsd` is what it actually cost.

You get back. Named, typed fields in the same shape whichever source answers.

FAQ

About the LinkedIn Comment reactions API

The AnyAPI LinkedIn Comment reactions API returns LinkedIn comment reactions data as normalized JSON from one POST call to /v1/run/linkedin.comment_reactions. List who reacted to a comment on a LinkedIn post - reactor name, profile URL, job title, and reaction type, 100 per page. AnyAPI returns one normalized schema whichever source serves it. It costs from $2.60 per 1,000 requests, in US dollars with no subscription and no monthly minimum. Over the last 30 days, 100.0% of LinkedIn comment reactions calls through AnyAPI succeeded, with a median response time of 1.4 seconds across 1 measured calls.

It costs from $2.60 per 1,000 requests, in US dollars with no subscription and no monthly minimum. You fund one USD wallet and each call draws it down. Some failed wallet-funded requests incur processing charges that we pass through at cost, with no markup; the error response shows the amount charged.

List who reacted to a comment on a LinkedIn post - reactor name, profile URL, job title, and reaction type, 100 per page. The response is normalized JSON with the same envelope every AnyAPI endpoint returns, so parsing a second endpoint is a change of URL and nothing else.

Over the last 30 days, 100.0% of LinkedIn comment reactions calls through AnyAPI succeeded, with a median response time of 1.4 seconds across 1 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.

Yes. A new AnyAPI account starts with $0.10 of free balance and no card required, which covers 38 LinkedIn Comment reactions calls at $0.0026 each.

Send a POST request to https://api.getanyapi.com/v1/run/linkedin.comment_reactions with your AnyAPI key in an "Authorization: Bearer" header and the input as a JSON body. The same key and the same wallet work on every AnyAPI endpoint.

No. You add US dollars to one prepaid AnyAPI balance and each request draws it down. There is no monthly plan and no minimum, and the same balance pays for every AnyAPI endpoint.

Yes. Install @getanyapi/sdk from npm for TypeScript or getanyapi from pip for Python. Both call every AnyAPI endpoint with the same key, and any HTTP client works too.

Yes. An agent can connect to the AnyAPI MCP server at https://api.getanyapi.com/mcp, or create its own free-trial key with one unauthenticated POST to https://api.getanyapi.com/agent/signup and call this endpoint over HTTP.