> 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

> **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.

Rules that act when a signal happens: create, preview, edit, archive and read their stats.

Integrations. 9 endpoints under `https://api.ken.so`. Every request sends `Authorization: Bearer <your API key>` and `Ken-Version: 2026-11-02`: see [Authentication](/docs/authentication.md), [Workspaces](/docs/workspaces.md) and [Errors](/docs/errors.md). OpenAPI for this resource only: [/docs/api/triggers/openapi.json](/docs/api/triggers/openapi.json).

- `GET /v1/triggers` - List triggers (`triggers.list`): [/docs/api/triggers/list.md](/docs/api/triggers/list.md)
- `POST /v1/triggers` - Create a trigger (`triggers.create`): [/docs/api/triggers/create.md](/docs/api/triggers/create.md)
- `GET /v1/triggers/{triggerId}` - Get a trigger (`triggers.get`): [/docs/api/triggers/get.md](/docs/api/triggers/get.md)
- `PATCH /v1/triggers/{triggerId}` - Update a trigger (`triggers.update`): [/docs/api/triggers/update.md](/docs/api/triggers/update.md)
- `DELETE /v1/triggers/{triggerId}` - Archive a trigger (`triggers.delete`): [/docs/api/triggers/delete.md](/docs/api/triggers/delete.md)
- `POST /v1/triggers/preview` - Preview a trigger's matching companies (`triggers.preview`): [/docs/api/triggers/preview.md](/docs/api/triggers/preview.md)
- `POST /v1/triggers/{triggerId}/test-fire` - Test a trigger with a sample signal (`triggers.test-fire`): [/docs/api/triggers/test-fire.md](/docs/api/triggers/test-fire.md)
- `GET /v1/triggers/{triggerId}/stats` - Get a trigger's firing stats (`triggers.get-stats`): [/docs/api/triggers/get-stats.md](/docs/api/triggers/get-stats.md)
- `GET /v1/triggers/{triggerId}/linkedin-engagements` - List a trigger's LinkedIn engagements (`triggers.list-linkedin-engagements`): [/docs/api/triggers/list-linkedin-engagements.md](/docs/api/triggers/list-linkedin-engagements.md)

## List triggers

`GET /v1/triggers` - operationId `triggers.list`

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

Returns the workspace's triggers. Filter them by `campaignId` and by `status`.

Errors:

- `400 validation_failed`: `status`, `limit` or `cursor` is invalid.

Requires Campaigns view.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/triggers/GET/v1/triggers)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `limit` | query | integer (int32) | no | How many triggers to return, from 1 to 200. Default 50. |
| `cursor` | query | string | no | The `pagination.nextCursor` of the previous page. |
| `campaignId` | query | integer (int64) | no | Only the triggers that add contacts to this campaign. |
| `status` | query | string | no | Only triggers with this status: `active`, `paused` or `archived`. |
| `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 `Trigger`. Each item has these fields. The response also carries `pagination`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | integer (int64) | The trigger's id. |
| `campaignId` | integer (int64) | The campaign the trigger adds contacts to. |
| `stagingCampaignId` | integer (int64) | For a `lead_uploaded` or `webhook_lead_received` trigger, the staging campaign where new leads wait for email enrichment and verification before the trigger adds them. Null for the other signal types. |
| `signalType` | string | The signal type the trigger watches, such as `link_clicked`, `reply_received` or `fundraising`. |
| `tier` | string | Deprecated: no effect. Every trigger is processed at the same speed whatever its tier, and `maxAgeMinutes` bounds how long a firing may wait. Still returned and accepted: `minutes`, `hours` or `same_day`. |
| `parameters` | string | The signal type's parameters as a JSON string, such as `{"count":3,"windowMinutes":10}`. |
| `audienceFilter` | string | The campaigns whose contacts the trigger watches, as a JSON string such as `{"sourceCampaignIds":[1,2]}`. Null watches every campaign in the workspace. |
| `cooldownMinutes` | integer (int32) | How long, in minutes, the trigger waits before it fires again for the same contact. |
| `maxAgeMinutes` | integer (int32) | How long, in minutes, a firing may wait to be processed. An older firing is suppressed as `expired`. |
| `priority` | integer (int32) | When several triggers fire for the same person at once, only the highest priority one acts. The others are suppressed as `lost_arbitration`. |
| `stopSourceSequence` | boolean | True when Kenso stops the contact's sequence in its current campaign as the trigger adds it to this one. |
| `status` | string | The trigger's status: `active`, `paused` or `archived`. |
| `createdAt` | string (date-time) | When the trigger was created, in UTC. |
| `updatedAt` | string (date-time) | When the trigger last changed, in UTC. |
| `listeningIdleReason` | string | Why a `linkedin_post_engagement` trigger that lists topics or watched profiles finds nothing now. `no_opted_in_seat`: no LinkedIn account in the workspace has research reads turned on, and only such an account reads topics and watched profiles. Returned when you get or list triggers; left out when the trigger can be read, and for every other trigger. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/triggers?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,
      "campaignId": 812,
      "stagingCampaignId": 812,
      "signalType": "link_clicked",
      "tier": "minutes",
      "parameters": "{\"count\":3,\"windowMinutes\":10}",
      "audienceFilter": "{\"sourceCampaignIds\":[1,2]}",
      "cooldownMinutes": 1,
      "maxAgeMinutes": 1,
      "priority": 1,
      "stopSourceSequence": true,
      "status": "active",
      "createdAt": "2026-09-23T15:02:11Z",
      "updatedAt": "2026-09-23T15:02:11Z",
      "listeningIdleReason": "string"
    }
  ],
  "pagination": {
    "nextCursor": "eyJpZCI6ODE1fQ",
    "hasMore": true,
    "total": 1,
    "totalCount": 1,
    "isTotalCapped": true
  }
}
```

