Back to Email finder
Hunter·Email finder

Search people across companies

/multi-domain-searchsync$0 / call

One query across every company matching your filters: returns one row per matching person with title, department, seniority, decision-maker flag and verification status, but the email itself masked behind a reveal_handle. Free. Pass the handles you want to /multi-domain-search/reveal to unlock the addresses. At least one filter is required.

Input
  • company_namestring

    Company name filter, comma-separated for several.

  • locationstring

    Company location, e.g. "US" or "US,GB".

  • industrystring

    LinkedIn industry codes (integers 0–32767), comma-separated, e.g. "43" for Financial Services, "4" for Software Development. Names are rejected.

  • headcountstring

    Headcount ranges, comma-separated, e.g. "51-200,201-500".

  • company_typestring

    Company type filter, e.g. "privately held".

  • founded_yearstring

    Founding year or range, e.g. "2015" or "2015-2020".

  • technologystring

    Technologies the company uses, comma-separated, e.g. "salesforce".

  • departmentstring

    Person's department: executive, it, finance, management, sales, legal, support, hr, marketing, communication, education, design, health, operations. Comma-separated for several.

  • senioritystring

    junior, senior or executive; comma-separated for several.

  • typestring

    Personal (named) or generic (info@) addresses.

    personal, generic

  • decision_makerboolean

    Only people Hunter flags as decision makers.

  • verification_statusstring

    Only addresses with this verification status, e.g. "valid".

  • required_fieldstring

    Only rows that have every listed field: full_name, position, phone_number (comma-separated).

  • min_confidenceinteger

    Minimum confidence score for a row.

  • limitinteger

    Rows per page (default and max 100).

  • search_afterstring

    Cursor from the previous page's meta.next_search_after.

  • per_domainboolean

    Include a per-domain breakdown of matching counts in meta.

Run it

curl -s https://sooma.dev/v1/run \ -H "Authorization: Bearer $SOOMA_API_KEY" \ -H "Content-Type: application/json" \ -d '{"provider":"hunterio","endpoint":"/multi-domain-search","input":{"location":"US","department":"executive","seniority":"executive","limit":5}}'

Or ask your agent: it will call inspect for this schema and run it over MCP.