Skip to main content
GET
Get reactions on a post

Endpoint

Authentication

Include your API key in the request header:

Parameters

string
required
Professional post URL or URN.Examples:
  • https://www.linkedin.com/posts/username_some-post-slug-1234567890-abcd
  • urn:li:activity:7287782484287606784
  • urn:li:ugcPost:7287782484287606784
  • urn:li:groupPost:4521873-7287782484287606784 — a post published in a group, as urn:li:groupPost:<groupId>-<postId> or any URL containing it. A post in a private group is visible to the group’s members only and answers 404 POST_NOT_FOUND, like a deleted post.
A repost without commentary answers with the original post’s reactions, as Get Post Comments does with comments.
integer
default:"100"
Number of reactions to fetch per page.
  • Minimum: 1
  • Maximum: 100
  • Default: 100
integer
default:"0"
Offset for pagination.
  • Default: 0

Response

array
Array of reactions on the post
integer
Number of reactions the source reports for the post. Omitted when it reports none. A complete walk can end a few short of it, because the source withholds a few reactors.
boolean
Indicates whether there are more reactions to fetch.

Example Request

Example Response

Errors

See Error Handling for the full list of error codes and recommended handling.
  • 400 — MISSING_PARAMETER, INVALID_URN
  • 401 — INVALID_API_KEY
  • 404 — POST_NOT_FOUND
  • 402 — QUOTA_EXHAUSTED
  • 429 — RATE_LIMITED
  • 500 — INTERNAL_ERROR
  • 503 — SERVICE_UNAVAILABLE

Pagination

To fetch all reactions from a post with many reactions, use offset pagination:
  1. Make an initial request with start=0
  2. If hasMore is true, increment start by count in your next request
  3. Continue until hasMore is false
A complete walk can collect a few reactions fewer than total: the source withholds a few reactors from the list while still counting them.

Notes

This endpoint consumes 1 credit from your credit balance per API call, regardless of the count parameter value. Errors are free — with one exception: a 404 not found costs 1 credit. See Quotas.
You can pass either a professional post URL (e.g. https://www.linkedin.com/posts/...) or a post URN (e.g. urn:li:activity:...). When a URL is provided, the API automatically resolves it to the correct activity URN.

Authorizations

X-API-Key
string
header
required

Query Parameters

postUrlOrUrn
string
required

Professional post URL or URN: urn:li:activity:<id>, urn:li:ugcPost:<id>, a group post as urn:li:groupPost:<groupId>-<postId>, or any post URL containing one.

Example:

"https://www.linkedin.com/posts/username_post-slug-1234567890-abcd"

count
integer
default:100

Number of reactions to fetch (default: 100)

Required range: 1 <= x <= 100
start
integer
default:0

Offset of the first item to return. This endpoint pages by offset: advance start by the number of items you received. Keep requesting while hasMore is true; an empty page ends the list.

Required range: x >= 0

Response

Successfully fetched post reactions

reactions
object[]
total
integer

Number of reactions the source reports for the post. Omitted when it reports none. A complete walk can end a few short of it, because the source withholds a few reactors.

hasMore
boolean

Whether more reactions are available