Skip to main content
Person enrichment endpoints turn a name + company (or LinkedIn URL) into contact data for outbound workflows.

​
Endpoints

EndpointPurpose
POST /person-emailFind work email address
POST /person-linkedinFull profile from LinkedIn URL
POST /person-linkedin-urlResolve profile URL from name + company

​
Find a work email

curl --request POST \
  --url https://api.tryhuntr.com/person-email \
  --header 'content-type: application/json' \
  --header "x-api-key: ${HUNTR_API_KEY}" \
  --data '{
    "first_name": "Patrick",
    "last_name": "Collison",
    "company_domain": "stripe.com"
  }'
Provide the most specific company identifier you have (company_domain is preferred over company name).

​
LinkedIn profile

curl --request POST \
  --url https://api.tryhuntr.com/person-linkedin \
  --header 'content-type: application/json' \
  --header "x-api-key: ${HUNTR_API_KEY}" \
  --data '{ "linkedin_url": "https://www.linkedin.com/in/patrickc" }'

​
Resolve LinkedIn URL first

When you only have name and employer: 
curl --request POST \
  --url https://api.tryhuntr.com/person-linkedin-url \
  --header 'content-type: application/json' \
  --header "x-api-key: ${HUNTR_API_KEY}" \
  --data '{
    "first_name": "Dylan",
    "last_name": "Field",
    "company_domain": "figma.com"
  }'
Then pass the URL to /person-linkedin.

​
Bulk contact workflows

For many contacts, do not use /research in a loop. Instead:
  1. Person search to discover candidates
  2. person-email per selected person
  3. Or run columns in Clay/n8n with Huntr HTTP steps
/research rejects multi-entity enrichment with 422 BULK_ENRICHMENT_REQUIRED.

​
Buyer research vs raw email

NeedUse
Just the email for sequencing/person-email
Role, priorities, angles, risks/research tier deep on one person

​
Next step