## Create a trigger

`POST /v1/triggers` - operationId `triggers.create`

| Permission | Rate limit |
| --- | --- |
| Campaigns edit | 4,800 requests a minute per API key |

Creates a trigger that watches one signal type for a campaign. The trigger starts as `active`.

`campaignId` and `signalType` are required. The campaign must be in trigger mode. To use a batch
campaign, send `switchCampaignToTrigger: true`, and Kenso switches the campaign to trigger mode in the same
step, so a failed create leaves the campaign as it was. The LinkedIn signal types,
`linkedin_post_engagement` and `linkedin_profile_view`, take a campaign that is not in trigger mode
and need the `linkedin_signals` feature. A `linkedin_post_engagement` trigger on pasted posts takes
posts no older than 30 days, and a workspace has at most 10 such posts active.

`parameters` is a JSON string with the keys `GET /v1/trigger-schemas` lists for the signal type.
Omitted fields take these defaults: `cooldownMinutes` 10080 (7 days), `maxAgeMinutes` 1440 (1 day),
`priority` 50 and `stopSourceSequence` true. `cooldownMinutes` is at least 1, and
`maxAgeMinutes` is from 1 to 10080. `tier` is deprecated and has no effect: every trigger is processed
at the same speed.

A campaign has at most one active `lead_uploaded` trigger and one active `webhook_lead_received`
trigger. Both types need email enrichment and email verification set up on the campaign, and Kenso creates a
staging campaign for them, returned as `stagingCampaignId`.

Errors:

- `400 validation_failed`: a field is missing or invalid, the parameters or audience filter do not fit
the signal type, the campaign has the wrong mode, or a `lead_uploaded` or `webhook_lead_received`
trigger already exists or lacks email enrichment and verification.
- `402 plan_required`: the workspace's plan does not include the feature the signal type reads:
`funding_signals` for `fundraising`, `job_post_search` for `open_roles`. `error.refusal`
carries the code `PLAN_FEATURE_NOT_AVAILABLE` and the feature.
- `404 not_found`: the campaign is not in the workspace.
- `409 conflict`: an active trigger of this type already exists for this campaign.

Requires Campaigns edit.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/triggers/POST/v1/triggers)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `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`. |

### Request body

`application/json`, optional.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `campaignId` | integer (int64) | yes | Required. The campaign the trigger adds contacts to. |
| `signalType` | string | yes | Required. The signal type to watch, such as `link_clicked`, `reply_received` or `job_change`. |
| `tier` | string | no | Deprecated: no effect, so leave it out. Every trigger is processed at the same speed whatever its tier. Still accepted: `minutes`, `hours` or `same_day`. Default `minutes`. |
| `parameters` | string | no | The signal type's parameters as a JSON string, with the keys `GET /v1/trigger-schemas` lists. Omitted: `{}`, which a signal type with required parameters refuses. |
| `audienceFilter` | string | no | The campaigns whose contacts to watch, as a JSON string `{"sourceCampaignIds":[1,2]}`. The list cannot be empty, and every campaign must be in the workspace. Omitted: every campaign in the workspace. A `job_change` trigger requires it. |
| `cooldownMinutes` | integer (int32) | no | Minutes before the trigger can fire again for the same contact, at least 1. Default 10080 (7 days). |
| `maxAgeMinutes` | integer (int32) | no | Minutes a firing may wait to be processed before Kenso drops it, from 1 to 10080. Default 1440 (1 day). |
| `priority` | integer (int32) | no | When several triggers fire for the same person at once, the highest priority wins. Default 50. |
| `stopSourceSequence` | boolean | no | True stops the contact's sequence in its current campaign when the trigger adds it. Default true. |
| `switchCampaignToTrigger` | boolean | no | True switches a batch campaign to trigger mode as part of the create, so a failed create leaves the campaign as it was. Default false. Ignored for the LinkedIn signal types. |

