Skip to main content
POST
This endpoint is synchronous. It costs 0.1 credit per profile found, and nothing when no profile matches.There is no request_id and nothing to poll: the profile comes back in the same response. Expect a couple of seconds.
This endpoint returns profile data only. It never returns an email address or a phone number. For contact data, use Enrich leads.

Identifying the lead

There are two ways in, and they are not equivalent.

By LinkedIn URL

Send linkedin_url alone. This is the most reliable form and the one to prefer whenever you have the URL.

By name and company

Send first_name, last_name and company_domain together. All three are required.
company_domain is required in the second form, a company name is not enough. Sending first_name + last_name + company without company_domain is rejected with 422. You can send company in addition to company_domain, but never instead of it.
When linkedin_url is present the other attributes are ignored.

Authentication

The key goes either in the X-API-Key header, like every other endpoint, or as an api_key attribute in the body. The header is the recommended form: it keeps the key out of your request payloads and out of your logs.

What you get back

25 fields describing the person and their current company. Unlike the enrichment and Lead Finder payloads, there are no extra always-null legacy keys: what you see is the whole response. A few fields deserve a note: Values are capitalised on the way out, which is why a job title comes back as Development solutions sr. principal engineer rather than in its original casing.

Authorizations

X-API-Key
string
header
required

Body

application/json

Lead to look up

Identify the lead in one of two ways:

  • By LinkedIn URL: send linkedin_url alone. This is the most reliable form.
  • By name and company: send first_name, last_name and company_domain.

linkedin_url takes precedence: when it is present the other attributes are ignored.

linkedin_url
string

Public LinkedIn profile URL of the contact. Sufficient on its own.

Example:

"https://www.linkedin.com/in/veronick-martinuzzi-a4533373"

first_name
string

First name. Required when you do not send linkedin_url.

Example:

"Veronick"

last_name
string

Last name. Required when you do not send linkedin_url.

Example:

"Martinuzzi"

company_domain
string

Company domain. Required when you do not send linkedin_url.

Example:

"hondaresearch.com"

company
string

Company name. Complements company_domain, it cannot replace it.

Example:

"Honda R&D Americas"

api_key
string

Your API key. Only needed if you do not send the X-API-Key header.

Response

Profile found.

success
boolean
Example:

true

data
object

The lead profile. These are all the keys returned: unlike the enrichment and Lead Finder payloads there are no extra always-null legacy keys.