Skip to Content
Prospecting data

Social profile resolution

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 data1 endpointKen-Version: 2026-11-02AuthenticationWorkspacesErrors
MarkdownOpenAPI

Headers

The endpoints on this page take these headers. Each endpoint's curl shows the ones it sends.

NameInTypeRequiredDescription
Ken-Versionheaderstring, one of: 2026-11-02, 1.1optionalThe 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-Idheaderinteger (int64)optionalThe 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.

Resolve a social link or a name

POST/v1/social-resolutionssocial-resolutions.create
Permission
Search edit
Credits
Spends credits, price not on the rate card yet (social_data_record)
Rate limit
120 requests a minute per API key
Needs the social_data feature on your workspace. Until it is on, calls answer 404.

Try it on developer.ken.so

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

Request body

application/json, optional.

FieldTypeRequiredDescription
urlstringoptionalA social link to resolve to its canonical profile. Free.
namestringoptionalA 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.
companystringoptionalThe person's company, to rank the candidates.
knownUrlsarray of stringoptionalLinks you already hold for the person, such as a website or another network's profile.
contactIdinteger (int64)optionalA contact of this workspace the person is. Its stored profiles count as evidence.
accountIdinteger (int64)optionalAn account of this workspace the person works at.
personIdinteger (int64)optionalA person of this workspace the name is. Its stored profiles count as evidence.
Request
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
}'

Response 200

data is a SocialResolution.

Show the 5 response fields and an example

The fields and an example are also on this endpoint's Markdown page.


On this page