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

# Meeting briefs: Get a meeting's prep brief

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

## Get a meeting's prep brief

`GET /v1/meetings/{meetingId}/client-brief` - operationId `meetings.get-client-brief`

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

Returns the prep brief of a meeting you can see, without its credit cost and write state. This call never writes
a brief and never charges credits. Members with Meetings edit write and refresh briefs in the Kenso app.

`status` is `ready` when a brief exists, `not_written` when the meeting qualifies but has no brief
yet, or `not_eligible`. `ineligibleReason` then says why: `not_account_meeting`, `no_owner`,
`cancelled`, `owner_declined`, `no_external_guest`, `too_many_guests` or
`already_started`. `isStale` is true when the account had new activity after the brief was written, and
`staleSince` says when that activity started. Every line in `sections` lists its `sources`.

Errors:

- `403 forbidden`: the API key is not tied to a member of the workspace.
- `404 not_found`: the meeting is not in this workspace, or you cannot see it.

Requires Meetings view.

Needs the `meetings` 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/meetings/GET/v1/meetings/%7BmeetingId%7D/client-brief)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `meetingId` | path | string | yes | The meeting's id, starting with `mtg_`. |
| `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 `MeetingClientBrief`.

| Field | Type | Description |
| --- | --- | --- |
| `meetingId` | string | The meeting's id, starting with `mtg_`. |
| `status` | string | Where the brief is: `ready`, `not_written` or `not_eligible`. |
| `ineligibleReason` | string | Why the meeting gets no brief: `not_account_meeting`, `no_owner`, `cancelled`, `owner_declined`, `no_external_guest`, `too_many_guests`, `already_started`, `no_brief_for_type` or `brief_off_for_type`. Omitted while the meeting qualifies. |
| `version` | integer (int32) | The brief's version: 0 until the first brief is written, then one more on each rewrite. |
| `writtenAt` | string (date-time) | When the current version was written (UTC); omitted until then. |
| `language` | string | The language the brief is written in, such as `en`. |
| `authorSource` | string | Who wrote the current version: `ken`, `agent` or `user`. Omitted until it is written. |
| `meetingType` | string | The meeting type the current version was written for; omitted until it is written, and for a brief written without a type. |
| `staleSince` | string (date-time) | The account's first activity after `writtenAt`. |
| `isStale` | boolean | True when the account had activity after the brief was written. |
| `sections` | MeetingBriefSections | The brief itself; omitted until it is written. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/meetings/mtg_2bX9kq4LmR7tW3vY/client-brief" \
  -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": {
    "meetingId": "mtg_2bX9kq4LmR7tW3vY",
    "status": "ready",
    "ineligibleReason": "not_account_meeting",
    "version": 1,
    "writtenAt": "2026-09-23T15:02:11Z",
    "language": "en",
    "authorSource": "ken",
    "meetingType": "string",
    "staleSince": "2026-09-23T15:02:11Z",
    "isStale": true,
    "sections": {
      "openWith": {
        "text": "string",
        "sources": [
          {
            "kind": "touch",
            "id": "msg_2bX9kq4LmR7tW3vY",
            "label": "string",
            "url": "https://example.com",
            "at": "2026-09-23T15:02:11Z"
          }
        ]
      },
      "attending": [
        {
          "name": "string",
          "email": "jane@example.com",
          "title": "string",
          "committeeRole": "champion",
          "isNew": true,
          "personId": 812,
          "stakeholderId": 812,
          "response": "yes"
        }
      ],
      "gotTheYes": {
        "text": "string",
        "sources": [
          {
            "kind": "touch",
            "id": "msg_2bX9kq4LmR7tW3vY",
            "label": "string",
            "url": "https://example.com",
            "at": "2026-09-23T15:02:11Z"
          }
        ]
      },
      "relationship": {
        "stage": "string",
        "touches": 1,
        "replies": 1,
        "firstContactAt": "2026-09-23T15:02:11Z",
        "lastTouchAt": "2026-09-23T15:02:11Z"
      },
      "whyNow": [
        {
          "text": "string",
          "sources": [
            {}
          ]
        }
      ],
      "angle": [
        {
          "text": "string",
          "sources": [
            {}
          ]
        }
      ],
      "openItems": [
        {
          "text": "string",
          "sources": [
            {}
          ]
        }
      ],
      "touchHistory": [
        {
          "at": "2026-09-23T15:02:11Z",
          "channel": "email",
          "direction": "outbound",
          "title": "string",
          "personName": "string",
          "source": {
            "kind": "touch",
            "id": "msg_2bX9kq4LmR7tW3vY",
            "label": "string",
            "url": "https://example.com",
            "at": "2026-09-23T15:02:11Z"
          }
        }
      ],
      "dataNote": "string"
    }
  }
}
```

