Skip to main content
GET
Get Post Engagement

Endpoint

Returns both the comments and the reactions of a professional post in one request. Use this instead of calling /post/comments and /post/reactions separately when you need both.
This endpoint bills 2 credits and counts as 2 units against your per-second rate limit. It is all-or-nothing: if either half cannot be fetched, the whole request returns an error and 0 credits are charged. Because it costs 2 rate-limit units, your plan’s per-second limit must be at least 2 to call it.

Authentication

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
integer
default:"100"
Number of comments to fetch (1–100).
integer
default:"0"
Comments offset (kept for parity; comments primarily paginate by token).
string
Token from a previous response used to fetch the next page of comments.
integer
default:"100"
Number of reactions to fetch (1–100).
integer
default:"0"
Reactions offset for pagination.

Response

string
The resolved post identifier you passed in.
array
Array of comments (same object shape as Get Post Comments).
string
Token to fetch the next page of comments. Absent when there are no more.
boolean
Whether more comments are available.
array
Array of reactions (same object shape as Get Post Reactions).
boolean
Whether more reactions are available.

Example Request

Example Response

Errors

See Error Handling for the full list of error codes and recommended handling.
  • 400MISSING_PARAMETER, INVALID_URN
  • 401INVALID_API_KEY
  • 404POST_NOT_FOUND
  • 402QUOTA_EXHAUSTED
  • 429RATE_LIMITED (also returned when the endpoint’s 2-unit cost exceeds your per-second limit)
  • 500INTERNAL_ERROR
  • 503SERVICE_UNAVAILABLE

Pagination

The two lists paginate independently:
  • Comments paginate by token: pass commentPaginationToken from the previous response, and stop when commentsHasMore is false.
  • Reactions paginate by offset: increment reactionStart by reactionCount, and stop when reactionsHasMore is false.
Every call to /post/engagement bills 2 credits and 2 rate-limit units, so if you only need to deep-paginate one of the two lists, use the dedicated /post/comments or /post/reactions endpoint (1 credit each) instead.

Notes

Billing is all-or-nothing: 2 credits when both lists are returned, 0 credits if the request errors. There is no partial result.

Authorizations

X-API-Key
string
header
required

Query Parameters

postUrlOrUrn
string
required

Professional post URL or URN

commentCount
integer
default:100

Number of comments to fetch (1-100)

commentStart
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.

commentPaginationToken
string

Token for the next page of comments

reactionCount
integer
default:100

Number of reactions to fetch (1-100)

reactionStart
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.

Response

Combined comments and reactions

post
string

The resolved post identifier

comments
object[]

Comments (same shape as GET /post/comments)

commentsPaginationToken
string

Token for the next page of comments (absent when none)

commentsHasMore
boolean
reactions
object[]
reactionsHasMore
boolean