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

# Meeting notes

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

Meeting notes are call notes or a transcript you keep on an account, with each attendee linked to a person on it. Add a note for a meeting that happened, list an account's notes (each with a short excerpt), read one note in full and delete one. A note also shows on the account's meetings. A note on a private meeting shows only to the meeting's owner and workspace admins.

CRM. 4 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/meeting-notes/openapi.json](/docs/api/meeting-notes/openapi.json).

- `GET /v1/accounts/{accountId}/meeting-notes` - List an account's meeting notes (`meeting-notes.list`): [/docs/api/meeting-notes/list.md](/docs/api/meeting-notes/list.md)
- `POST /v1/accounts/{accountId}/meeting-notes` - Add meeting notes or a transcript to an account (`meeting-notes.create`): [/docs/api/meeting-notes/create.md](/docs/api/meeting-notes/create.md)
- `GET /v1/meeting-notes/{meetingNoteId}` - Return one meeting note with its full text (`meeting-notes.get`): [/docs/api/meeting-notes/get.md](/docs/api/meeting-notes/get.md)
- `DELETE /v1/meeting-notes/{meetingNoteId}` - Delete a meeting note (`meeting-notes.delete`): [/docs/api/meeting-notes/delete.md](/docs/api/meeting-notes/delete.md)

## List an account's meeting notes

`GET /v1/accounts/{accountId}/meeting-notes` - operationId `meeting-notes.list`

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

Newest first by `occurredAt`. Items omit `notes` and carry `excerpt` (the first 280
characters); get one note for the full text. A note on a private meeting shows only to the meeting's owner and
workspace admins, on list, get and delete. Requires accounts view.

Needs the `accounts` 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/meeting-notes/GET/v1/accounts/%7BaccountId%7D/meeting-notes)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `accountId` | path | integer (int64) | yes |  |
| `limit` | query | integer (int32) | no | Items per page, from 1 to 200. Default 50. |
| `cursor` | query | string | no | The `nextCursor` of 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 `MeetingNote`. Each item has these fields. The response also carries `pagination`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | integer (int64) |  |
| `accountId` | integer (int64) |  |
| `meetingId` | integer (int64) | The meeting that carries the note. Title, occurredAt, source and attendees are its. |
| `title` | string |  |
| `occurredAt` | string (date-time) |  |
| `source` | string | manual, transcript, gong, fathom, fireflies, zoom, teams, google_meet or other. A note added to a meeting already on the account (meetingId on create) carries that meeting's source, such as calendar or notetaker. |
| `attendees` | array of MeetingNoteAttendee |  |
| `notes` | string | Full note only (get and create). List items carry excerpt instead. |
| `excerpt` | string | List items only: the first 280 characters of notes. |
| `createdBy` | MeetingNoteActor | Who added the note. `via` is the agent client ("Claude Code"), absent for the web app. |
| `createdAt` | string (date-time) |  |
| `updatedAt` | string (date-time) |  |

### Request

```bash
curl -X GET "https://api.ken.so/v1/accounts/812/meeting-notes?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": 5001,
      "accountId": 6120,
      "meetingId": 9100,
      "title": "Discovery call",
      "occurredAt": "2026-10-14T15:00:00Z",
      "source": "zoom",
      "attendees": [
        {
          "name": "Amanda Chen",
          "email": "amanda.chen@northwind.example.com",
          "personId": 77310,
          "stakeholderId": 2410
        },
        {
          "name": "Alex Morgan",
          "email": "alex@mail.example.com"
        }
      ],
      "notes": "Amanda owns the outbound budget. Pilot in Q1 with two SDRs; she wants LinkedIn and email in one place.",
      "createdBy": {
        "kind": "user",
        "memberId": 1093
      },
      "createdAt": "2026-10-14T15:00:00Z",
      "updatedAt": "2026-10-14T15:00:00Z"
    }
  ],
  "pagination": {
    "nextCursor": "eyJpZCI6ODE1fQ",
    "hasMore": true,
    "total": 1,
    "totalCount": 1,
    "isTotalCapped": true
  }
}
```

## Add meeting notes or a transcript to an account

`POST /v1/accounts/{accountId}/meeting-notes` - operationId `meeting-notes.create`

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