## Types

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

### MeetingBriefSections

The brief's sections. `attending`, `relationship` and `touchHistory` come from Kenso's data. Ken writes the other lines, each with the sources it rests on.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `openWith` | MeetingBriefLine | no | The line to open the meeting with. |
| `attending` | array of MeetingBriefAttendee | no | The guests, the meeting's owner left out. |
| `gotTheYes` | MeetingBriefLine | no | The touch, asset or reply that led to the meeting. |
| `relationship` | MeetingBriefRelationship | no | The relationship with the account so far. |
| `whyNow` | array of MeetingBriefLine | no | Signals from the last 90 days. |
| `angle` | array of MeetingBriefLine | no | Two or three talking points. |
| `openItems` | array of MeetingBriefLine | no | Commitments and unanswered questions. |
| `touchHistory` | array of MeetingBriefTouch | no | The account's touches and emails, from Kenso's data, newest first. |
| `dataNote` | string | no | A note when the data is thin, such as "No outbound history yet; this is from the account's research." |

### MeetingBriefLine

One line of the brief and the sources it rests on.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `text` | string | no | The line's text. |
| `sources` | array of MeetingBriefSource | no | The sources the line rests on. |

### MeetingBriefAttendee

One guest on the meeting, the meeting's owner left out.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `name` | string | no | The guest's name. |
| `email` | string | no | The guest's email address. |
| `title` | string | no | The guest's job title, when Kenso knows it. |
| `committeeRole` | string | no | The guest's role on the account's buying committee: `champion`, `economic_buyer`, `approver`, `evaluator`, `user`, `executive_sponsor`, `blocker` or `unknown`. Omitted when the guest is not on the committee. |
| `isNew` | boolean | no | True when no earlier meeting with the account had this guest. |
| `personId` | integer (int64) | no | The guest's person id, when the guest is a person in the workspace. |
| `stakeholderId` | integer (int64) | no | The guest's stakeholder id, when the guest is on the account's committee. |
| `response` | string | no | The guest's answer to the invite: `yes`, `maybe`, `no` or `awaiting`. |

### MeetingBriefRelationship

The relationship with the account, counted from Kenso's data.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `stage` | string | no | The account's stage. |
| `touches` | integer (int32) | no | How many touches and campaign emails went out to the account. |
| `replies` | integer (int32) | no | How many replies came back. |
| `firstContactAt` | string (date-time) | no | The first message either way (UTC); omitted when there is none. |
| `lastTouchAt` | string (date-time) | no | The latest message that went out (UTC); omitted when there is none. |

### MeetingBriefTouch

One row of the touch history.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `at` | string (date-time) | no | When it happened (UTC). |
| `channel` | string | no | The channel it went through, such as `email`. |
| `direction` | string | no | Which way it went: `outbound` or `inbound`. |
| `title` | string | no | A one-line title for the row. |
| `personName` | string | no | The person it went to or came from, when known. |
| `source` | MeetingBriefSource | no | The touch or email the row comes from. |

### MeetingBriefSource

Where a line comes from.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `kind` | string | no | The kind of source: `touch`, `email`, `signal`, `person`, `account`, `research` or `workspace`. |
| `id` | string | no | The source's id: a touch, signal, person, account or workspace id as a string, or an email's id starting with `msg_`. |
| `label` | string | no | A short name for the source. |
| `url` | string | no | An outside link, for research claims and signals that have one. |
| `at` | string (date-time) | no | When the source happened (UTC), where it has a date. |
