List reactions on a LinkedIn post · LinkedIn API
Returns the people who reacted to a LinkedIn post and the reaction type of each. Paginate with `cursor`.
Using ChatGPT, Claude Code or another client? See the setup steps
curl https://api.unifapi.com/linkedin/posts/{id}/reactions \
-H "Authorization: Bearer $UNIFAPI_KEY"Parameters
- idpathrequired
- LinkedIn post activity id (the number in urn:li:activity:{id}).
- cursorquery
- Opaque pagination cursor from a previous response's `pagination.next_cursor`. Omit for the first page.
- The parameter for this LinkedIn operation. Use the URL-visible slug or id described in the docs.
This operation is part of the LinkedIn API in the social platforms category. It uses the same Bearer token, request tracing, error model, and billing envelope as every UnifAPI endpoint, so agents can switch between platforms without custom per-vendor glue code.
Use it when a workflow needs LinkedIn public data alongside other social networks, but should still keep one API key, one account balance, and one predictable JSON contract.
Common agent workflows
- Fetch canonical public LinkedIn content for summarization, ranking, monitoring, or enrichment.
- Attach engagement, author, media, and source metadata to an agent workflow.
- Give an AI agent a stable LinkedIn data source without building a per-platform integration.
- Normalize LinkedIn responses into the same UnifAPI envelope used across the catalog.
Unified envelope, platform-native fields
- List-style responses return `data` as an array of top-level records plus optional `pagination` for continuation tokens or cursors.
- The operation has a 9 credits ($0.009) minimum charge, so `billing.records_charged` can be higher than the visible records returned.
- If the workspace balance cannot cover every result, the response can be truncated and `billing.truncated_due_to_balance` tells the caller why.
Response status codes
Billing
This operation charges 1 credit per billable record, with a 9 credits ($0.009) operation minimum. Public responses include billing metadata with credits charged, records charged, and remaining workspace balance. Incorrect Credit deductions caused by platform failures can be restored as billing corrections.
Errors and retries
Authentication, validation, rate-limit, not-found, and provider errors use the unified UnifAPI error format. Agents should log `request_id`, retry only retryable failures, and treat invalid API keys, disabled keys, and expired keys as the same public `unauthorized` error type.
Fields on each record in data
A successful List reactions on a LinkedIn post call returns data as an array; each record carries these fields.
- actorobject | null
- Person or organization that reacted when observed.
- reaction_typestring | null
- Reaction type when observed.
Agents & Skills built on LinkedIn
You rarely call List reactions on a LinkedIn post by hand. These prebuilt agents and skills already read LinkedIn data inside Claude or Codex — start from one of them, or call this endpoint yourself.
Try it free in the browser
More LinkedIn operations
Combine endpoints from the same platform, then join the results with other UnifAPI categories without changing authentication or response parsing.
List top-level comments on a LinkedIn post
Return top-level comments on a LinkedIn post by activity ID as a cursor-paginated list. This operation is capacity-limited; the gateway makes up to 3 total attempts for transient failures.
Get the transcript of a LinkedIn video post
Returns the spoken-word transcript of a LinkedIn video post. Returns `not_found` when the post does not exist.
Get a LinkedIn post by ID
Return a single LinkedIn post by its numeric ID, including author, text, media, and engagement counts. Useful for hydrating a known post or checking its current reach.
List posts published by a LinkedIn company page
Return posts published from a LinkedIn company page by URL slug as a cursor-paginated list. This operation is capacity-limited; the gateway makes up to 3 total attempts for transient failures.
Get a LinkedIn job posting by ID
Return a LinkedIn job posting by ID, including title, company, location, description, and optional skills or hiring-team data. This operation is capacity-limited; the gateway makes up to 3 total attempts for transient failures.
List posts authored by a LinkedIn user
Return posts authored by a LinkedIn user from the profile URL slug as a cursor-paginated list. This operation is capacity-limited; the gateway makes up to 3 total attempts for transient failures.