Meeting briefs
A meeting is a calendar event with people outside your workspace. Before a meeting with an account, Ken writes a prep brief: who is attending, how the meeting came about, why now, talking points and open items, each line with its sources. This section reads that brief without its credit cost or write state, so you can show it to a Client seat.
Headers
The endpoints on this page take these headers. Each endpoint's curl shows the ones it sends.
| Name | In | Type | Required | Description |
|---|---|---|---|---|
Ken-Version | header | string, one of: 2026-11-02, 1.1 | optional | 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 date that is not a version answers 400 unsupported_version; any other value that is not a version is treated as legacy. |
X-Ken-Workspace-Id | header | integer (int64) | optional | 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. |
Get a meeting's prep brief
/v1/meetings/{meetingId}/client-briefmeetings.get-client-brief- Permission
- Calendar view
- Rate limit
- 12,000 requests a minute per API key
meetings feature on your workspace. Until it is on, calls answer 404.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.
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
meetingId | path | string | required | The meeting's id, starting with mtg_. |
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"Response 200
data is a MeetingClientBrief.
Show the 11 response fields and an example
The fields and an example are also on this endpoint's Markdown page.
More in Meetings and calls:Meeting typesBooking linksBookingsExternal bookingsCallingAll resources