Person behavior
A person is one real human in your workspace, the same record across your campaigns and your accounts. A person carries their owner, lead status, score, phone numbers and a record of where they came from. List people, look one up by email or LinkedIn URL, or search them by account, role, lead status and tags. Create, update, merge and delete people, and upload or remove a person's photo. Put a person on an account through the account's stakeholders. Use intake to send Kenso people from your own sources, such as a web form, a workflow or your CRM: Kenso matches each one to an existing person or creates them, places them on their company's account and assigns an owner.
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. |
Return a person's behavior signals
/v1/people/{personId}/behaviorperson-behavior.get- Permission
- Accounts view
- Rate limit
- 12,000 requests a minute per API key
accounts feature on your workspace. Until it is on, calls answer 404. Needs the behavior_signals feature on your workspace. Until it is on, calls answer 404.The same body as contact-behavior.get for the person's LinkedIn profile (else their email): workspace and, with the behavior_signals_network feature, network with workspaces (other workspaces only). Address tags (email_confirmed, email_dead_end, left_company) are never on a person: read them on a contact. Absent means null. An unknown or deleted person, another workspace's, or with account scope own a person on none of the caller's accounts, is 404 not_found; a merged person is 404 with detail person_merged and mergedIntoId. Requires Accounts view and the accounts and behavior_signals features.
Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
personId | path | integer (int64) | required |
curl -X GET "https://api.ken.so/v1/people/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 CRM:AccountsPeopleAccount domainsStakeholdersMeeting notesAll resources