`title` (1-200 characters), `occurredAt` (ISO 8601, at most one day ahead) and `notes`
(1-200,000 characters) are required. `source`: manual (default), transcript, gong, fathom,
fireflies, zoom, teams, google_meet, other. `attendees`: at most 50 of `{name, email}`,
each with a name or an email; an email listed twice is stored once. An email that matches a person in
the workspace links `personId`, and `stakeholderId` when that person is a stakeholder on this
account; no person is created. Creates the meeting the notes belong to (status done, no calendar event, owned by the
caller's member) with the attendees as participants, and records the added notes on the account timeline. That meeting counts as one of the account's meetings: notes stored before the account's first booking
make that booking not its first meeting, so its `meeting.booked` webhook carries `firstMeeting` false
and `meeting_booked` skills set to first meetings only do not run for it.

For a call already on the account, such as a synced calendar meeting, send `meetingId` and
`notes` only: the note goes on that meeting and no meeting is created,
so the account's meeting counts and first-meeting detection do not move. The response carries that meeting's
title, time, source and participants. `title`, `occurredAt`, `source` and `attendees` sent
with it are `400` (`invalid`). A meeting that is not on this account, or that the caller cannot see
(another member's private meeting), is `404`. Deleting the note later keeps the meeting. The response's `meetingId` names the meeting either way. Requires accounts edit.
A workspace key gets `403 forbidden`, with or without `meetingId`: a new meeting is owned by the
member who adds its notes, and a workspace key is not a person.

Needs the `accounts` 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/meeting-notes/POST/v1/accounts/%7BaccountId%7D/meeting-notes)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `accountId` | path | integer (int64) | yes |  |
| `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 |
| --- | --- | --- | --- |
| `meetingId` | integer (int64) | no | A meeting already on this account, such as a synced calendar meeting: the note goes on it and no meeting is created. Send only notes with it; title, occurredAt, source and attendees are the meeting's. |
| `title` | string | no | 1 to 200 characters. Required without meetingId. |
| `occurredAt` | string (date-time) | no | When the meeting happened. ISO 8601; a time without an offset is UTC. At most one day ahead. Required without meetingId. |
| `source` | string | no | manual (default), transcript, gong, fathom, fireflies, zoom, teams, google_meet or other. Not with meetingId. |
| `attendees` | array of MeetingNoteAttendeeBody | no | At most 50. Each needs a name or an email. Not with meetingId. |
| `notes` | string | yes | The notes or transcript, 1 to 200,000 characters. Required. |

### Response 201

`data` is a `MeetingNote`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | integer (int64) |  |
| `accountId` | integer (int64) |  |
| `meetingId` | integer (int64) | The meeting that carries the note. Title, occurredAt, source and attendees are its. |
| `title` | string |  |
| `occurredAt` | string (date-time) |  |
| `source` | string | manual, transcript, gong, fathom, fireflies, zoom, teams, google_meet or other. A note added to a meeting already on the account (meetingId on create) carries that meeting's source, such as calendar or notetaker. |
| `attendees` | array of MeetingNoteAttendee |  |
| `notes` | string | Full note only (get and create). List items carry excerpt instead. |
| `excerpt` | string | List items only: the first 280 characters of notes. |
| `createdBy` | MeetingNoteActor | Who added the note. `via` is the agent client ("Claude Code"), absent for the web app. |
| `createdAt` | string (date-time) |  |
| `updatedAt` | string (date-time) |  |

### Request

```bash
curl -X POST "https://api.ken.so/v1/accounts/812/meeting-notes" \
  -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 '{
  "title": "Discovery call",
  "occurredAt": "2026-10-14T15:00:00Z",
  "source": "zoom",
  "attendees": [
    {
      "name": "Amanda Chen",
      "email": "amanda.chen@northwind.example.com"
    },
    {
      "name": "Alex Morgan",
      "email": "alex@mail.example.com"
    }
  ],
  "notes": "Amanda owns the outbound budget. Pilot in Q1 with two SDRs; she wants LinkedIn and email in one place."
}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "id": 5001,
    "accountId": 6120,
    "meetingId": 9100,
    "title": "Discovery call",
    "occurredAt": "2026-10-14T15:00:00Z",
    "source": "zoom",
    "attendees": [
      {
        "name": "Amanda Chen",
        "email": "amanda.chen@northwind.example.com",
        "personId": 77310,
        "stakeholderId": 2410
      },
      {
        "name": "Alex Morgan",
        "email": "alex@mail.example.com"
      }
    ],
    "notes": "Amanda owns the outbound budget. Pilot in Q1 with two SDRs; she wants LinkedIn and email in one place.",
    "createdBy": {
      "kind": "user",
      "memberId": 1093
    },
    "createdAt": "2026-10-14T15:00:00Z",
    "updatedAt": "2026-10-14T15:00:00Z"
  }
}
```

## Return one meeting note with its full text

`GET /v1/meeting-notes/{meetingNoteId}` - operationId `meeting-notes.get`

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

Requires accounts view.

Needs the `accounts` 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/meeting-notes/GET/v1/meeting-notes/%7BmeetingNoteId%7D)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `meetingNoteId` | path | integer (int64) | yes |  |
| `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 `MeetingNote`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | integer (int64) |  |
| `accountId` | integer (int64) |  |
| `meetingId` | integer (int64) | The meeting that carries the note. Title, occurredAt, source and attendees are its. |
| `title` | string |  |
| `occurredAt` | string (date-time) |  |
| `source` | string | manual, transcript, gong, fathom, fireflies, zoom, teams, google_meet or other. A note added to a meeting already on the account (meetingId on create) carries that meeting's source, such as calendar or notetaker. |
| `attendees` | array of MeetingNoteAttendee |  |
| `notes` | string | Full note only (get and create). List items carry excerpt instead. |
| `excerpt` | string | List items only: the first 280 characters of notes. |
| `createdBy` | MeetingNoteActor | Who added the note. `via` is the agent client ("Claude Code"), absent for the web app. |
| `createdAt` | string (date-time) |  |
| `updatedAt` | string (date-time) |  |

