Get Post Engagement
Posts
Get Post Engagement
Fetch a post’s comments and reactions in a single call
GET
Get Post Engagement
Endpoint
/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-abcdurn:li:activity:7287782484287606784urn: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.400—MISSING_PARAMETER,INVALID_URN401—INVALID_API_KEY404—POST_NOT_FOUND402—QUOTA_EXHAUSTED429—RATE_LIMITED(also returned when the endpoint’s 2-unit cost exceeds your per-second limit)500—INTERNAL_ERROR503—SERVICE_UNAVAILABLE
Pagination
The two lists paginate independently:- Comments paginate by token: pass
commentPaginationTokenfrom the previous response, and stop whencommentsHasMoreisfalse. - Reactions paginate by offset: increment
reactionStartbyreactionCount, and stop whenreactionsHasMoreisfalse.
/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
Query Parameters
Professional post URL or URN
Number of comments to fetch (1-100)
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.
Token for the next page of comments
Number of reactions to fetch (1-100)
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.