# st.retrievePersonReactions

> The API Reference is also the SDK and CLI reference. Consecutive code fences marked `tab=HTTP`, `tab=Node`, `tab=Python` and `tab=CLI` are the same call on each surface (a fence marked `tab=HTTP,CLI` is the same text for both), and a block between `:::surface <names>` and `:::` applies only to the surfaces it names. Identifiers in the text are written as in Node and in HTTP JSON (camelCase); the Python SDK spells methods, parameters and result attributes in snake_case (`sendMessage` → `send_message`, `reconnectionLink` → `reconnection_link`), while names inside HTTP JSON stay camelCase.

This action allows you to retrieve reactions made by a person.

:::surface node
In the Node SDK this action runs inside `fetchPerson` with `retrieveReactions` enabled; its result comes back in `data.reactions`, and its errors in `errors`.

> Up to `@linkedapi/node` 2.3.21 the `TReaction` type declares the reaction kind as `reactionType`, while the API returns it as `type`, described below. At runtime the value is in `type`; `reactionType` is always undefined. Since 2.3.22 the type declares `type`.
:::

:::surface python
In the Python SDK this action runs inside `fetch_person` with `retrieve_reactions` enabled; its result comes back in `result.data.reactions`, and its errors in `result.errors`.

> Up to `linkedapi` 1.4.9 the `Reaction` model drops the reaction kind: the API returns it as `type`, described below, but `reaction_type` is always `None` and the model has no `type`. Since 1.4.10 the model has `type`, and `reaction_type` returns the same value.
:::

:::surface cli
In the CLI this action runs inside `linkedin person fetch` with `--reactions`; that command's other options are on [`st.openPersonPage`](/docs/action-st-open-person-page).
:::

## Constraints

> ⏺️ **Root Start:** not allowed.

> ⬆️ **Parent Actions:** [st.openPersonPage](/docs/action-st-open-person-page).

> ⬇️ **Child Actions:** N/A.

## Parameters

```json tab=HTTP
{
  "actionType": "st.retrievePersonReactions",
  "label": "person1Reactions",
  "limit": 10,
  "since": "2023-01-01T00:00:00Z"
}
```

```typescript tab=Node
const workflow = await linkedapi.fetchPerson.execute({
  personUrl: "https://www.linkedin.com/in/person1",
  retrieveReactions: true,
});

const { data, errors } = await linkedapi.fetchPerson.result(workflow.workflowId);
console.log(data?.reactions);
console.log(errors);
```

```python tab=Python
from linkedapi import FetchPersonParams

workflow = linkedapi.fetch_person.execute(
    FetchPersonParams(
        person_url="https://www.linkedin.com/in/person1",
        retrieve_reactions=True,
    )
)

result = linkedapi.fetch_person.result(workflow.workflow_id)
if result.data:
    print(result.data.reactions)
print(result.errors)
```

```bash tab=CLI
linkedin person fetch https://www.linkedin.com/in/person1 --reactions --json
```

- `label` (optional) – custom label for tracking this action in workflow completion.
- `limit` (optional) – number of reactions to retrieve. Defaults to **20**, with a maximum value of **100**.
- `since` (optional) – timestamp to filter reactions made after the specified time.

**Note**: both `limit` and `since` conditions are applied simultaneously. For example:

- If `limit` is 10, but there are more than 10 reactions since the specified timestamp, only 10 reactions will be returned.
- If `limit` is 15, but only 5 reactions exist after the specified timestamp, only those 5 reactions will be returned.

## Result options

This action always completes successfully. Even if the person has no reactions, it returns an empty array.

```json
{
  "actionType": "st.retrievePersonReactions",
  "label": "person1Reactions",
  "success": true,
  "data": [
    {
      "postUrl": "https://www.linkedin.com/posts/example1",
      "time": "2023-01-02T12:30:00Z",
      "type": "like"
    },
    {
      "postUrl": "https://www.linkedin.com/posts/example2",
      "time": "2023-01-03T12:30:00Z",
      "type": "celebrate"
    }
  ]
}
```

- `label` – included only if specified in the action parameters.
- `data` – array of person reactions.
  - `postUrl` – URL of the post the reaction belongs to.
  - `time` – timestamp when the reaction was made.
  - `type` – enum describing the reaction type. May take one of the following values:
    - `like` – standard "like".
    - `celebrate` – celebrates an achievement.
    - `support` – shows support.
    - `love` – expresses love or admiration.
    - `insightful` – appreciates insightful content.
    - `funny` – reacts to something humorous.
