> 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-post-searches/openapi.json](/docs/api/job-post-searches/openapi.json). CLI docs offline: `kenso docs <topic>`.
> Last updated: 2026-11-22.

# Job post search: Count people at hiring companies

> **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 post search](/docs/api/job-post-searches.md). Authentication, workspaces and errors: [/docs.md](/docs.md).

## Count people at hiring companies

`POST /v1/job-post-searches/people/count` - operationId `job-post-searches.count`

| Permission | Rate limit |
| --- | --- |
| Search view | 240 requests a minute per API key |

Count the people at the companies hiring for your job filters, without returning them. Use it to size an import.

Send the same `jobFilters` and `peopleFilters` as `POST /v1/job-post-searches/people`. The answer
holds `totalResults` and `hiringSet`. Counting does not use the `searchBrowseRows` quota.

Errors:

- `400 validation_failed`: the body is not a JSON object, `jobFilters` is missing or not an object,
`peopleFilters` is not an object, or Search refused the people filters.
- `401 unauthenticated`: the API key belongs to no member.
- `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`.
- `402 plan_required`: `peopleFilters` needs funding signals, which the plan lacks (`error.refusal`).
- `403 forbidden`: Search refused a people filter for this member.
- `422 filter_required`: `jobFilters` sets no filter.
- `503 service_unavailable`: job postings or Search are not available right now. Try again.

Requires Search view.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/job-post-searches/POST/v1/job-post-searches/people/count)

### 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`. |

### Request body

`application/json`, optional: `object`.

### Response 200

`data` is a `JobPostSearchPeopleCount`.

| Field | Type | Description |
| --- | --- | --- |
| `totalResults` | integer (int64) | How many people match the people filters at the hiring companies. |
| `hiringSet` | JobPostSearchHiringSet | The hiring companies the count covered. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/job-post-searches/people/count" \
  -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 '{}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "totalResults": 1,
    "hiringSet": {
      "count": 1,
      "truncated": true
    }
  }
}
```

## Types

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

### JobPostSearchHiringSet

The companies hiring for the job filters.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `count` | integer (int32) | no | How many hiring companies the search covered. With `companyIds`, the ones of them in the hiring set. |
| `truncated` | boolean | no | True when more companies matched the job filters than the 25,000 a hiring set holds. |