### Request

```bash
curl -X GET "https://api.ken.so/v1/meeting-notes/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": 5001,
    "accountId": 6120,
    "meetingId": 9100,
    "title": "Discovery call",
    "occurredAt": "2026-10-14T15:00:00Z",
    "source": "zoom",
    "attendees": [
      {
        "name": "Amanda Chen",
        "email": "amanda.chen@northwind.example.com",
        "personId": 77310,
        "stakeholderId": 2410
      },
      {
        "name": "Alex Morgan",
        "email": "alex@mail.example.com"
      }
    ],
    "notes": "Amanda owns the outbound budget. Pilot in Q1 with two SDRs; she wants LinkedIn and email in one place.",
    "createdBy": {
      "kind": "user",
      "memberId": 1093
    },
    "createdAt": "2026-10-14T15:00:00Z",
    "updatedAt": "2026-10-14T15:00:00Z"
  }
}
```

## Delete a meeting note

`DELETE /v1/meeting-notes/{meetingNoteId}` - operationId `meeting-notes.delete`

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

Soft delete: the note leaves list and get. Its meeting is deleted too when nothing else is on it (no calendar
event, never recorded, no transcript, no other notes). Returns `204`. Requires accounts edit.

Needs the `accounts` 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/meeting-notes/DELETE/v1/meeting-notes/%7BmeetingNoteId%7D)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `meetingNoteId` | path | integer (int64) | yes |  |
| `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/meeting-notes/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
```

## Types

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

### MeetingNoteAttendee

One attendee. personId when the email matches a person in the workspace; stakeholderId when that person is a stakeholder on this account. Unmatched attendees keep only name and email.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `name` | string | no |  |
| `email` | string | no |  |
| `personId` | integer (int64) | no |  |
| `stakeholderId` | integer (int64) | no |  |

### MeetingNoteActor

Who added the note. `via` is the agent client ("Claude Code"), absent for the web app.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `kind` | string | yes |  |
| `memberId` | integer (int64) | no |  |
| `via` | string | no |  |

### MeetingNoteAttendeeBody

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `name` | string | no |  |
| `email` | string | no | Matched to a person in the workspace. Never creates one. |

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