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

# Contact fields

> **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.

The contact fields available for columns, CSV export and CSV import.

Contacts and companies. 1 endpoint under `https://api.ken.so`. Every request sends `Authorization: Bearer <your API key>` and `Ken-Version: 2026-11-02`: see [Authentication](/docs/authentication.md), [Workspaces](/docs/workspaces.md) and [Errors](/docs/errors.md). OpenAPI for this resource only: [/docs/api/contact-fields/openapi.json](/docs/api/contact-fields/openapi.json).

- `GET /v1/contact-fields` - List contact fields (`contact-fields.list`): [/docs/api/contact-fields/list.md](/docs/api/contact-fields/list.md)

## List contact fields

`GET /v1/contact-fields` - operationId `contact-fields.list`

| Permission | Rate limit |
| --- | --- |
| Campaigns view | 12,000 requests a minute per API key |

Lists every contact field in a fixed order, with its key, label, value type and usages. A field's
`usages` says where it works: `list` (a column of the contact list), `export` (a column of a contact
export) and `import` (a target for a CSV column in a contact import).

A few fields appear only when the workspace has a feature. `securityGateway` and `mailboxProvider` need
the `security_gateways` feature on the workspace. `customImage` needs the `campaign_images` feature,
and `customVideo` needs both the `campaign_videos` and `campaign_images` features.

Errors:

- `400 validation_failed`: `limit` is not from 1 to 200, or `cursor` is invalid or points past the last page.

Requires Campaigns view.

[Try it on developer.ken.so](https://developer.ken.so/reference/#kenso-api/tag/contact-fields/GET/v1/contact-fields)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `limit` | query | integer (int32) | no | Fields per page, from 1 to 200. Default 50. |
| `cursor` | query | string | no | The `nextCursor` of the previous page. Omitted starts at the first page. |
| `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 list of `ContactField`. Each item has these fields. The response also carries `pagination`.

| Field | Type | Description |
| --- | --- | --- |
| `key` | string | The field's key in camelCase, such as `firstName`, `companyDomain` or `qualityScore`. |
| `label` | string | A readable name for the field. It is the key when the field has no label of its own. |
| `type` | string | The value type: `string`, `int`, `short`, `float`, `bool`, `date_time`, `email_validity` or `phone_number_validity`. |
| `usages` | array of string | Where the field works, in this order: `list` (a column of the contact list), `export` (a column of a contact export) and `import` (a target for a CSV column). Every field has at least one. |
| `isMultiSelect` | boolean | True when an import can map more than one CSV column to this field, as with `email`. |
| `isDefaultExport` | boolean | True when this field is one of the default export columns, which a contact export of kind `contacts`, `clicked` or `advanced` writes when you send no `fields`. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/contact-fields?limit=50" \
  -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": [
    {
      "key": "firstName",
      "label": "string",
      "type": "string",
      "usages": [
        "string"
      ],
      "isMultiSelect": true,
      "isDefaultExport": true
    }
  ],
  "pagination": {
    "nextCursor": "eyJpZCI6ODE1fQ",
    "hasMore": true,
    "total": 1,
    "totalCount": 1,
    "isTotalCapped": true
  }
}
```

All resources: [/docs.md](/docs.md).
