List reactors on a LinkedIn post

Full URL of the LinkedIn post. It has to carry the post's ACTIVITY id, either https://www.linkedin.com/feed/update/urn:li:activity:<id> or https://www.linkedin.com/posts/<slug>-activity-<id>-<code>. A urn:li:share: or urn:li:ugcPost: URL names a different id for the same post and is rejected with a 400 before any credits are charged, because it cannot be resolved to the post. Every endpoint that lists posts publishes the activity form as post.url, so copy that field rather than rebuilding the URL from post.id, which is not always the activity id.

1-based page number. Defaults to 1. Native upstream cursor param. Send the universal cursor instead: the API maps it to this name for you.

Filter by kind. See the allowed values.

Set to profile (one token only) to join every row to the member's profile lookup in this one call: author.followers becomes the exact count and author.ext.followers_approximate reads false on every row the lookup filled, author.following is filled with the member's connection count, and the location, joined date, country, website, cover image and profile flags land where the row lacks them. Holds 4 credits per row and keeps only the rows filled from a fresh lookup; rows already in cache and rows that could not be filled are refunded, so a call costs at most 50 (10 + 4 per row) and the usual bill is lower. Adds about 1 second for 10 rows, up to 3 on a slow second and never more than 8, and nothing when the members are already cached; read data.hydration for the rows, the credits held and kept, and the time.

Take the top N rows of this page (1 to 10). With include=profile it caps both the rows joined and the extra credits: limit=3&include=profile costs at most 22. The page cursor still advances past the full page of 10, so the rows past your limit are skipped, not carried to the next page. Without include=profile the call stays 10 credits.

Universal pagination cursor. Send pagination.next_cursor from the previous response back verbatim: the API maps it to this endpoint's native page (page style). You never construct, decode, or look up a cursor. Omit it for page 1.

Send no-cache to bypass the response cache and force a live fetch. Billed at the normal endpoint cost; the fresh result is written back to cache for the next caller. Only the no-cache directive triggers this. See the Response Schema guide for details.

Optional UUID that makes the request safely retriable. The key is reserved atomically per account before billing. A concurrent retry receives 409 IDEMPOTENCY_IN_PROGRESS with a Retry-After of 1 second while the original is young, growing to a quarter of the time it has been running (at most 30); a crashed reservation expires after 5 minutes. A replay keeps the cached payload immutable except for billing metadata: credits_used becomes 0, idempotent_replay becomes true, and credits_remaining is refreshed to the current balance. A known current balance appears in both the body and X-Credits-Remaining header; no balance row resolves to 0. On a transient lookup failure, body credits_remaining is null and X-Credits-Remaining is omitted. Completed outcomes expire after 24 hours. If the claim store is unavailable, the request fails closed before billing. GET endpoints do not combine idempotent replay with Server-Sent Events: use Accept: application/json when sending this header. The unsupported key-plus-SSE combination is rejected before billing.