GuideAPI referenceSDKs
Dashboard
Core Concepts

Find People

Build people lists by combining contact fields with the current employer snapshot on each contact record.

When to use it

Use POST /v2/search/people when you need a list of contacts by role, seniority, geography, or current employer. The endpoint searches the contacts index and can return company details such as company.name, company.domain, company.industry, and company.about with each person.

How it works

  • Send at least one supported people or company filter.
  • Use exact normalized values for seniority, functions, country codes, continents, regions, and company type.
  • Use max_results from 1 to 100. Pagination uses the opaque cursor from the previous response.
  • The nested company object is an employer snapshot stored on the person record, not a standalone company enrichment response.

Working filters

Company filters inside Find People

Request fieldNormalized formatResponse fieldExamples
company.domainBare employer hostname, or include/exclude arrays.company.domainopenai.com, google.com
company.nameEmployer name terms or phrases, or include/exclude arrays.company.nameOpenAI, Microsoft
company.keywordsAlias-style employer name keyword filter.company.nameopenai, salesforce
company.country_codeUppercase ISO 3166-1 alpha-2 country code.company country snapshotUS, GB, IN
company.continentDataset continent value.company continent snapshotNorth America, Europe
company.typeExact source company type label.company.typePrivately Held, Public Company

People filters

Request fieldNormalized formatResponse fieldExamples
people.job_titleCurrent title terms or phrases, or include/exclude arrays.job_titleCEO, VP Marketing, Head of Growth
people.titleAlias for people.job_title.job_titleFounder, Product Manager
people.job_functionExact source department or function label.job_functionGeneral Business & Management
people.departmentAlias for people.job_function.job_functionSales & Business Development
people.job_levelExact source seniority label.job_levelStaff, Manager, Director, VP, C-Team, Other
people.seniorityAlias for people.job_level.job_levelC-Team, VP
people.country_codeUppercase ISO 3166-1 alpha-2 country code.location.country_codeUS, GB, IN
people.continentDataset continent value.location.continentNorth America, Asia
people.sales_regionDataset sales region code.Filter-onlyNORAM, LATAM, EMEA, APAC
people.min_connections_countPositive integer lower bound.connections_count500

Accepted values

Use these canonical exact values in list filters. Title and domain filters can use include/exclude arrays.

FieldAccepted values
people.job_levelC-Team, Director, Manager, Other, Staff, VP
people.sales_regionAPAC, EMEA, LATAM, NORAM
company.typeEducational, Educational Institution, Government Agency, Nonprofit, Partnership, Privately Held, Public Company, Self-Employed, Self-Owned, Sole Proprietorship
country_codeUppercase two-letter country codes from Geography.

Response shape

Each result includes normalized person fields and, when present on the contact record, a compact employer object.

FieldTypeDescription
first_namestring | nullGiven name.
last_namestring | nullFamily name when present in the source data.
full_namestring | nullPerson display name.
headlinestring | nullLinkedIn headline.
job_titlestring | nullCurrent title.
job_functionstring | nullDepartment or functional area.
job_levelstring | nullSeniority level.
linkedin_urlstring | nullCanonical LinkedIn profile URL.
connections_countinteger | nullLinkedIn connection count when available.
profile_picture_urlstring | nullProfile image URL when available.
location.citystring | nullPerson city.
location.state_codestring | nullPerson state or subdivision code.
location.country_codestring | nullPerson country code.
location.continentstring | nullSource continent value.
emailstring | nullWork email when available.
phonestring | nullMobile or direct phone when available.
companyobject | nullNested normalized company object using the company fields above.

Employer snapshot fields

FieldTypeDescription
company.linkedin_urlstring | nullCurrent employer LinkedIn company URL.
company.namestring | nullCurrent employer display name.
company.headlinestring | nullCurrent employer headline when available.
company.aboutstring | nullCurrent employer description when available.
company.industrystring | nullCurrent employer industry label returned from the contact index.
company.typestring | nullCurrent employer entity type.
company.sizestring | number | nullCurrent employer size bucket when available.
company.employees_on_linkedininteger | nullEmployee count represented on LinkedIn.
company.founded_yearinteger | nullYear the employer was founded.
company.domainstring | nullCurrent employer primary domain.
company.websitestring | nullCurrent employer website URL.
company.logostring | nullCurrent employer logo image URL.

Examples

Role and domain

curl -X POST "https://moltsetz.com/v2/search/people" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "company": {
    "domain": {
      "include": [
        "openai.com"
      ]
    }
  },
  "people": {
    "job_title": {
      "include": [
        "CEO"
      ],
      "exclude": [
        "Assistant"
      ]
    }
  },
  "max_results": 10
}'

Seniority, function, and geography

curl -X POST "https://moltsetz.com/v2/search/people" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "people": {
    "job_level": [
      "VP",
      "Director"
    ],
    "job_function": [
      "Sales & Business Development"
    ],
    "country_code": [
      "US"
    ],
    "sales_region": [
      "NORAM"
    ]
  },
  "max_results": 25
}'

Employer type

curl -X POST "https://moltsetz.com/v2/search/people" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "company": {
    "type": [
      "Privately Held"
    ],
    "country_code": [
      "US"
    ]
  },
  "people": {
    "job_title": {
      "include": [
        "Head of Growth"
      ]
    }
  },
  "max_results": 10
}'

Not yet supported

These fields exist in the wider data model or company-focused docs, but should not be used as Find People filters until the API maps them in the contacts query.

  • company.industry, company.employee_range, and company.sales_region as People Search filters.
  • company.hq.*, revenue, funding, NAICS, SIC, traffic, ad spend, technologies, and open roles as People Search filters.
  • people.education, people.skills, people.certifications, and people.languages as People Search filters.
moltsetz - B2B data infrastructure