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

# Event log: Poll events after a cursor

> **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 [Event log](/docs/api/event-occurrences.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## Poll events after a cursor

`GET /v1/event-occurrences` - operationId `event-occurrences.poll`

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

Returns the events logged after your cursor and the cursor to send on the next poll.

Start without `cursor`. Kenso then returns no events and a cursor at the current time, and starts logging
events for the workspace. Every poll keeps the log running for another 7 days. Send the returned
`cursor` back unchanged on the next poll.

`types` is a comma-separated list of event types. Omit it to get every type you can receive.
`campaignId` and `classification` filter the events that carry those fields. `limit` is from 1
to 100, default 50. `maxAgeMs` skips events older than that many milliseconds instead of returning them,
and the response then has `truncated: true`.

When `hasMore` is true, poll again right away. Otherwise wait `nextPollMs` milliseconds. Events
older than 7 days are gone from the log.

Errors:

- `400 validation_failed`: `limit`, `maxAgeMs`, `classification` or `cursor` is
invalid.
- `400 unsupported`: a type in `types` is not in the event log.
- `403 forbidden`: you cannot see the page of a type in `types`, or you are held to your own
accounts and a type in `types` is an Accounts-lane event (the `accounts`, `accounts_activity`,
`calls` and `meetings` groups, and `research.completed`). With `types` omitted, those
events are left out.
- `404 not_found`: event polling is not on for the workspace, or a type in `types` is unknown.

Open to any workspace member.

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

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `cursor` | query | string | no | The `cursor` of the previous poll, unchanged. Omitted: Kenso returns no events and a cursor at the current time. |
| `types` | query | string | no | A comma-separated list of event types, such as `reply.received,meeting.booked`. Omitted: every type you can receive. |
| `campaignId` | query | integer (int64) | no | Only events of this campaign. |
| `classification` | query | string | no | Only events with this reply classification, such as `interested`. |
| `limit` | query | integer (int32) | no | Events per poll, from 1 to 100. Default 50. |
| `maxAgeMs` | query | integer (int64) | no | Skip events older than this many milliseconds instead of returning them. Ignored without a cursor. |
| `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 `EventOccurrences`.

| Field | Type | Description |
| --- | --- | --- |
| `events` | array of EventOccurrence | The events after your cursor. Empty on the first poll without a cursor. |
| `cursor` | string | The cursor to send unchanged on the next poll. |
| `hasMore` | boolean | True when more events are waiting, so poll again right away. |
| `truncated` | boolean | True when Kenso skipped events, because they were older than `maxAgeMs` or no longer in the log. There is a gap before these events. |
| `nextPollMs` | integer (int32) | Milliseconds to wait before the next poll. 0 when `hasMore` is true. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/event-occurrences?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": {
    "events": [
      {
        "eventId": "string",
        "name": "meeting.booked",
        "timestamp": "2026-09-23T15:02:11Z",
        "data": null,
        "cursor": "eyJpZCI6ODE1fQ"
      }
    ],
    "cursor": "eyJpZCI6ODE1fQ",
    "hasMore": true,
    "truncated": true,
    "nextPollMs": 1
  }
}
```

## Types

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

### EventOccurrence

One event from the event log.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `eventId` | string | no | The event's id. The same event can arrive twice, so skip an id you already handled. |
| `name` | string | no | The event type, such as `meeting.booked`. |
| `timestamp` | string (date-time) | no | When the event happened, in UTC. |
| `data` | object | no | A short JSON object with ids, the status or classification, and `links`. Fetch the full records with the API. |
| `cursor` | string | no | The log position right after this event. Polling from it returns the events that follow. |
