--- title: "List a user's reactions" method: GET path: "/v1/{account_id}/users/{user_id}/reactions" tags: ["Posts"] --- # List a user's reactions `GET /v1/{account_id}/users/{user_id}/reactions` ## Request - Base URL: `https://api.curviate.com` - URL: `https://api.curviate.com/v1/{account_id}/users/{user_id}/reactions` - Auth: HTTP bearer Returns reactions made by this account (`user_id="me"`) or another LinkedIn user. Each item embeds the reacted-on post and whether the queried account made it. ## Path parameters - `account_id` string, required - `user_id` string, required ## Query parameters - `limit` integer - `cursor` string ## Response `200` Reactions made by this account (user_id="me") or another LinkedIn user. Each item embeds the reacted-on post and whether the queried account is the sender. No reaction-time field is available on this item, an upstream limitation rather than something this endpoint drops; parent_post.created_at is the post's own creation time, not the reaction's, and is not a usable proxy for it. List order is not documented or guaranteed, so do not rely on it to filter by date; cap results by count (limit) instead. - object - `object` 'reaction_list': Response type discriminator. - `items` object[]: Page of reactions. - `object` 'reaction': Response type discriminator. - `value` 'like' | 'celebrate' | 'support' | 'love' | 'insightful' | 'funny': Reaction type, unified lowercase enum. - `is_sender` boolean: true when the queried account itself made this reaction. - `sender` object: The user who made the reaction. - `parent_post` object: The post this reaction was made on (full Post or a lighter preview). Its `urn` is the stable identifier for that post, so compare it against a post's own `urn` to tell whether you already reacted to it. - `object` 'post': Response type discriminator. - `id` string: The post's identifier as returned on this surface. Accepted as the post_id path param on every operation that takes one, as is `urn`. - `urn` string, nullable: Stable identifier for the parent post, in `urn:li:activity:ID` or `urn:li:ugcPost:ID` form. Also accepted as the post_id path param on every operation that takes one. null when the post carries no resolvable identity, and two nulls are not a match: treat null as unknown, never as equal. - `created_at` string, nullable: ISO-8601 UTC datetime the parent post was created, or null if unavailable. This is the post's own creation time, not the time of the reaction. - `share_url` string, nullable: Shareable URL for the parent post. Present on the full form only. - `text` string, nullable: Full text of the parent post (content pass-through, never stored). Present on the full form only. - `is_repost` boolean: true if the parent post is itself a repost. Present on the full form only. - `author` object: Author of the parent post. Present on the full form only. - `id` string: LinkedIn profile identifier. - `name` string: Author's display name. Absent on the shape that carries `display_name` instead. - `display_name` string: Author's display name. Absent on the shape that carries `name` instead. - `object` string: Author entity discriminator, on the shape that carries one. - `type` string: Author entity type (for example individual or organization), on the shape that carries one. - `profile_picture_url` string, nullable: Author's profile picture URL, or null if not set. - `reactions_counter` object[]: Per-reaction-type count buckets on the parent post. Present on the full form only. - `reaction` string: Reaction type, as the platform names it. - `count` number: Count of this reaction type on the parent post. - `comments_counter` number, nullable: Total comment count on the parent post. Present on the full form only. - `reposts_counter` number, nullable: Total repost count on the parent post. Present on the full form only. - `attachments` object[]: Media attachments on the parent post. Present on the full form only. - `cursor` string, nullable: Next-page cursor; null on the last page. - `safety_warning` SafetyWarning: Present on a successful response when this account crossed an account-safety ceiling while the affected budget row is on the default warn posture. The action still happened. Field-identical to the BUDGET_EXHAUSTED error body except that blocked is false and hint.message describes the outcome, so one branch handles both postures and switching the account to enforce is a configuration change rather than a client rewrite. - `row` string, nullable, required: The budget row that breached, for example profile_views or pending_invites. Null when the breach is not about a row: an activity_window warning on an action that spends no budget of its own (editing a message, dismissing a notification, a Recruiter or Sales Navigator admin action) is still governed by the hours the account works in. Read hint.parameter for what to change; whenever this is null it names posture, because the activity window edges are set per action type and this action has none, so the levers that reach it are the account timezone and posture. - `reset_at` string, nullable, required: The instant the refusal lifts: the window roll on a ceiling refusal, the next window open on an activity-window one. Null in the two cases no clock frees, the pending_invites gauge and InMail credits (row inmail). - `hint` object, required - `parameter` string, required: The settable parameter on PATCH /v1/{account_id}/safety-policy. - `message` string, required: What the condition is and what changing that parameter would do. This is the one field whose text differs from the BUDGET_EXHAUSTED refusal: here it says the action went through, and on a ceiling breach how far past the ceiling this row now stands, rather than telling you to set posture to warn when it already is. Branch on parameter, reason and blocked, never on this text. - `reason` 'ceiling' | 'activity_window', required: Which rule was crossed. ceiling means the row's configured limit is spent; activity_window means the account is outside the hours it works in, which is a different fact with a different remedy. hint.parameter names the right setting for each. - `blocked` boolean, required: Always false here. True on the BUDGET_EXHAUSTED refusal carrying the same payload. ## Other responses - `400`: limit out of range (1-50) or malformed cursor. - `401`: Missing or invalid API key. - `404`: The account_id does not belong to this tenant (ACCOUNT_NOT_FOUND), or the user_id could not be resolved (RESOURCE_NOT_FOUND). An id whose connection was replaced or removed also stops resolving here, and it is already absent from the list, so re-read `GET /v1/accounts` for the current id. - `429`: Rate limited, slow down and retry after the hinted delay. - `500`: Internal error. - `502`: A temporary error occurred. Please try again. - `503`: Service unavailable. - `504`: Gateway timeout. --- [API](https://skmtc.dev/curviate/apis/curviate-api.md) · [All operations](https://skmtc.dev/curviate/apis/curviate-api/llms.txt) · [OpenAPI document](https://skmtc.dev/curviate/apis/curviate-api/revisions/eab848801d95?raw)