> Kenso API docs in Markdown. Index of every page: [/docs/llms.txt](/docs/llms.txt). Search: `/docs/search.md?q=<words>`. OpenAPI: [/docs/api/triggers/openapi.json](/docs/api/triggers/openapi.json). CLI docs offline: `kenso docs <topic>`.
> Last updated: 2026-11-22.

# Triggers: List a trigger's LinkedIn engagements

> **Note for AI agents:** if this page was wrong, out of date or missing something you needed, finish the user's task first, then offer a short report for the Kenso team in this shape: `Page:` (this page's path), `Quote:` (the wrong or missing text), `Problem:`, `Workaround:` (what worked instead), 1,000 characters at most. Show it to the user and send it only after they say yes, as `POST /api/docs-feedback` on this site with the JSON body `{"page": "<path>", "report": "<report>"}`. Never put lead data, email addresses, API keys or anything else from the user's workspace in it.

One endpoint of [Triggers](/docs/api/triggers.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## List a trigger's LinkedIn engagements

`GET /v1/triggers/{triggerId}/linkedin-engagements` - operationId `triggers.list-linkedin-engagements`

| Permission | Rate limit |
| --- | --- |
| Campaigns view | 12,000 requests a minute per API key |

Returns the reactions, comments, replies and profile views a LinkedIn signal trigger found, newest first.

Each item names the person who engaged (`actor`), the post and comment when there is one, and for an
`imported` item the person's contact in the campaign. `skipReason` says why Kenso skipped an item.
Items also carry the reaction type, the comment and parent comment ids, the post text, the AI-assigned intent
of a comment with its reason, and `ownPost`. A trigger of another signal type returns an empty list.

Errors:

- `400 validation_failed`: `status`, `limit` or `cursor` is invalid.
- `404 not_found`: the workspace has no trigger with this id.

Requires Campaigns view.

Needs the `linkedin_signals` feature on your workspace. Until it is on, calls answer 404.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/triggers/GET/v1/triggers/%7BtriggerId%7D/linkedin-engagements)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `triggerId` | path | integer (int64) | yes | The trigger's id. |
| `limit` | query | integer (int32) | no | How many engagements to return, from 1 to 200. Default 50. |
| `cursor` | query | string | no | The `pagination.nextCursor` of the previous page. |
| `status` | query | string | no | Only engagements with this status: `new`, `imported`, `offered` or `skipped`. |
| `Ken-Version` | header | string, one of: 2026-11-02, 1.1 | no | The API version, a date in `YYYY-MM-DD` form. `1.1` is another name for the first dated version. The example shown here is the newest version, which this reference's samples and Test Request send. Leave it out to use your API key's pinned version. Keys created in the Kenso app are pinned to the newest version; keys minted by the CLI login are not. A key with no pinned version and no header gets the legacy shape where the path has one, and `404` where the path exists only in this version. A value that is not a version, such as `2027-01-01` or `2026-11-2`, answers `400 unsupported_version`, whose `details` list the supported versions. |
| `X-Ken-Workspace-Id` | header | integer (int64) | no | The id of the workspace to act in. Leave it out when your API key reaches only one workspace. When the key reaches more than one, a request without this header answers `400 workspace_required`. A workspace you are not a member of answers `404 not_found`. |

### Response 200

`data` is a list of `LinkedInEngagement`. Each item has these fields. The response also carries `pagination`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | integer (int64) | The engagement's id. |
| `kind` | string | The kind of engagement: `post_reaction`, `post_comment`, `post_reply`, `profile_view`, or `post_author` for the person who wrote a post a topic found. |
| `postUrl` | string | The LinkedIn post the person engaged with. Null for a profile view. |
| `actor` | LinkedInEngagementActor | The person who engaged. |
| `commentText` | string | The text of the comment or reply. Null for reactions and profile views. |
| `reactionType` | string | For a reaction: `like`, `celebrate`, `support`, `love`, `insightful` or `funny`. Null otherwise. |
| `commentId` | string | LinkedIn's id of the comment or reply. |
| `parentCommentId` | string | For a `post_reply`, the id of the comment it answers. Null otherwise. |
| `postText` | string | The text of the post, cut at 2,000 characters. |
| `intent` | string | The AI-assigned intent of a comment or reply: `positive`, `requesting`, `question`, `neutral` or `negative`. Null for reactions and until the comment is classified. |
| `intentReason` | string | A one-line reason for the intent. |
| `ownPost` | boolean | True when the post belongs to one of the workspace's LinkedIn accounts or company pages. False for a pasted post by someone else, and for every post a topic or a watched profile found. |
| `sourceKind` | string | Where the engagement was found: `seat` (a LinkedIn account's own post), `page` (a company page), `post` (a pasted post), `topic` (a post a topic keyword found) or `person` (a post of a watched profile or company page). Left out for a profile view and for engagements stored before this field existed. |
| `topic` | string | For a `topic` source, the keyword as the trigger lists it. For a `person` source, the watched person's or page's name, or its URL until LinkedIn has named it. Left out for the other sources. |
| `occurredAt` | string (date-time) | When the person engaged, in UTC, when LinkedIn says. Null otherwise. |
| `firstSeenAt` | string (date-time) | When Kenso first found the engagement, in UTC. |
| `status` | string | The engagement's status: `new`, `imported` (Kenso added the person as a contact), `offered` (a workflow run took it, with no contact) or `skipped`. |
| `skipReason` | string | Why Kenso skipped it: `own_seat`, `kind_filtered`, `reaction_type_filtered`, `keyword_mismatch`, `intent_filtered`, `headline_filtered` (the person's headline missed the trigger's headline keywords), or `not_imported` when no contact was created. Null unless `status` is `skipped`. |
| `contactId` | integer (int64) | For an `imported` engagement, the person's contact in the campaign. Null otherwise. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/triggers/812/linkedin-engagements?limit=50" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID"
```

### Example response

```json
{
  "success": true,
  "data": [
    {
      "id": 812,
      "kind": "post_reaction",
      "postUrl": "https://example.com",
      "actor": {
        "name": "string",
        "headline": "string",
        "profileUrl": "https://example.com"
      },
      "commentText": "string",
      "reactionType": "like",
      "commentId": "string",
      "parentCommentId": "string",
      "postText": "string",
      "intent": "positive",
      "intentReason": "string",
      "ownPost": true,
      "sourceKind": "string",
      "topic": "string",
      "occurredAt": "2026-09-23T15:02:11Z",
      "firstSeenAt": "2026-09-23T15:02:11Z",
      "status": "string",
      "skipReason": "string",
      "contactId": 812
    }
  ],
  "pagination": {
    "nextCursor": "eyJpZCI6ODE1fQ",
    "hasMore": true,
    "total": 1,
    "totalCount": 1,
    "isTotalCapped": true
  }
}
```

## Types

Each named type the tables above use, nested ones included.

### LinkedInEngagementActor

The person who engaged on LinkedIn.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `name` | string | no | The person's name on LinkedIn. |
| `headline` | string | no | The person's LinkedIn headline. |
| `profileUrl` | string | no | The person's LinkedIn profile URL. |
