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

# Funding rounds: Resolve filter values

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

## Resolve filter values

`POST /v1/funding-rounds/filters/resolve` - operationId `funding-rounds.resolve-filters`

| Permission | Rate limit |
| --- | --- |
| Search view | 4,800 requests a minute per API key |

Turn partial text into the exact values a funding round filter accepts, for type-ahead filter pickers.

Send `field` (`companies`, `industries`, `states` or `people`), `query` (the text
typed so far) and `limit`. The answer's `values` list holds each match's `value` to send as a
filter, its `label` to show, and its `count` of rounds.

The call is free and does not use the export allowance.

Errors:

- `400 validation_failed`: `field` is unknown or a value is not valid.
- `402 plan_required`: the workspace's plan does not include funding signals. `error.refusal` carries
the code `PLAN_FEATURE_NOT_AVAILABLE` and the feature `funding_signals`.
- `413 validation_failed`: the body is larger than 1 MB.
- `503 service_unavailable`: the funding data is not available right now. Try again.
- `504 upstream_timeout`: the funding data took too long to answer. Try again.

Requires Search view.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/funding-rounds/POST/v1/funding-rounds/filters/resolve)

### Parameters

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

| Field | Type | Description |
| --- | --- | --- |
| `values` | array of FundingRoundFilterValue | The matching values. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/funding-rounds/filters/resolve" \
  -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": {
    "values": [
      {
        "value": "string",
        "label": "string",
        "count": 1
      }
    ]
  }
}
```

## Types

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

### FundingRoundFilterValue

One filter value that matches the text sent to resolve.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `value` | string | no | The value to send in the filter: for a company its domain, or its name when it has none. |
| `label` | string | no | The text to show for the value: a company's name, or the value itself. |
| `count` | integer (int64) | no | How many rounds have this value. |
