Enrich a lead profile
Look up a single person and get their profile and current company.
request_id and nothing to poll: the profile comes back in the same response. Expect
a couple of seconds.Identifying the lead
There are two ways in, and they are not equivalent.By LinkedIn URL
linkedin_url alone. This is the most reliable form and the one to prefer whenever you have
the URL.By name and company
first_name, last_name and company_domain together. All three are required.linkedin_url is present the other attributes are ignored.
Authentication
The key goes either in theX-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:Development solutions sr. principal engineer rather than in its original casing.Authorizations
Body
Lead to look up
Identify the lead in one of two ways:
- By LinkedIn URL: send
linkedin_urlalone. This is the most reliable form. - By name and company: send
first_name,last_nameandcompany_domain.
linkedin_url takes precedence: when it is present the other attributes are ignored.
Public LinkedIn profile URL of the contact. Sufficient on its own.
"https://www.linkedin.com/in/veronick-martinuzzi-a4533373"
First name. Required when you do not send linkedin_url.
"Veronick"
Last name. Required when you do not send linkedin_url.
"Martinuzzi"
Company domain. Required when you do not send linkedin_url.
"hondaresearch.com"
Company name. Complements company_domain, it cannot replace it.
"Honda R&D Americas"
Your API key. Only needed if you do not send the X-API-Key header.