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

# Contact behavior

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

What Kenso learned about the person behind a contact from how they answered outreach: tags such as `cold_responder` or `prefers_linkedin`, and the counts behind them. Use them to pick a channel, a send window or whether to follow up. Kenso rebuilds the signals nightly. With the `behavior_signals_network` feature, you also get anonymous signals from outreach by other Kenso workspaces.

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-behavior/openapi.json](/docs/api/contact-behavior/openapi.json).

- `GET /v1/contacts/{contactId}/behavior` - Get a contact's behavior signals (`contact-behavior.get`): [/docs/api/contact-behavior/get.md](/docs/api/contact-behavior/get.md)

## Get a contact's behavior signals

`GET /v1/contacts/{contactId}/behavior` - operationId `contact-behavior.get`

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

Returns the behavior signals of the person behind a contact. Kenso finds the person by the contact's LinkedIn
URL, or by its email when it has no LinkedIn URL.

The `workspace` object holds what your own workspace's outreach showed: `tags`, the `signals`
behind them, the number of `touches`, and `computedAt`. The `network` object has the same fields
from outreach across every Kenso workspace, plus `workspaces`, the number of other workspaces that reached the
person. It never says which workspace, sender, campaign or reply. You get `network` only with the
`behavior_signals_network` feature on the workspace, and only when enough other workspaces reached the person.

The tags `email_confirmed`, `email_dead_end` and `left_company` are about the contact's own email
address or its company domain. Kenso omits `workspace` when your workspace has no signals for the person. It
returns an empty object when the contact has no LinkedIn URL and no email.

Errors:

- `404 not_found`: the contact is not in the workspace or was deleted.

Requires Campaigns view.

Needs the `behavior_signals` 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/contact-behavior/GET/v1/contacts/%7BcontactId%7D/behavior)

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `contactId` | path | integer (int64) | yes | The contact's id. |
| `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 `PersonBehavior`.

| Field | Type | Description |
| --- | --- | --- |
| `workspace` | PersonBehaviorScope | Signals from your own workspace's outreach. Omitted when your workspace has no signals for the person. |
| `network` | PersonBehaviorScope | Anonymous signals from outreach across every Kenso workspace, which never name a workspace, sender, campaign or reply. Omitted without the `behavior_signals_network` feature on the workspace, or when too few other workspaces reached the person. |

### Request

```bash
curl -X GET "https://api.ken.so/v1/contacts/812/behavior" \
  -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": {
    "workspace": {
      "tags": [
        "prefers_linkedin"
      ],
      "signals": [
        {
          "key": "best_channel",
          "value": "linkedin",
          "rate": 0.25,
          "touches": 8,
          "responses": 2
        }
      ],
      "touches": 8,
      "computedAt": "2026-10-14T09:41:27Z"
    },
    "network": {
      "tags": [
        "cold_responder"
      ],
      "signals": [
        {
          "key": "responsiveness",
          "rate": 0.06,
          "touches": 46,
          "responses": 2
        }
      ],
      "touches": 46,
      "workspaces": 5,
      "computedAt": "2026-10-14T09:41:27Z"
    }
  }
}
```

## Types

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

### PersonBehaviorScope

The behavior tags and counts for one scope, your workspace or the network.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `tags` | array of string | no | Behavior tags such as `cold_responder`, `prefers_linkedin` or `away_until:2026-11-18`, where a tag with a value reads `name:value`. Kenso can add new tags, so ignore any you do not recognize. |
| `signals` | array of BehaviorSignal | no | The signals behind the tags. |
| `touches` | integer (int32) | no | How many outbound touches (emails, LinkedIn actions and calls) this scope counted for the person. |
| `workspaces` | integer (int32) | no | Network scope only: how many workspaces other than yours reached the person. Omitted on the workspace scope. |
| `computedAt` | string (date-time) | no | When Kenso last built these signals, in UTC. Kenso rebuilds them nightly. |

### BehaviorSignal

One behavior signal and the counts behind it.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `key` | string | no | The signal's key, such as `best_channel`, `responsiveness` or `best_send_window`. |
| `value` | string | no | The signal's value, such as `email`, `linkedin` or `weekday_morning`, or a `YYYY-MM-DD` date for `away_until` and `revisit_after`. Omitted when the signal has no value. |
| `rate` | number (double) | no | A smoothed rate from 0 to 1. Omitted when the signal has no rate. |
| `touches` | integer (int32) | no | How many touches the signal counted. |
| `responses` | integer (int32) | no | How many of those touches got a response. |

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