## linkedin/post-reactions

`GET /v1/linkedin/post-reactions`

Who reacted to a post and how, ten a page with the total: reaction type, name, headline and profile.

*LinkedIn post reactions*

| Parameter | Required | Description |
| --- | --- | --- |
| `url` | no | Post URL (or pass reactions_urn from a profile-posts card) — e.g. `https://www.linkedin.com/feed/update/urn:li:activity:7496695637644828672` |
| `reactions_urn` | no | urns.reactions from a profile-posts card |
| `cursor` | no | Page number from the previous page — e.g. `2` |
| `pages` | no | Optional bounded collection of 1–3 source pages at the normal price, within one shared spending limit and total deadline. Default 1. Inspect pages_fetched, partial and window_stop_reason: fewer pages may fit. Continue using the returned cursor with the same pages and filters. Source order is preserved; this is not an exhaustive result set. — e.g. `1` |
| `dry_run` | no | Read a zero-credit estimate without fetching sources, running AI, or reserving credits. Cache status is a snapshot, not a guarantee at execution. — e.g. `1` |
| `judgments` | no | Add bounded AI labels to eligible returned records (default on). off preserves the original data shape. Unclassified records remain present; labels depend on evidence, time, capacity and the existing request budget. No label surcharge. — e.g. `on` |
| `label` | no | Set none to disable labels; default enables the endpoint’s label set. Equivalent to judgments=off. — e.g. `none` |
| `label_evidence` | no | Include exact supporting sentences and zero-based sentence indexes when a label has validated evidence. No extra charge or change to decisions. — e.g. `1` |
| `exclude` | no | Optionally remove confidently labelled engagement bait. Uncertain and unclassified records stay; removed IDs and an owner-bound recall reference are returned. — e.g. `engagement_bait` |
| `fit` | no | Use goal to replace confidently irrelevant records with recall stubs. Keeps first, last, relevant and uncertain records; preserves order. Full evidence is stored for 24 hours when available. — e.g. `goal` |
| `goal` | no | Required with fit=goal: describe the task in at most 600 characters. Supplied text is task context, never permission to act on posts. — e.g. `Find concrete product complaints` |
| `tokens` | no | Optional soft response target for fit=goal, 256–32000. Safety and evidence retention take priority, so the returned result may exceed it. — e.g. `4000` |

**Cost:** 8 credits at list price per successful uncached response; variable-cost operations may quote or settle a different charge. Confirmed uncharged or refunded failures report zero. Pending reconciliation can report credits_used:null; retain request_id and the original idempotency key.

```bash
curl "https://www.monocrawl.com/v1/linkedin/post-reactions?url=https%3A%2F%2Fwww.linkedin.com%2Ffeed%2Fupdate%2Furn%3Ali%3Aactivity%3A7496695637644828672" \
  -H "x-api-key: mn_your_key_here"
```

### Response data

Illustrative abbreviated data; documented core fields are optional and may be null. Additional source fields are allowed.

```json
{
  "count": 0,
  "cursor": null,
  "dropped": 0,
  "has_more": false,
  "items": [
    {
      "actor": {
        "avatar": "https://example.com/example",
        "headline": "example",
        "id": "example",
        "name": "example",
        "url": "https://example.com/example"
      },
      "type": "example"
    }
  ],
  "page": 0,
  "post_url": "https://example.com/example",
  "total": 0
}
```

[Field reference](https://www.monocrawl.com/docs/endpoints/linkedin/post-reactions#response) · [JSON Schema for response.data](https://www.monocrawl.com/schemas/linkedin/post-reactions.json)