> 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: Get a trigger's firing stats

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

## 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"
  }
}
```
