> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryhuntr.com/llms.txt
> Use this file to discover all available pages before exploring further.

# LinkedIn Social Activity

> Retrieve LinkedIn post details, reaction identities, and comments from a public post URL.

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                                                                                  | Price               |
| ------------------------------- | ---------------------------------------------------------------------------------------- | ------------------- |
| `POST /linkedin-post`           | Post text, author, timestamps, engagement, media, reshared content, and initial comments | \$0.012 per request |
| `POST /linkedin-post-reactions` | People who reacted and their reaction types                                              | \$0.012 per page    |
| `POST /linkedin-post-comments`  | Comments, authors, timestamps, permalinks, and engagement                                | \$0.012 per page    |

All three endpoints accept a public LinkedIn post URL containing an activity, `ugcPost`, or share identifier. Failed lookups are refunded automatically.

## Get post details

```bash theme={null}
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:

```bash theme={null}
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.token` is not `null`, pass it back with the same post URL:

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

Stop when `pagination.token` is `null`. The response also provides `page`, `pages`, and `total_reactions`.

## Get comments

The first request needs only the post URL:

```bash theme={null}
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.token` is not `null`, pass it back with the same post URL:

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

Stop when `pagination.token` is `null`.

## Build an engagement workflow

A typical workflow is:

1. Call `/linkedin-post` for the post content and aggregate engagement.
2. Paginate `/linkedin-post-reactions` to collect people who reacted.
3. Paginate `/linkedin-post-comments` to collect commenters and discussion context.
4. 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.

## Next step

* [Contact enrichment](/guides/contact-enrichment)
* [Research vs direct endpoints](/concepts/research-vs-direct-endpoints)
* [API Reference — LinkedIn](/api-reference)