Contact APIs
These lookups return contact data for known people. Billing depends on the API key’s active pricing plan and whether billable data is found.
Discovery (who works where) is separate — see Person search.
Find a work email
company_url (domain or URL) or linkedin_url. All four fields can be combined; LinkedIn is tried first when present. When found, the result includes the email plus returned fields such as phone, phone_type, linkedin_url, company_url, company_name, company_linkedin_url, industry, revenue, employee_count, location fields, and company_phone.
Find a phone number
/person-email: linkedin_url or (company_url + first_name + last_name). When found, the result includes phone, phone_type, company_name, employee_count, region_code, and country_code.
Reverse email lookup
Identify who owns a work email:status: "FOUND", the submitted email, person fields such as first_name, last_name, title, phone, phone_type, linkedin_url, and returned company fields such as company_url, company_name, company_linkedin_url, company_phone, industry, revenue, employee_count, city, region_code, and country_code. Not-found responses return status: "NOT_FOUND".
Returns normalized person and company fields when a match is found.
LinkedIn profile
Resolve LinkedIn URL first
When you have a LinkedIn profile URL, or first name, last name, and company website:first_name, last_name, and company_url when you do not already have a LinkedIn profile URL.
Then pass the URL to /person-linkedin.
Typical chains
Bulk contact workflows
For many contacts, do not use/research in a loop. Instead:
- Person search to discover candidates
person-email/person-phoneper selected person- Or run columns in Clay/n8n with Huntr HTTP steps
/research rejects multi-entity enrichment with 422 BULK_ENRICHMENT_REQUIRED.