Contact behavior
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.
Headers
The endpoints on this page take these headers. Each endpoint's curl shows the ones it sends.
| Name | In | Type | Required | Description |
|---|---|---|---|---|
Ken-Version | header | string, one of: 2026-11-02, 1.1 | optional | 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 date that is not a version answers 400 unsupported_version; any other value that is not a version is treated as legacy. |
X-Ken-Workspace-Id | header | integer (int64) | optional | 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. |
Get a contact's behavior signals
/v1/contacts/{contactId}/behaviorcontact-behavior.get- Permission
- Campaigns view
- Rate limit
- 12,000 requests a minute per API key
behavior_signals feature on your workspace. Until it is on, calls answer 404.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.
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
contactId | path | integer (int64) | required | The contact's id. |
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"Response 200
data is a PersonBehavior.
Show the 2 response fields and an example
The fields and an example are also on this endpoint's Markdown page.
More in Contacts and companies:ContactsContact importsContact exportsTagsBlocklistBlocklist rulesContact fieldsCompaniesCompany dataAll resources