### Response 201

`data` is a `Trigger`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | integer (int64) | The trigger's id. |
| `campaignId` | integer (int64) | The campaign the trigger adds contacts to. |
| `stagingCampaignId` | integer (int64) | For a `lead_uploaded` or `webhook_lead_received` trigger, the staging campaign where new leads wait for email enrichment and verification before the trigger adds them. Null for the other signal types. |
| `signalType` | string | The signal type the trigger watches, such as `link_clicked`, `reply_received` or `fundraising`. |
| `tier` | string | Deprecated: no effect. Every trigger is processed at the same speed whatever its tier, and `maxAgeMinutes` bounds how long a firing may wait. Still returned and accepted: `minutes`, `hours` or `same_day`. |
| `parameters` | string | The signal type's parameters as a JSON string, such as `{"count":3,"windowMinutes":10}`. |
| `audienceFilter` | string | The campaigns whose contacts the trigger watches, as a JSON string such as `{"sourceCampaignIds":[1,2]}`. Null watches every campaign in the workspace. |
| `cooldownMinutes` | integer (int32) | How long, in minutes, the trigger waits before it fires again for the same contact. |
| `maxAgeMinutes` | integer (int32) | How long, in minutes, a firing may wait to be processed. An older firing is suppressed as `expired`. |
| `priority` | integer (int32) | When several triggers fire for the same person at once, only the highest priority one acts. The others are suppressed as `lost_arbitration`. |
| `stopSourceSequence` | boolean | True when Kenso stops the contact's sequence in its current campaign as the trigger adds it to this one. |
| `status` | string | The trigger's status: `active`, `paused` or `archived`. |
| `createdAt` | string (date-time) | When the trigger was created, in UTC. |
| `updatedAt` | string (date-time) | When the trigger last changed, in UTC. |
| `listeningIdleReason` | string | Why a `linkedin_post_engagement` trigger that lists topics or watched profiles finds nothing now. `no_opted_in_seat`: no LinkedIn account in the workspace has research reads turned on, and only such an account reads topics and watched profiles. Returned when you get or list triggers; left out when the trigger can be read, and for every other trigger. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/triggers" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID" \
  -H "Content-Type: application/json" \
  -d '{
  "campaignId": 812,
  "signalType": "link_clicked",
  "tier": "minutes",
  "parameters": "string",
  "audienceFilter": "string",
  "cooldownMinutes": 1,
  "maxAgeMinutes": 1,
  "priority": 1,
  "stopSourceSequence": true,
  "switchCampaignToTrigger": true
}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "id": 812,
    "campaignId": 812,
    "stagingCampaignId": 812,
    "signalType": "link_clicked",
    "tier": "minutes",
    "parameters": "{\"count\":3,\"windowMinutes\":10}",
    "audienceFilter": "{\"sourceCampaignIds\":[1,2]}",
    "cooldownMinutes": 1,
    "maxAgeMinutes": 1,
    "priority": 1,
    "stopSourceSequence": true,
    "status": "active",
    "createdAt": "2026-09-23T15:02:11Z",
    "updatedAt": "2026-09-23T15:02:11Z",
    "listeningIdleReason": "string"
  }
}
```

## Get a trigger

`GET /v1/triggers/{triggerId}` - operationId `triggers.get`

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

Returns one trigger with its signal type, parameters and status.

Errors:

- `404 not_found`: the workspace has no trigger with this id.

Requires Campaigns view.

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

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `triggerId` | path | integer (int64) | yes | The trigger's id. |
| `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 `Trigger`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | integer (int64) | The trigger's id. |
| `campaignId` | integer (int64) | The campaign the trigger adds contacts to. |
| `stagingCampaignId` | integer (int64) | For a `lead_uploaded` or `webhook_lead_received` trigger, the staging campaign where new leads wait for email enrichment and verification before the trigger adds them. Null for the other signal types. |
| `signalType` | string | The signal type the trigger watches, such as `link_clicked`, `reply_received` or `fundraising`. |
| `tier` | string | Deprecated: no effect. Every trigger is processed at the same speed whatever its tier, and `maxAgeMinutes` bounds how long a firing may wait. Still returned and accepted: `minutes`, `hours` or `same_day`. |
| `parameters` | string | The signal type's parameters as a JSON string, such as `{"count":3,"windowMinutes":10}`. |
| `audienceFilter` | string | The campaigns whose contacts the trigger watches, as a JSON string such as `{"sourceCampaignIds":[1,2]}`. Null watches every campaign in the workspace. |
| `cooldownMinutes` | integer (int32) | How long, in minutes, the trigger waits before it fires again for the same contact. |
| `maxAgeMinutes` | integer (int32) | How long, in minutes, a firing may wait to be processed. An older firing is suppressed as `expired`. |
| `priority` | integer (int32) | When several triggers fire for the same person at once, only the highest priority one acts. The others are suppressed as `lost_arbitration`. |
| `stopSourceSequence` | boolean | True when Kenso stops the contact's sequence in its current campaign as the trigger adds it to this one. |
| `status` | string | The trigger's status: `active`, `paused` or `archived`. |
| `createdAt` | string (date-time) | When the trigger was created, in UTC. |
| `updatedAt` | string (date-time) | When the trigger last changed, in UTC. |
| `listeningIdleReason` | string | Why a `linkedin_post_engagement` trigger that lists topics or watched profiles finds nothing now. `no_opted_in_seat`: no LinkedIn account in the workspace has research reads turned on, and only such an account reads topics and watched profiles. Returned when you get or list triggers; left out when the trigger can be read, and for every other trigger. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/triggers/812" \
  -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,
    "campaignId": 812,
    "stagingCampaignId": 812,
    "signalType": "link_clicked",
    "tier": "minutes",
    "parameters": "{\"count\":3,\"windowMinutes\":10}",
    "audienceFilter": "{\"sourceCampaignIds\":[1,2]}",
    "cooldownMinutes": 1,
    "maxAgeMinutes": 1,
    "priority": 1,
    "stopSourceSequence": true,
    "status": "active",
    "createdAt": "2026-09-23T15:02:11Z",
    "updatedAt": "2026-09-23T15:02:11Z",
    "listeningIdleReason": "string"
  }
}
```

## Update a trigger

`PATCH /v1/triggers/{triggerId}` - operationId `triggers.update`

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

Changes the fields you send. Omitted fields keep their values.

The body can hold `status` (`active` or `paused`), `parameters` (a JSON string),
`audienceFilter` (a JSON string, or null to clear the filter), `cooldownMinutes`,
`maxAgeMinutes`, `priority` and `stopSourceSequence`. Their rules are the same as on create.
`tier` (`minutes`, `hours` or `same_day`) is still accepted but deprecated: it has no
effect. `signalType` and `campaignId` cannot change. To archive a trigger, use
`DELETE /v1/triggers/{triggerId}`.

Errors:

- `400 validation_failed`: a field has the wrong type or value, the body changes `signalType` or
`campaignId`, `status` is `archived`, or the trigger is archived.
- `402 plan_required`: the body sends `parameters`, or sets `status` to `active` on a trigger
that is not active, and the workspace's plan does not include the feature the signal type reads (as on create).
Pausing and other edits are not refused.
- `404 not_found`: the workspace has no trigger with this id.
- `409 conflict`: an active trigger of this type already exists for the campaign.

Requires Campaigns edit.

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

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `triggerId` | path | integer (int64) | yes | The trigger's id. |
| `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`. |

### Request body

`application/json`, optional: `object`.

The fields to change.

### Response 200

`data` is a `Trigger`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | integer (int64) | The trigger's id. |
| `campaignId` | integer (int64) | The campaign the trigger adds contacts to. |
| `stagingCampaignId` | integer (int64) | For a `lead_uploaded` or `webhook_lead_received` trigger, the staging campaign where new leads wait for email enrichment and verification before the trigger adds them. Null for the other signal types. |
| `signalType` | string | The signal type the trigger watches, such as `link_clicked`, `reply_received` or `fundraising`. |
| `tier` | string | Deprecated: no effect. Every trigger is processed at the same speed whatever its tier, and `maxAgeMinutes` bounds how long a firing may wait. Still returned and accepted: `minutes`, `hours` or `same_day`. |
| `parameters` | string | The signal type's parameters as a JSON string, such as `{"count":3,"windowMinutes":10}`. |
| `audienceFilter` | string | The campaigns whose contacts the trigger watches, as a JSON string such as `{"sourceCampaignIds":[1,2]}`. Null watches every campaign in the workspace. |
| `cooldownMinutes` | integer (int32) | How long, in minutes, the trigger waits before it fires again for the same contact. |
| `maxAgeMinutes` | integer (int32) | How long, in minutes, a firing may wait to be processed. An older firing is suppressed as `expired`. |
| `priority` | integer (int32) | When several triggers fire for the same person at once, only the highest priority one acts. The others are suppressed as `lost_arbitration`. |
| `stopSourceSequence` | boolean | True when Kenso stops the contact's sequence in its current campaign as the trigger adds it to this one. |
| `status` | string | The trigger's status: `active`, `paused` or `archived`. |
| `createdAt` | string (date-time) | When the trigger was created, in UTC. |
| `updatedAt` | string (date-time) | When the trigger last changed, in UTC. |
| `listeningIdleReason` | string | Why a `linkedin_post_engagement` trigger that lists topics or watched profiles finds nothing now. `no_opted_in_seat`: no LinkedIn account in the workspace has research reads turned on, and only such an account reads topics and watched profiles. Returned when you get or list triggers; left out when the trigger can be read, and for every other trigger. |

### Request

```bash
curl -X PATCH "https://api.ken.so/v1/triggers/812" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID" \
  -H "Content-Type: application/json" \
  -d '{}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "id": 812,
    "campaignId": 812,
    "stagingCampaignId": 812,
    "signalType": "link_clicked",
    "tier": "minutes",
    "parameters": "{\"count\":3,\"windowMinutes\":10}",
    "audienceFilter": "{\"sourceCampaignIds\":[1,2]}",
    "cooldownMinutes": 1,
    "maxAgeMinutes": 1,
    "priority": 1,
    "stopSourceSequence": true,
    "status": "active",
    "createdAt": "2026-09-23T15:02:11Z",
    "updatedAt": "2026-09-23T15:02:11Z",
    "listeningIdleReason": "string"
  }
}
```

## Archive a trigger

`DELETE /v1/triggers/{triggerId}` - operationId `triggers.delete`

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

Archives the trigger, so it stops firing. An archived trigger cannot be changed or made active again, and it
stays readable.

Errors:

- `404 not_found`: the workspace has no trigger with this id.
- `409 conflict`: another request changed the trigger at the same time. Read it again and retry.

Requires Campaigns edit.

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

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `triggerId` | path | integer (int64) | yes | The trigger's id. |
| `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 204

