# LinkedIn Post Engagers (`linkedin.post_engagers`)

Up to 100 people who reacted to or commented on a public LinkedIn post, with name, profile link and headline, in one call.

Docs: https://primaryapi.com/docs/api-reference/linkedin/post_engagers

> **Planned.** This API is on the roadmap and cannot be called yet: `POST /v1/run/linkedin.post_engagers` answers `404 not_found`. Ask for it with `POST https://api.primaryapi.com/v1/api-requests` or the MCP tool `send_feedback`.

- Endpoint: `POST https://api.primaryapi.com/v1/run/linkedin.post_engagers`
- Category: Social · Platform: `linkedin` · Kind: composite · Status: planned
- Price: Not priced yet: this API is planned and cannot be called.
- Billing unit: per successful call
- Reliability: routed to a healthy upstream and retried automatically when an attempt fails; live 30-day status: `GET https://api.primaryapi.com/v1/status/apis?sku=linkedin.post_engagers`
- Execution: synchronous (answers 202 only if it outlives the wait window)

## Input

| Field | Type | Required | Default | Constraints | Description |
|---|---|---|---|---|---|
| `post_url` | string | yes |  | max 2048 chars | Public LinkedIn post URL, its numeric post id or its URN (urn:li:activity:…), e.g. "https://www.linkedin.com/posts/satyanadella_today-at-microsoft-build-activity-7329207003942125568-xyz". |
| `engagement` | enum | no | "reactions" | one of: reactions, comments | Which people to return: those who reacted (default) or those who commented. |

Unknown fields are rejected with `400 invalid_input`. The routing controls `preferLatencyUnderMs` and `maxCredits` may be sent in the same JSON body.

## Output

When `output.found` is `true`, `output.data` has this shape:

| Field | Type | Description |
|---|---|---|
| `items` | object[] | Reactions (reactionType + actor) or comments (commentary + actor); `actor` is the person |
| `totalResults` | integer \| null | Total results LinkedIn reports for this list, when known |
| `nextCursor` | string \| null | More people: pass it as cursor, with the same post URL as url, to linkedin.post_reactions (or linkedin.post_comments) |

When the thing you asked about does not exist (or a search matches nothing) the call still succeeds: `output.found` is `false`, `output.data` is `null` and `output.reason` says why (`not_found`, `private`, `no_results`, …). Misses are free unless the notes below say misses are billed.

## Example request

```bash
curl -sS -X POST "https://api.primaryapi.com/v1/run/linkedin.post_engagers" \
  -H "Authorization: Bearer $PRIMARYAPI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"post_url":"https://www.linkedin.com/posts/satyanadella_today-at-microsoft-build-activity-7329207003942125568-xyz"}'
```

## Errors to handle

`invalid_input`, `unauthorized`, `insufficient_balance`, `key_limit_reached`, `trial_cap_reached`, `forbidden`, `not_found`, `idempotency_conflict`, `rate_limited`, `all_sources_failed`, `service_unavailable`, `timeout`. See https://primaryapi.com/docs/errors.

## Notes

Returns the first 100 people from linkedin.post_reactions (engagement=reactions) or linkedin.post_comments (engagement=comments), unchanged: each entry’s actor holds the name, profile URL and headline. A post without reactions or comments answers found=false and costs nothing. For deeper lists, call those two APIs directly with nextCursor.

## Legal

Public LinkedIn data only. LinkedIn’s User Agreement restricts automated collection and LinkedIn enforces it; use the data for lawful purposes, keep copies only as long as you need them, and treat post and article text as the author’s content (analysis, not republication). Results contain personal data about identifiable people (GDPR, UK GDPR, CCPA): have a lawful basis, honour deletion requests, and never use it for spam or unsolicited bulk outreach.

