linkedin.post_reactions

beta 2 credits needs a pack

People who reacted to a LinkedIn post.

GET /v1/linkedin/post_reactions

What you get#

A list of LinkedIn results in Onekey's unified shape, in data (an array). An empty array is a normal, successful answer and is charged like any other; a source that reports "nothing found" as an error returns a free 404 not_found instead.

Pagination: 2 results per page. The response carries a pagination block; send its next_cursor back as the cursor parameter to get the next page. Every page is one call at the price below. See Pagination.

Also known as: /linkedin/post/reactions on APIs that nest their paths. See Alternatives and equivalents.

What it costs#

2 credits for a fresh fetch, charged only when it succeeds.
Free when served from cache (0.2 credit for a cached response over 100 KB).
Free if the request is invalid (never charged) or the source fails or reports not found (refunded).

Parameters#

Name	Type	Required	Default	What it is	Constraints
`url`	string	yes	(required)	Full URL of the LinkedIn post carrying its activity id, e.g. https://www.linkedin.com/feed/update/urn:li:activity:7000000000000000000	max 500 chars; must match `https://([a-z]{2,3}\.)?linkedin\.com/[A-Za-z0-9\-_%./:()?=&+~@,]{1,400}`; trimmed
`cursor`	string	no	-	Opaque cursor from a previous response's `pagination.next_cursor`. Omit for the first page.	-

Request#

curl "https://api.onekey.dev/v1/linkedin/post_reactions?url=https%3A%2F%2Fwww.linkedin.com%2Ffeed%2Fupdate%2Furn%3Ali%3Aactivity%3A7000000000000000000" \
  -H "x-api-key: YOUR_API_KEY"

Try it

Add your key to run this call right here. No key? Get one free. The key stays in this tab.

Recorded response#

A real LinkedIn response, recorded and returned in Onekey's shape. Fields the platform does not provide are null.

json

{
  "success": true,
  "data": [
    {
      "author": {
        "displayName": "Example name 0",
        "bio": "Example headline 0",
        "url": "https://www.linkedin.com/in/example-0"
      },
      "ext": {
        "reactionType": "Example reactionType 0"
      }
    },
    {
      "author": {
        "displayName": "Example name 1",
        "bio": "Example headline 1",
        "url": "https://www.linkedin.com/in/example-1"
      },
      "ext": {
        "reactionType": "Example reactionType 1"
      }
    }
  ],
  "metadata": {
    "platform": "linkedin",
    "endpoint": "post_reactions",
    "cached": false,
    "stale": false,
    "age_s": 0,
    "fetched_at": "2026-01-01T12:00:00+00:00",
    "credits_charged": 2,
    "request_id": "7f3a9c2e5b1d4c8fa2e6d0b9c4f18e37"
  },
  "error": null
}

Field mapping#

How this endpoint's source fields become Onekey's unified schema. Fields the source lacks come back as null.

Source path	Onekey field	Transform
`name`	`author.displayName`	-
`headline`	`author.bio`	-
`url`	`author.url`	`safeUrl`
`reactionType`	`ext.reactionType`	-

Caching and freshness#

Fresh for about 2 minutes. Repeat calls in that window are served from cache and are free.
Between 2 minutes and 15 minutes the cached copy is still served instantly and marked stale: true while Onekey refreshes it in the background.
If the source is down when a refresh is needed, the last copy can be served for up to 1 hour more (marked stale).
A "not found" is remembered for 1 minute and is free.
The cache is shared across all customers, which is what keeps repeat calls cheap.

What can go wrong#

Status	Code	What to do
401	`unauthorized`	Check the `x-api-key` header.
402	`insufficient_credits`	Add credits; your balance must cover the price.
404	`not_found`	Unknown endpoint path.
422	`invalid_params`	Fix the parameters using the table above. Free.
429	`rate_limited`	Wait `Retry-After` seconds, then retry.
502	`upstream_error`	The source failed. Refunded; retry with backoff.

See Errors for the full list and retry guidance.

Status: beta (not yet verified against the live source).