### Request

```bash
curl -X DELETE "https://api.ken.so/v1/triggers/812" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID"
```

### Example response

```http
HTTP/1.1 204 No Content
```

## Preview a trigger's matching companies

`POST /v1/triggers/preview` - operationId `triggers.preview`

| Permission | Rate limit |
| --- | --- |
| Campaigns edit | 240 requests a minute per API key |

Runs a trigger's parameters against live company data and shows which companies would match, how many pass
each step, and an estimated credit cost. Kenso saves nothing, fires nothing and charges nothing, and the
preview does not use your export allowance. Use it to tune parameters before you create the trigger.

`signalType` is `fundraising`, `open_roles` or `company_headcount_growth`.
`parameters` is a JSON object with the same keys a trigger stores. `limit` is from 1 to 25 companies,
default 25. To read the next page, pass `pagination.nextCursor` as `cursor`.

Every page has:

- `companies`: sample matching companies.
- `total`: the matching companies across all pages, or null for `open_roles`.
- `steps`: the name, count and description of each filter step on this page, in order. The last step,
`max_contacts_per_company`, is the most people the page can import.
- `estimatedCredits`: `isEstimate` (always true), `leads`, `credits`,
`totalMillicredits`, `lines` and `basis`. `basis` says how Kenso computed it: those people
at the leads rate of `POST /v1/credits/estimates`.

