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

# Job postings: Resolve job 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 [Job postings](/docs/api/job-postings.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## Resolve job filter values

`POST /v1/job-postings/filters/resolve` - operationId `job-postings.resolve-filters`

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

Turn partial company, job title or location text into the exact values a job posting filter accepts, for
type-ahead filter pickers.

Unlike a search, the call needs no filter. It is free and does not use the export allowance.

Errors:

- `400 validation_failed`: a field is not valid.
- `402 plan_required`: the workspace's plan does not include job post search. `error.refusal` carries
the code `PLAN_FEATURE_NOT_AVAILABLE` and the feature `job_post_search`.
- `413 validation_failed`: the body is larger than 1 MB.
- `503 service_unavailable`: job postings are not available right now. Try again.
- `504 upstream_timeout`: job postings took too long to answer. Try again.

Requires Search view.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/job-postings/POST/v1/job-postings/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 `JobPostingFilterValues`.

| Field | Type | Description |
| --- | --- | --- |
| `companies` | array of JobPostingCompanyMatch | Companies whose name, a word of their name or their domain starts with the `companies` text, most open postings first. Empty when that text is under 2 characters. |
| `titles` | array of JobPostingValueCount | Job titles with a word that starts with the `titles` text, most open postings first. Empty when that text is under 2 characters. |
| `locations` | array of JobPostingLocationValue | Locations with a word that starts with the `locations` text, most open postings first. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/job-postings/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": {
    "companies": [
      {
        "id": "string",
        "name": "string",
        "domain": "example.com",
        "open_jobs": 1
      }
    ],
    "titles": [
      {
        "value": "string",
        "count": 1
      }
    ],
    "locations": [
      {
        "value": "string",
        "count": 1,
        "kind": "country"
      }
    ]
  }
}
```

## Types

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

### JobPostingCompanyMatch

A company that matches the `companies` text.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | string | no | The company's id in the job postings index, as a string. The `companies.ids` filter takes it. |
| `name` | string | no | The company's name. |
| `domain` | string | no | The company's web domain. Null when unknown. |
| `open_jobs` | integer (int64) | no | How many open postings the company has. |

### JobPostingValueCount

A value and how many job postings have it.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `value` | string | no | The value, as the matching filter takes it. |
| `count` | integer (int64) | no | How many postings have the value: matching postings in a facet, open postings in a filter suggestion. |

### JobPostingLocationValue

A location that matches the `locations` text.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `value` | string | no | The value, as the matching filter takes it. |
| `count` | integer (int64) | no | How many postings have the value: matching postings in a facet, open postings in a filter suggestion. |
| `kind` | string | no | What the location is: `country`, `region`, `state` or `city`. |
