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.
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. |
More in Prospecting data:People and company searchSaved searchesSaved listsSaved list membersSaved list invitesEmail finderFunding roundsJob postingsJob post searchLinkedIn job searchLinkedIn jobsWeb scrapingSocial data lookupsSocial data searchesSocial data recordsSignalsAll resources
Resolve a social link or a name
/v1/social-resolutionssocial-resolutions.createsocial_data_record)social_datafeature on your workspace. Until it is on, calls answer 404.Try it on developer.ken.so
With
url: the link's canonical profile inlink, free. Withname(and optionallycompany,knownUrlsand thecontactId,accountIdorpersonIdit is for): candidate profiles incandidates, most likely first, each with aconfidencefrom 0 to 1 and itsevidence. 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 issearchId. 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 awarningthat 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_foundfor 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 withcontactIdor Accounts edit withaccountIdorpersonId(403 permission_denied).Request body
application/json, optional.urlnamecompanyknownUrlscontactIdaccountIdpersonIdResponse 200
datais aSocialResolution.Show the 5 response fields and an example
The fields and an example are also on this endpoint's Markdown page.