Errors:

- `400 validation_failed`: `signalType` or `parameters` is invalid. For a signal type the
preview does not cover, `error.details[0].code` is `preview_not_supported`.

Requires Campaigns edit.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/triggers/POST/v1/triggers/preview)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `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`. |

### Request body

`application/json`, optional.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `signalType` | string | yes | Required. The signal type to preview: `fundraising`, `open_roles` or `company_headcount_growth`. |
| `parameters` | object | yes | Required. The trigger's parameters as a JSON object, with the same keys a trigger stores. |
| `limit` | integer (int32) | no | How many companies to return, from 1 to 25. Default 25. |
| `cursor` | string | no | The `pagination.nextCursor` of the previous page. |

### Response 200

`data` is a `TriggerPreviewPage`.

| Field | Type | Description |
| --- | --- | --- |
| `signalType` | string | The previewed signal type: `open_roles` or `company_headcount_growth`. Left out for `fundraising`. |
| `month` | string | The month of the headcount data, as `yyyy-MM`. Present only for `company_headcount_growth`. |
| `companies` | array of TriggerPreviewCompany | Sample matching companies on this page. |
| `total` | integer (int64) | The matching companies across all pages. Null for `open_roles`. For `fundraising` it stops at 1,000 (see `totalIsCapped`). |
| `totalIsCapped` | boolean | True when `total` stopped at 1,000, so more companies match. Present only for `fundraising`. |
| `steps` | array of TriggerPreviewStep | Each filter step on this page, in order, with how many companies or people pass it. The last step, `max_contacts_per_company`, is the most people the page can import. |
| `estimatedCredits` | TriggerPreviewCreditEstimate | The estimated lead credits for the people this page can import. Kenso charges nothing for a preview. |
| `pagination` | TriggerPreviewPagination | How to get the next page. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/triggers/preview" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID" \
  -H "Content-Type: application/json" \
  -d '{
  "signalType": "fundraising",
  "parameters": null,
  "limit": 1,
  "cursor": "eyJpZCI6ODE1fQ"
}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "signalType": "open_roles",
    "month": "string",
    "companies": [
      {
        "kenCompanyId": 812,
        "companyId": 812,
        "name": "string",
        "domain": "acme.com",
        "linkedinUrl": "https://example.com",
        "openJobCount": 1,
        "jobs": [
          {
            "title": "string",
            "location": "string",
            "source": "string",
            "url": "https://example.com"
          }
        ],
        "previousHeadcount": 1,
        "currentHeadcount": 1,
        "growthAbs": 1,
        "growthPct": 0.5,
        "websiteUrl": "https://example.com",
        "city": "string",
        "state": "string",
        "industry": "string",
        "revenueRange": "string",
        "foundedYear": 1,
        "totalRaisedUsd": 1,
        "raises": [
          {
            "reportedAt": "string",
            "amountRaisedUsd": 1,
            "roundRaisedUsd": 1,
            "roundSizeUsd": 1,
            "isOpenEnded": true,
            "investorCount": 1,
            "isNewRound": true
          }
        ],
        "executives": [
          {
            "name": "string",
            "title": "string"
          }
        ]
      }
    ],
    "total": 1,
    "totalIsCapped": true,
    "steps": [
      {
        "name": "string",
        "count": 1,
        "description": "string"
      }
    ],
    "estimatedCredits": {
      "isEstimate": true,
      "leads": 1,
      "totalMillicredits": 1,
      "credits": 0.5,
      "lines": [
        {
          "action": "ai_qualification",
          "units": 1,
          "millicredits": 1,
          "description": "string"
        }
      ],
      "basis": "string"
    },
    "pagination": {
      "nextCursor": "eyJpZCI6ODE1fQ",
      "hasMore": true
    }
  }
}
```

## Test a trigger with a sample signal

`POST /v1/triggers/{triggerId}/test-fire` - operationId `triggers.test-fire`

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

Checks one sample signal of the trigger's own type the way Kenso checks a real one, and says whether the trigger
would fire and why. Kenso queues no signal, starts no cooldown, records no firing, changes no counter, and sends
or charges nothing. It does not replay recent signals: the sample is the only input.

`contactId` is required. `campaignId` feeds the audience filter. `payload` is the signal's JSON
object, for example `clickedUrl` for `link_clicked` or `classification` for
`reply_received`. `occurredAt` defaults to now.

Kenso runs every check in order: `status`, `audience_filter`, `parameters` and
`cooldown`. `rejectedBy` names the first that failed. `status` fails for a paused or archived
trigger and for one whose campaign was deleted. A real firing can still be suppressed later, for example by do
not contact, the blocklist or a frequency cap.

Errors:

- `400 validation_failed`: `contactId` is missing, the contact or campaign is not in the workspace,
or the body is invalid. For a signal type that only a scheduled scan produces, `error.details[0].code` is
`test_fire_not_supported`.
- `404 not_found`: the workspace has no trigger with this id.

Requires Campaigns edit.

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

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `triggerId` | path | integer (int64) | yes | The trigger to test. |
| `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`. |

### Request body

`application/json`, optional.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `contactId` | integer (int64) | yes | Required. The contact the sample signal is about. It must be in the workspace. |
| `campaignId` | integer (int64) | no | The campaign the sample came from, checked against the trigger's audience filter. It must be in the workspace. |
| `payload` | object | no | The signal's data, a JSON object of at most 16 KB, such as `{"clickedUrl":"https://example.com"}`. |
| `occurredAt` | string (date-time) | no | When the sample happened, in ISO 8601, within the last 365 days and not in the future. Default now. |

### Response 200

`data` is a `TriggerTestFire`.

| Field | Type | Description |
| --- | --- | --- |
| `object` | string | Always `trigger_test_fire`. |
| `triggerId` | integer (int64) | The trigger that was tested. |
| `signalType` | string | The trigger's signal type, which is also the sample's type. |
| `status` | string | The trigger's status: `active`, `paused` or `archived`. |
| `shouldFire` | boolean | True only when every check passed, so the trigger would fire for this sample now. |
| `rejectedBy` | string | The name of the first check that failed. Null when all passed. |
| `checks` | array of TriggerTestFireCheck | Every check, in the order Kenso runs them: `status`, `audience_filter`, `parameters` and `cooldown`. All of them run, even after one fails. |
| `evidence` | object | The evidence a real firing would record, as a JSON object. Null when the sample did not meet the parameters. |
| `scheduledFor` | string (date-time) | When the trigger delays its firing, the time it would act, in UTC. Null otherwise. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/triggers/812/test-fire" \
  -H "Authorization: Bearer $KENSO_API_KEY" \
  -H "Ken-Version: 2026-11-02" \
  -H "X-Ken-Workspace-Id: $KENSO_WORKSPACE_ID" \
  -H "Content-Type: application/json" \
  -d '{
  "contactId": 812,
  "campaignId": 812,
  "payload": null,
  "occurredAt": "2026-09-23T15:02:11Z"
}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "object": "string",
    "triggerId": 812,
    "signalType": "string",
    "status": "active",
    "shouldFire": true,
    "rejectedBy": "string",
    "checks": [
      {
        "name": "status",
        "passed": true,
        "message": "string"
      }
    ],
    "evidence": null,
    "scheduledFor": "2026-09-23T15:02:11Z"
  }
}
```

