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

# Client approvals: List approval events

> **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 [Client approvals](/docs/api/client-approvals.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## List approval events

`GET /v1/client-approvals/events` - operationId `client-approvals.list-events`

| Permission | Rate limit |
| --- | --- |
| Any workspace member except a Network member | 12,000 requests a minute per API key |

Lists the approval log, newest first: items created, decisions, comments, lead removals and restores,
reminders, link rotations, rule changes, campaign pauses and resumes, submitted campaign reviews and share
link activity. Filter to one item with `itemId`, read older events with `before`, and page with
`limit` and `cursor`.

The log leaves out the events of items whose page you cannot view, as the item list does. Share link events
need Share, and campaign review events need Campaigns.

Errors:

- `400 validation_failed`: `limit` is not from 1 to 200, or `cursor` is invalid.

Open to any workspace member.

Needs the `client_approvals` 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/client-approvals/GET/v1/client-approvals/events)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `itemId` | query | integer (int64) | no | Only the entries of this approval item. |
| `before` | query | string (date-time) | no | Only entries before this time, as an ISO 8601 timestamp. The bound is exclusive, and a `cursor` replaces it. |
| `limit` | query | integer (int32) | no | Page size, from 1 to 200. Defaults to 50. |
| `cursor` | query | string | no | The `nextCursor` from the previous page. Omit it for the first page. |
| `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 `ClientApprovalEvent`. Each item has these fields. The response also carries `pagination`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | integer (int64) | Id of the entry. |
| `itemId` | integer (int64) | Id of the item the entry is about. Null for an entry about the whole workspace, such as a rules change. |
| `eventType` | string | What happened: `item_created`, `approved`, `changes_requested`, `commented`, `lead_removed`, `lead_restored`, `superseded`, `cancelled`, `reminder_sent`, `link_rotated`, `rules_changed`, `campaign_paused`, `campaign_resumed`, `classic_review_submitted`, `share_created`, `share_viewed`, `share_reminder_sent`, `share_submitted`, `share_revoked`, `report_sent`, `decision_undone` or `snapshot_refreshed`. Kenso may add new types, so handle unknown values. |
| `actorKind` | string | Who acted: `reviewer` (the client, through a link), `user` (a workspace member) or `system` (Kenso). |
| `actorName` | string | Name of the person who acted, when known. |
| `actorUserId` | integer (int64) | Id of the member who acted. Null unless `actorKind` is `user`. |
| `data` | object | Details of the entry as a JSON object. Its keys depend on `eventType`. Null when there are none. |
| `createdAt` | string (date-time) | When it happened, in UTC. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/client-approvals/events?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,
      "itemId": 812,
      "eventType": "item_created",
      "actorKind": "string",
      "actorName": "string",
      "actorUserId": 812,
      "data": null,
      "createdAt": "2026-09-23T15:02:11Z"
    }
  ],
  "pagination": {
    "nextCursor": "eyJpZCI6ODE1fQ",
    "hasMore": true,
    "total": 1,
    "totalCount": 1,
    "isTotalCapped": true
  }
}
```
