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

# Bug reports: Add a note to a bug report

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

## Add a note to a bug report

`POST /v1/bug-reports/{bugReportId}/notes` - operationId `bug-reports.notes-create`

| Permission | Rate limit |
| --- | --- |
| Any workspace member except a Network member | 20 requests a day per user; 50 requests a day per workspace |

Adds the user's note to a bug report they filed, for the Kenso team to read with the report. Use the `id`
from the report's receipt as `bugReportId`. Answers 201 with `status` set to `received`.

Send a JSON body with one required field, `note`: the user's own words, from 1 to 10,000 characters once
leading and trailing spaces are trimmed.

Only the member who filed the report can add a note, in the same workspace, within 24 hours of filing. Each note
counts once toward the same daily limits as reports: 20 for the caller and 50 for the workspace. A note that Kenso
could not add does not count.

Errors:

- `400 validation_failed`: `note` is missing, blank or longer than 10,000 characters.
- `404 not_found`: the id is unknown, expired after 24 hours, or belongs to another member or workspace.
- `429 quota_exceeded`: the caller or the workspace reached its daily limit. Wait for the seconds in
`Retry-After`, or until `quotaResetAt`.
- `503 service_unavailable`: Kenso could not add the note. Try again later.

Open to any workspace member, Client seats included.

Needs the `bug_reports` 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/bug-reports/POST/v1/bug-reports/%7BbugReportId%7D/notes)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `bugReportId` | path | string | 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 |
| --- | --- | --- | --- |
| `note` | string | yes | What the user was doing or anything else they want to add, in their own words. Required, from 1 to 10000 characters once leading and trailing spaces are trimmed. |

### Response 201

`data` is a `BugReportNoteReceipt`.

| Field | Type | Description |
| --- | --- | --- |
| `status` | string | Always `received`: the Kenso team has the note with the report. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/bug-reports/01JC8Z3K6Q2W4M7N9P5R1T3V5X/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 '{
  "note": "string"
}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "status": "string"
  }
}
```