## Get a trigger's firing stats

`GET /v1/triggers/{triggerId}/stats` - operationId `triggers.get-stats`

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

Returns how many times the trigger fired over the last `days` days, how many of those firings added the
contact to the campaign, and how many Kenso suppressed, by reason.

`days` is from 1 to 90, default 7.

Errors:

- `400 validation_failed`: `days` is out of range.
- `404 not_found`: the workspace has no trigger with this id.

Requires Campaigns view.

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

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `triggerId` | path | integer (int64) | yes | The trigger's id. |
| `days` | query | integer (int32) | no | How many days back to count, from 1 to 90. Default 7. |
| `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 `TriggerStats`.

| Field | Type | Description |
| --- | --- | --- |
| `fired` | integer (int32) | How many times the trigger fired in the period. |
| `exported` | integer (int32) | How many of those firings added the contact to the campaign. |
| `suppressed` | integer (int32) | How many of those firings Kenso suppressed. |
| `suppressionBreakdown` | map of integer (int32) | The suppressed firings by reason, such as `cooldown` or `do_not_contact`, with a count for each. |
| `lastFiredAt` | string (date-time) | When the trigger last fired, at any time, in UTC. Null when it never fired. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/triggers/812/stats" \
  -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": {
    "fired": 1,
    "exported": 1,
    "suppressed": 1,
    "suppressionBreakdown": {
      "key": 1
    },
    "lastFiredAt": "2026-09-23T15:02:11Z"
  }
}
```

