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

# Social profile resolution

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

Social data: records from social links (lookups), searches on a platform, a name or link to its profiles (resolutions), and the records stored for a contact, account or person. Each record read on Kenso's key costs 0.15 credits; on the workspace's own key, and for stored records, it is free. 404 unless the workspace has `social_data` on. Reads need Search view and the POSTs Search edit, as web scraping, because they can spend credits. Never a Client seat.

Prospecting data. 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/social-resolutions/openapi.json](/docs/api/social-resolutions/openapi.json).

- `POST /v1/social-resolutions` - Resolve a social link or a name (`social-resolutions.create`): [/docs/api/social-resolutions/create.md](/docs/api/social-resolutions/create.md)

## Resolve a social link or a name

`POST /v1/social-resolutions` - operationId `social-resolutions.create`

| Permission | Credits | Rate limit |
| --- | --- | --- |
| Search edit | Spends credits, price not on the rate card yet (`social_data_record`) | 120 requests a minute per API key |

With `url`: the link's canonical profile in `link`, free. With `name` (and optionally
`company`, `knownUrls` and the `contactId`, `accountId` or `personId` it is for): candidate
profiles in `candidates`, most likely first, each with a `confidence` from 0 to 1 and its
`evidence`. A first and last name runs a LinkedIn people search, charged 0.15 credits per record on Kenso's
key (free on your own key, and free again within 24 hours); its id is `searchId`. When that search did not
run (a one-word name), did not finish, or is still running, the candidates found from your links and stored
profiles still come back, with a `warning` that says why the list may be short. Errors:
`400 validation_failed` (no url or name, or a one-word name with no candidates),
`402 insufficient_credits`, `404 not_found` for a contact, account or person outside this workspace,
`422 unsupported_link`, `424 provider_key_failed`, `429 daily_limit_reached`,
`503 social_data_unavailable`. Needs Search edit, and Campaigns edit with `contactId` or Accounts edit
with `accountId` or `personId` (`403 permission_denied`).
A workspace key gets `403 forbidden`: the request records the member who asked for it, and a workspace key
is not a person.

Needs the `social_data` 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/social-resolutions/POST/v1/social-resolutions)

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

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `url` | string | no | A social link to resolve to its canonical profile. Free. |
| `name` | string | no | A person's name to find profiles for. A first and last name runs a people search; one word answers only from the links you send and stored profiles. |
| `company` | string | no | The person's company, to rank the candidates. |
| `knownUrls` | array of string | no | Links you already hold for the person, such as a website or another network's profile. |
| `contactId` | integer (int64) | no | A contact of this workspace the person is. Its stored profiles count as evidence. |
| `accountId` | integer (int64) | no | An account of this workspace the person works at. |
| `personId` | integer (int64) | no | A person of this workspace the name is. Its stored profiles count as evidence. |

### Response 200

`data` is a `SocialResolution`.

| Field | Type | Description |
| --- | --- | --- |
| `link` | SocialResolvedLink | The canonical profile a `url` names. Only on a link resolution. |
| `candidates` | array of SocialCandidate | Candidate profiles for a name, most likely first. Empty on a link resolution. |
| `searchId` | string | The people search the resolution ran (`ssr_`), when it ran one. Read its records with `social-searches.get`. |
| `creditsCharged` | number (double) | Credits the people search charged (0.15 per record on Kenso's key). A link resolution is free. |
| `warning` | SocialResolutionWarning | Why the candidates may be incomplete: the people search did not run, did not finish, or is still running. |

### Request

```bash
curl -X POST "https://api.ken.so/v1/social-resolutions" \
  -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 '{
  "url": "https://example.com",
  "name": "string",
  "company": "string",
  "knownUrls": [
    "https://example.com"
  ],
  "contactId": 812,
  "accountId": 812,
  "personId": 812
}'
```

### Example response

```json
{
  "success": true,
  "data": {
    "link": {
      "platform": "string",
      "kind": "string",
      "url": "https://example.com",
      "handle": "string",
      "externalId": "string"
    },
    "candidates": [
      {
        "url": "https://example.com",
        "platform": "string",
        "name": "string",
        "headline": "string",
        "confidence": 0.5,
        "evidence": [
          "string"
        ]
      }
    ],
    "searchId": "ssr_2bX9kq4LmR7tW3vY",
    "creditsCharged": 0.5,
    "warning": {
      "code": "string",
      "message": "string"
    }
  }
}
```

## Types

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

### SocialResolvedLink

A supported social link in its canonical form.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `platform` | string | no |  |
| `kind` | string | no | `profile`, `company`, `channel`, `post`, ... |
| `url` | string | no | The canonical link. |
| `handle` | string | no | The username, page name or slug the link names. |
| `externalId` | string | no | The platform's own id, when the link carries one. |

### SocialCandidate

One candidate profile for a name.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `url` | string | no |  |
| `platform` | string | no |  |
| `name` | string | no |  |
| `headline` | string | no |  |
| `confidence` | number (double) | no | 0 to 1: how likely the profile is this person. |
| `evidence` | array of string | no | Why the profile is a candidate, one reason per entry (a link you sent, a stored profile, a name and company match). |

### SocialResolutionWarning

Why a resolution's candidates may be incomplete.

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `code` | string | no | `validation_failed` (the name needs a first and last name, so the people search did not run), `search_running`, or the code the people search failed with. |
| `message` | string | no |  |

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