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

# AI feedback: Get one of the caller's ratings

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

## Get one of the caller's ratings

`GET /v1/ai-feedback/{feedbackId}` - operationId `ai-feedback.get`

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

The caller's own rating and its reward, for the poll after Send (every 1.5 s for up to 15 s). Another person's
rating, another workspace's, a cleared rating or an unknown id is `404`. A read that fails is
`503 service_unavailable`: retry it. A credential with no member behind it is `403 forbidden`, and a
Network member seat is `403 permission_denied`.

Needs the `ai_feedback` 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/ai-feedback/GET/v1/ai-feedback/%7BfeedbackId%7D)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `feedbackId` | 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 `AiFeedback`.

| Field | Type | Description |
| --- | --- | --- |
| `id` | integer (int64) |  |
| `surface` | string | Where the output shows, such as `ken_chat` or `reply_draft`. |
| `targetRef` | string | The output's id on that surface. |
| `rating` | string | `up` or `down`. |
| `reasons` | array of string | Reason chip keys. |
| `note` | string | The note; omitted when there is none. |
| `noteWords` | integer (int32) | Words in the note as the server counts them (tokens of at least 2 letters). This count sets the tier. |
| `reward` | AiFeedbackReward | The reward on a rating's note. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/ai-feedback/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": 812,
    "surface": "ken_chat",
    "targetRef": "string",
    "rating": "up",
    "reasons": [
      "string"
    ],
    "note": "string",
    "noteWords": 1,
    "reward": {
      "status": "none",
      "tier": "none",
      "credits": 1,
      "reason": "filler",
      "alreadyRewarded": true
    }
  }
}
```

## Types

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

### AiFeedbackReward

The reward on a rating's note.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `status` | string, one of: none, pending, granted, held_review, held_unpaid, rejected | no | `none` (no note, or rewards do not apply), `pending` (being checked, usually seconds), `granted`, `held_review` (a person on the team reviews it), `held_unpaid` (paid once the workspace pays an invoice) or `rejected`. |
| `tier` | string, one of: none, short, detailed | no | `none`, `short` or `detailed`. |
| `credits` | integer (int32) | no | Credits granted or held (whole credits). |
| `reason` | string | no | Why the note earned nothing or is held, when it did: absent for `pending`, `granted` and `held_unpaid`. With status `none`: `too_short` (the note is too short to earn; a fuller note on this output still can) or `already_rated` (this person's one reward on this output is on another of their ratings). With status `rejected`: `filler`, `duplicate`, `unverified`, `no_proof`, `judged_none`, `workspace_excluded` or `staff_rejected`. With status `held_review`: `no_resolver`, `judge_failed`, `flagged_person` or `over_daily_amount`. |
| `alreadyRewarded` | boolean | no | This person already earned (or holds) a reward on this output, so this note earns nothing more. |
