LinkedIn Social Activity

Use the social activity endpoints when you already know the public URL of a LinkedIn post and need structured post or engagement data.

Endpoints

Endpoint	Returns
`POST /linkedin-post`	Post text, author, timestamps, engagement, media, reshared content, and initial comments
`POST /linkedin-post-reactions`	People who reacted and their reaction types
`POST /linkedin-post-comments`	Comments, authors, timestamps, permalinks, and engagement

All three endpoints accept a public LinkedIn post URL containing an activity, ugcPost, or share identifier. Pricing is plan-specific; see GET /pricing.

Get post details

curl --request POST \
  --url https://api.tryhuntr.com/linkedin-post \
  --header 'content-type: application/json' \
  --header "x-api-key: ${HUNTR_API_KEY}" \
  --data '{
    "post_url": "https://www.linkedin.com/feed/update/urn:li:activity:7430337505431957506"
  }'

The response includes result.post and any initial comments available in result.comments.

Get reactions

The first request needs only the post URL:

curl --request POST \
  --url https://api.tryhuntr.com/linkedin-post-reactions \
  --header 'content-type: application/json' \
  --header "x-api-key: ${HUNTR_API_KEY}" \
  --data '{
    "post_url": "https://www.linkedin.com/feed/update/urn:li:activity:7430337505431957506"
  }'

Each page contains up to 10 reactions. When pagination.has_more is true, pass pagination.token back with the same post URL:

{
  "post_url": "https://www.linkedin.com/feed/update/urn:li:activity:7430337505431957506",
  "pagination": {
    "token": "TOKEN_FROM_PREVIOUS_RESPONSE"
  }
}

Stop when pagination.has_more is false or pagination.token is null. The response provides the current page of people in result.reactions and the overall reaction count in top-level total.

Get comments

The first request needs only the post URL:

curl --request POST \
  --url https://api.tryhuntr.com/linkedin-post-comments \
  --header 'content-type: application/json' \
  --header "x-api-key: ${HUNTR_API_KEY}" \
  --data '{
    "post_url": "https://www.linkedin.com/feed/update/urn:li:activity:7430337505431957506"
  }'

Each page contains up to 100 comments. When pagination.has_more is true, pass pagination.token back with the same post URL:

{
  "post_url": "https://www.linkedin.com/feed/update/urn:li:activity:7430337505431957506",
  "pagination": {
    "token": "TOKEN_FROM_PREVIOUS_RESPONSE"
  }
}

Stop when pagination.has_more is false or pagination.token is null.

Build an engagement workflow

A typical workflow is:

Call /linkedin-post for the post content and aggregate engagement.
Paginate /linkedin-post-reactions to collect people who reacted.
Paginate /linkedin-post-comments to collect commenters and discussion context.
Use returned LinkedIn profile URLs with person enrichment endpoints when you need additional contact data.

Keep pagination state separate for each post. Reaction and comment tokens are opaque and must only be reused with the same post URL.

Getting started

Concepts

Guides

Build with AI

Integrations

Reference

LinkedIn Social Activity

Endpoints

Get post details

Get reactions

Get comments

Build an engagement workflow

Next step

​Endpoints

​Get post details

​Get reactions

​Get comments

​Build an engagement workflow

​Next step

Endpoints

Get post details

Get reactions

Get comments

Build an engagement workflow

Next step