Skip to main content
POST /person-search finds people from Huntr’s people index using structured filters — job titles, employers, skills, schools, and location.

​
Preview match count (free)

curl --request POST \
  --url https://api.tryhuntr.com/person-search-count \
  --header 'content-type: application/json' \
  --header "x-api-key: ${HUNTR_API_KEY}" \
  --data '{
    "query": {
      "currentJobTitle": { "include": ["CTO", "Chief Technology Officer"] },
      "currentCompanyWebsite": { "include": ["stripe.com"] }
    }
  }'

​
Search people

curl --request POST \
  --url https://api.tryhuntr.com/person-search \
  --header 'content-type: application/json' \
  --header "x-api-key: ${HUNTR_API_KEY}" \
  --data '{
    "query": {
      "currentJobTitle": { "include": ["VP Engineering", "Head of Engineering"] },
      "currentCompanyWebsite": { "include": ["linear.app"] },
      "location": { "include": ["US"] }
    },
    "pagination": { "size": 50 }
  }'

​
Filter tips

​
Scope to a company with currentCompanyWebsite

This is the most reliable way to mean “people at company X”: 
{ "currentCompanyWebsite": { "include": ["stripe.com"] } }
Do not use linkedin.com as a company website — that matches broadly, not one employer.

​
Job titles use contains match

"CTO" matches “Group CTO”, “Former CTO”, etc. List variants explicitly: 
{ "currentJobTitle": { "include": ["CTO", "Chief Technology Officer", "Chief Technical Officer"] } }

​
Past vs current roles

FilterMatches
currentJobTitle / currentCompanyWebsitePresent role
pastJobTitle / pastCompanyNamePrevious roles — alumni searches
keyword scans the full profile when no dedicated filter fits. Prefer explicit title and employer filters when you can.

​
Pagination

Same pattern as company search:
  • One page per request (max 200)
  • Loop with pagination.token
  • Keep the same query between pages

​
After you have people

Next stepEndpoint
Work emailPOST /person-email
Full LinkedIn profilePOST /person-linkedin
Narrative buyer briefPOST /research tier deep
See Contact enrichment.

​
Pricing

Per person returned. Count endpoint is free. See GET /pricing.

​
Next step