API para Email Finding: Contagem Hunter
Conte quantos contatos um domínio de empresa tem, separados em caixas pessoais e genéricas e divididos por departamento e senioridade. Avalie um domínio por US$ 1 a cada 1.000 requisições antes de pagar por contato.
Preços
Um preço, em dólares
Teste
Faça sua primeira requisição
{
"data": {
"departmentCounts": {
"administrative": 42,
"communication": 42,
"consulting": 42,
"design": 42,
"education": 42,
"executive": 42,
"finance": 42,
"health": 42,
"hr": 42,
"it": 42,
"legal": 42,
"management": 29,
"marketing": 42,
"operation": 13,
"operations": 13,
"procurement": 42,
"product": 42,
"research": 42,
"sales": 42,
"support": 42
},
"domain": "example.com",
"genericEmails": 42,
"personalEmails": 42,
"seniorityCounts": {
"executive": 42,
"junior": 42,
"senior": 42
},
"total": 12500,
"type": "general"
},
"found": true,
"reason": "not_found"
}interface EmailFindingHunterCountResponse {
data: {
departmentCounts?: {
administrative?: number;
communication?: number;
consulting?: number;
design?: number;
education?: number;
executive?: number;
finance?: number;
health?: number;
hr?: number;
it?: number;
legal?: number;
management?: number;
marketing?: number;
operation?: number;
operations?: number;
procurement?: number;
product?: number;
research?: number;
sales?: number;
support?: number;
};
domain: string;
genericEmails?: number;
personalEmails?: number;
seniorityCounts?: {
executive?: number;
junior?: number;
senior?: number;
};
total: number;
type?: string;
} | null;
found: boolean;
reason?: "not_found";
}Referência completa de parâmetros e resposta - todos os campos, tipos e exemplos deste endpoint.
Referência
Requisição, resposta e preço
Última verificação em 2026-09-29 · disponibilidade e latência medidas em 30dcurl -X POST https://api.getanyapi.com/v1/run/email_finding.hunter_count \
-H "Authorization: Bearer $ANYAPI_KEY" \
-H "Content-Type: application/json" \
-d '{"domain":"stripe.com"}'| Campo | Tipo | Valor de exemplo |
|---|---|---|
| Corpo da requisição | ||
| domain | string | "stripe.com"Domínio da empresa sem protocolo nem caminho, ex.: stripe.com. |
| type | enum | Conta apenas caixas pessoais de uma pessoa identificada, ou apenas genéricas como info@ e support@. |
| Resposta | ||
| data | object | |
| data.departmentCounts | object | Contacts per department. |
| data.departmentCounts.administrative | integer | Contacts in the administrative department. |
| data.departmentCounts.communication | integer | Contacts in the communication department. |
| data.departmentCounts.consulting | integer | Contacts in the consulting department. |
| data.departmentCounts.design | integer | Contacts in the design department. |
| data.departmentCounts.education | integer | Contacts in the education department. |
| data.departmentCounts.executive | integer | Contacts in the executive department. |
| data.departmentCounts.finance | integer | Contacts in the finance department. |
| data.departmentCounts.health | integer | Contacts in the health department. |
| data.departmentCounts.hr | integer | Contacts in the HR department. |
| data.departmentCounts.it | integer | Contacts in the IT department. |
| data.departmentCounts.legal | integer | Contacts in the legal department. |
| data.departmentCounts.management | integer | Contacts in the management department. |
| data.departmentCounts.marketing | integer | Contacts in the marketing department. |
| data.departmentCounts.operation | integer | Contacts Hunter files under its separate operation department. |
| data.departmentCounts.operations | integer | Contacts in the operations department. |
| data.departmentCounts.procurement | integer | Contacts in the procurement department. |
| data.departmentCounts.product | integer | Contacts in the product department. |
| data.departmentCounts.research | integer | Contacts in the research department. |
| data.departmentCounts.sales | integer | Contacts in the sales department. |
| data.departmentCounts.support | integer | Contacts in the support department. |
| data.domain | string | The company domain the counts describe. |
| data.genericEmails | integer | Contacts that are a shared inbox such as info@ or support@. |
| data.personalEmails | integer | Contacts that are a named person's mailbox. |
| data.seniorityCounts | object | Contacts per seniority level. |
| data.seniorityCounts.executive | integer | Contacts at executive level. |
| data.seniorityCounts.junior | integer | Contacts at junior level. |
| data.seniorityCounts.senior | integer | Contacts at senior level. |
| data.total | integer | Contacts known for the domain. |
| data.type | string | Mailbox type the counts are limited to when the request filtered by type: personal or generic. Absent when the counts cover both. |
| found | boolean | False when the domain has no counted contacts. |
| reason | "not_found" | Present only when `found` is false, and says why there is no result. `not_found`: the source states the target does not exist, or returned nothing for it. A `found: false` answer is a successful call, not an error, and `costUsd` is what it actually cost. |
| Preço | ||
| Preço por requisição | USD | US$ 0,001 |
| Preço /mil req. | USD | US$ 1,00 |
Dúvidas frequentes
Sobre o endpoint Contagem Hunter da API para Email Finding
O endpoint Contagem Hunter da AnyAPI para Email Finding retorna dados de Email Finding em JSON normalizado com uma chamada POST para /v1/run/email_finding.hunter_count. Conte quantos contatos um domínio de empresa tem, separados em caixas pessoais e genéricas e divididos por departamento e senioridade. Avalie um domínio por US$ 1 a cada 1.000 requisições antes de pagar por contato. A AnyAPI retorna um schema normalizado, seja qual for a fonte que atende. Custa a partir de US$ 1 por mil requisições, em dólares, sem assinatura e sem mínimo mensal. Nos últimos 30 dias, 100,0% das chamadas ao endpoint Contagem Hunter da API para Email Finding feitas pela AnyAPI tiveram sucesso, com tempo de resposta mediano de 1,4 segundos, em 3 chamadas medidas.