## 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.

### TriggerPreviewCompany

A sample company on a trigger preview page. The fields present depend on the signal type. Kenso may add fields to it.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `kenCompanyId` | integer (int64) | no | The company's Kenso company id. Present for `open_roles` and `company_headcount_growth`. |
| `companyId` | integer (int64) | no | The company's id in the funding data, the value the funding round `companyIds` filter takes. Present only for `fundraising`. |
| `name` | string | no | The company's name. Null when unknown. |
| `domain` | string | no | The company's web domain, for example `acme.com`. Null when unknown. |
| `linkedinUrl` | string | no | The company's LinkedIn page URL. Null when unknown. Present for `open_roles` and `company_headcount_growth`. |
| `openJobCount` | integer (int32) | no | How many open jobs the company has. Present only for `open_roles`. |
| `jobs` | array of TriggerPreviewJob | no | Up to 3 of the company's matching open jobs. Present only for `open_roles`. |
| `previousHeadcount` | integer (int32) | no | The company's employee count the month before. Null when unknown. Present only for `company_headcount_growth`. |
| `currentHeadcount` | integer (int32) | no | The company's employee count this month. Null when unknown. Present only for `company_headcount_growth`. |
| `growthAbs` | integer (int32) | no | How many employees the company added over the month. Null when unknown. Present only for `company_headcount_growth`. |
| `growthPct` | number (float) | no | The company's headcount growth over the month, in percent. Null when unknown. Present only for `company_headcount_growth`. |
| `websiteUrl` | string | no | The company's website URL. Null when unknown. Present only for `fundraising`. |
| `city` | string | no | The city the company reported with its newest matching round. Null when unknown. Present only for `fundraising`. |
| `state` | string | no | The two-letter US state the company reported. Null outside the US or when unknown. Present only for `fundraising`. |
| `industry` | string | no | The company's industry as reported with its newest matching round. Null when unknown. Present only for `fundraising`. |
| `revenueRange` | string | no | The company's revenue range as reported with its newest matching round. Null when unknown. Present only for `fundraising`. |
| `foundedYear` | integer (int32) | no | The year the company was founded. Null when unknown. Present only for `fundraising`. |
| `totalRaisedUsd` | integer (int64) | no | The company's total raised to date across all its rounds, in whole US dollars. Null when unknown. Present only for `fundraising`. |
| `raises` | array of TriggerPreviewRaise | no | Up to 10 of the company's matching round reports, newest first. Present only for `fundraising`. |
| `executives` | array of TriggerPreviewExecutive | no | The executive officers named on the newest matching round. Present only for `fundraising`. |

