LinkedIn API

LinkedIn Post reactions API

List who reacted to a LinkedIn post - reactor name, profile URL, job title, and reaction type. Lead-gen grade.

$2.90/1k req, pay per request, no subscription.

What the API returneditems[0]
{
"id": "urn:li:reaction:(urn:li:activity:7475945433668694017,PRAISE)",
"reactionType": "PRAISE",
"postId": "urn:li:activity:7475945433668694017",
"actor": {...}
}
Uptime
100.00%
30d · 4,257 calls
Requests
4,257
30d · weekly, last 12 wks
Response
1.5s
median · 30d

Pricing and providers

LinkedIn Post reactions API pricing: one API, 3 interchangeable providers

The cheapest provider serves first. If it fails, the next one takes over in the same call.

You pay
$29.00
$2.90/1k req, only for what you use. No monthly plan.
Your first 34 requests are free with the $0.10 starting balance.

Try it

Get LinkedIn post reactions in one request

requireFieldsarray
Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `postId`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. Naming a combination that no single source returns together is refused as invalid input, with no charge.
Open in
Get a free key
Sample response
Free runs return only the first 3 results. Fund a key to get the full response.

This sample shows 12 of 13 fields. See every field

{
  "found": true,
  "data": {
    "items": [
      {
        "id": "urn:li:reaction:(urn:li:activity:7475945433668694017,PRAISE)",
        "reactionType": "PRAISE",
        "postId": "urn:li:activity:7475945433668694017",
        "actor": {
          "id": "ACoAAB4nQpEB7dTr9-fkPmWzX2r8qHsY4L6n1cA",
          "name": "Priya Raghunathan",
          "linkedinUrl": "https://www.linkedin.com/in/priya-raghunathan-devrel",
          "position": "Developer Relations Lead at Northwind Cloud",
          "pictureUrl": "https://media.licdn.com/dms/image/v2/D4E03AQFbQ1cWJx8pZg/profile-displayphoto-shrink_400_400/priya-raghunathan.jpg"
        }
      },
      {
        "id": "urn:li:reaction:(urn:li:activity:7475945433668694017,LIKE)",
        "reactionType": "LIKE",
        "postId": "urn:li:activity:7475945433668694017",
        "actor": {
          "id": "ACoAAC91LmVJ3fRk2tXqZpY7wVh8oT5nB2mC9xY",
          "name": "Declan Foster",
          "linkedinUrl": "https://www.linkedin.com/in/declan-foster-pm",
          "position": "Senior Product Manager, Copilot Platform",
          "pictureUrl": "https://media.licdn.com/dms/image/v2/D4E03AQGxK9nWvR2tPd/profile-displayphoto-shrink_400_400/declan-foster.jpg"
        }
      },
      {
        "id": "urn:li:reaction:(urn:li:activity:7475945433668694017,ENTERTAINMENT)",
        "reactionType": "ENTERTAINMENT",
        "postId": "urn:li:activity:7475945433668694017",
        "actor": {
          "id": "ACoAAD2mPqW5xHnR8sVkJ4tY6wZ1oC3bL7nA0eF",
          "name": "Mei Lin Zhao",
          "linkedinUrl": "https://www.linkedin.com/in/meilinzhao",
          "position": "Founder at Loomwork Studio",
          "pictureUrl": "https://media.licdn.com/dms/image/v2/D4E03AQH8vRk2nWzYpX/profile-displayphoto-shrink_400_400/mei-lin-zhao.jpg"
        }
      }
    ]
  }
}

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-31 · uptime and latency measured over 30d

Request body

JSON, posted to this endpoint.

  • urlstring

    https://www.linkedin.com/posts/satyanadella_today-were-bringing-skills-to-copilot-for-activity-7475945433668694017--kvG

    URL of the LinkedIn post to list reactions for (a /posts/...-activity-... or /feed/update/urn:li:activity:... link).

  • limitinteger

    5

    Maximum number of reactions to return (1-100, default 100).

  • requireFieldsarray

    Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `postId`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. Naming a combination that no single source returns together is refused as invalid input, with no charge.

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

    ACoAAB4nQpEB7dTr9-fkPmWzX2r8qHsY4L6n1cA

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

  • linkedinUrlstring

    https://www.linkedin.com/in/priya-raghunathan-devrel

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

  • namestring

    Priya Raghunathan

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

  • pictureUrlstring

    https://media.licdn.com/dms/image/v2/D4E03AQFbQ1cWJx8pZg/profile-displayphoto-shrink_400_400/priya-raghunathan.jpg

    Profile picture URL of the reactor.

  • positionstring

    Developer Relations Lead at Northwind Cloud

    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 post, one record per reactor.

  • idstring

    urn:li:reaction:(urn:li:activity:7475945433668694017,PRAISE)

    LinkedIn identifier of the reaction.

  • postIdstringcan require

    urn:li:activity:7475945433668694017

    LinkedIn URN of the post that was reacted to.

  • reactionTypestring

    PRAISE

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

top level
  • foundboolean

    true

  • 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 Post reactions API

The AnyAPI LinkedIn Post reactions API returns LinkedIn post reactions data as normalized JSON from one POST call to /v1/run/linkedin.post_reactions. List who reacted to a LinkedIn post - reactor name, profile URL, job title, and reaction type. Lead-gen grade. AnyAPI routes each request across 3 sources and falls back automatically when one fails. It costs from $2.90 per 1,000 requests, in US dollars with no subscription and no monthly minimum. Over the last 30 days, 100.0% of LinkedIn post reactions calls through AnyAPI succeeded, with a median response time of 1.5 seconds across 4,257 measured calls.

It costs from $2.90 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 LinkedIn post - reactor name, profile URL, job title, and reaction type. Lead-gen grade. 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 post reactions calls through AnyAPI succeeded, with a median response time of 1.5 seconds across 4,257 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 34 LinkedIn Post reactions calls at $0.0029 each.

AnyAPI asks the next of its 3 sources in the same request, cheapest first, so one source going down does not fail your call.

Send a POST request to https://api.getanyapi.com/v1/run/linkedin.post_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.