Hunter — Domain Search (POST)
hunter_post_v2_domain_searchUse POST for nested location filters. The body can be JSON or URL-encoded form data. Boolean filters in this execution profile accept canonical true/false only; other provider aliases remain in the original documentation. Uses the caller's OpenAny gateway credentials. Charges and authorization are determined by the gateway.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | Get only personal or generic email addresses. | |
| limit | No | Specifies the max number of email addresses to return. The default is 10. | |
| domain | No | Domain name from which you want to find the email addresses. For example, "stripe.com". | |
| offset | No | Specifies the number of email addresses to skip. The default is 0. | |
| company | No | The company name from which you want to find the email addresses. For example, "stripe". Note that you'll get better results by supplying the domain name as we won't have to find it. If you send a request with both the domain and the company name, we'll use the domain name. It doesn't need to be in lowercase. | |
| location | No | Get only email addresses for people with the selected location(s). You can specify lists of locations in the include field to select on and/or in the exclude field to exclude. Each location can have either a continent or business_region or country, state and/or city. continent can be one of the following: Africa, Antarctica, Asia, Europe, North America, Oceania or South America business_region can be one of the following: AMER, EMEA, APAC or LATAM country must contain a valid ISO 3166-1 alpha-2 country code, for example "US" for the United States. state must contain a valid US state code, for example "CA" for California. You can only use this field when the country is set to "US". city must contain a city name, for example "San Francisco". Please note that when a city is provided, a country must also be specified: { "location": { "include": [ { "city": "Paris", "country": "FR" } ] } } Please note that using this filter requires to use a POST request. | |
| seniority | No | Comma-separated seniority values from Hunter's live position taxonomy (not a frozen enum). Unknown values are ignored; a list with no remaining valid values returns 400 (`invalid_seniority`). | |
| department | No | Comma-separated department values from Hunter's live position taxonomy (not a frozen enum). `~` matches people with no department. Unknown values are ignored; a list with no remaining valid values returns 400 (`invalid_department`). | |
| job_titles | No | Get only email addresses for people that have the selected job title(s). Several job titles can be selected (comma-delimited). Common executive titles match their well-known equivalents, so you don’t have to list every spelling. For example, Chief Technology Officer, Chief Technical Officer, and CTO match each other, and VP matches Vice President (covers CEO, CTO, CFO, COO, CMO, CIO, CISO, CHRO, VP, and HR). Titles match on whole words and common word forms: CTO matches “Co-founder & CTO” but not “Director”, and engineer also finds “Engineering” and “Engineers”. Use job_titles for a specific role wording. To target a whole tier of people (for example, all the leaders at a company), use the seniority, department, and decision_maker filters. | |
| provenance | No | Keep only addresses with this provenance: found, inferred. Replaces `source_type`; when both are sent they must agree, otherwise the request returns 400 (`invalid_provenance`). | |
| saved_leads | No | ||
| source_type | No | Deprecated, use `provenance`. "generated" is the old name for "inferred". | |
| aggregations | No | Set to true or false to include a breakdown of the domain's email addresses in meta.aggregations: the number of personal email addresses per department, the number of decision makers, and the split between personal and generic addresses. The counts reflect the filters applied to the search. Omitted by default. | |
| decision_maker | No | A boolean filter. Query-string clients may use the documented case-insensitive aliases. This execution profile accepts canonical true/false only; see the full native schema for other boolean aliases. | |
| required_field | No | Get only email addresses for people that have the selected field(s). The possible values are full_name, position and phone_number. Several fields can be selected (comma-delimited). | |
| verification_status | No | Get only email addresses that have the selected verification status(es). The possible values are valid, accept_all and unknown. Several statuses can be selected (comma-delimited). |