### TriggerPreviewStep

One filter step of a trigger preview.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `name` | string | no | The step: `funding_filters` for `fundraising`; `job_filter`, `resolved_company` for `open_roles`; `min_growth_pct`, `min_growth_abs` for `company_headcount_growth`; `min_company_size` and `people_filter` for both of those; and `max_contacts_per_company`, always last. |
| `count` | integer (int64) | no | How many companies on this page pass the step, or people for `people_filter` and `max_contacts_per_company`. Null when the step could not be counted. |
| `description` | string | no | What the step counts, in words. |

### TriggerPreviewCreditEstimate

An estimate of the lead credits for the people a preview page can import. Never charged.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `isEstimate` | boolean | no | Always true: this is an estimate, not a quote. |
| `leads` | integer (int32) | no | The people the page can import, the count of the `max_contacts_per_company` step. |
| `totalMillicredits` | integer (int64) | no | The estimated cost in millicredits (1,000 to a credit). |
| `credits` | number (double) | no | The estimated cost in credits. |
| `lines` | array of TriggerPreviewCreditLine | no | The estimate per charged action. Empty when `leads` is 0. |
| `basis` | string | no | How Kenso computed the estimate, in words. |

### TriggerPreviewPagination

How to get the next page of a trigger preview. Kenso may add fields to it.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `nextCursor` | string | no | Send it as `cursor` with the same parameters to get the next page. Null on the last page. |
| `hasMore` | boolean | no | True when there is a next page. Left out for `fundraising`; read `nextCursor` there. |

### TriggerPreviewJob

A sample open job of a company on an `open_roles` preview.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `title` | string | no | The job title. Null when unknown. |
| `location` | string | no | The job's location. Null when unknown. |
| `source` | string | no | The job board the posting came from. Null when unknown. |
| `url` | string | no | The URL to apply for the job. Null when unknown. |

### TriggerPreviewRaise

A report of a round on a `fundraising` preview. Kenso may add fields to it.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `reportedAt` | string | no | The day the round was reported, as `yyyy-MM-dd`. |
| `amountRaisedUsd` | integer (int64) | no | The money this report adds, in whole US dollars. Null when unknown. |
| `roundRaisedUsd` | integer (int64) | no | The total sold in the round so far, in whole US dollars. Null when unknown. |
| `roundSizeUsd` | integer (int64) | no | The round's target size in whole US dollars. Null when the round is open-ended or the size is unknown. |
| `isOpenEnded` | boolean | no | True when the round has no set size. |
| `investorCount` | integer (int32) | no | How many investors have put money into the round. Null when unknown. |
| `isNewRound` | boolean | no | True when this is the first report of a new round, false for a later update of a round. |

### TriggerPreviewExecutive

An executive officer named on a round. Kenso may add fields to it.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `name` | string | no | The person's full name. Null when unknown. |
| `title` | string | no | The person's title as reported, or `Executive officer` when none is given. |

### TriggerPreviewCreditLine

One charged action in a trigger preview's credit estimate.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `action` | string | no | The action: `ai_qualification`, `email_found` or `ai_personalization`. |
| `units` | integer (int64) | no | How many times the action runs. |
| `millicredits` | integer (int64) | no | The estimated cost of the action in millicredits. |
| `description` | string | no | What the action covers, in words. |

### TriggerTestFireCheck

One check of a trigger test.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `name` | string | no | The check's name: `status`, `audience_filter`, `parameters` or `cooldown`. |
| `passed` | boolean | no | True when the sample passed this check. |
| `message` | string | no | What the check found, in plain words. |

### 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. |

All resources: [/docs.md](/docs.md).
