Email Finding API
Email Finding Hunter count API
Count how many contacts a company domain has, split by personal and generic mailboxes and broken down by department and seniority. Scope a domain for $1 per 1,000 requests before paying per contact.
POST/v1/run/email_finding.hunter_count
Uptime
100.00%
30d · 3 calls
Requests
3
30d
Response
1.4s
median · 30d
Try it
Make your first request
Sample response
Free runs return only the first 3 results. Fund a key to get the full response.
{
"data": {
"departmentCounts": {
"communication": 42,
"design": 42,
"education": 42,
"executive": 42,
"finance": 42,
"health": 42,
"hr": 42,
"it": 42,
"legal": 42,
"management": 29,
"marketing": 42,
"operations": 13,
"sales": 42,
"support": 42
},
"domain": "example.com",
"genericEmails": 42,
"personalEmails": 42,
"seniorityCounts": {
"executive": 42,
"junior": 42,
"senior": 42
},
"total": 12500,
"type": "general"
},
"found": true
}Response interface
interface EmailFindingHunterCountResponse {
data: {
departmentCounts?: {
communication?: number;
design?: number;
education?: number;
executive?: number;
finance?: number;
health?: number;
hr?: number;
it?: number;
legal?: number;
management?: number;
marketing?: number;
operations?: 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;
}Full parameter and response reference - every field, type, and example for this endpoint.
Reference
Request, response, and price
Last verified 2026-09-12 · uptime and latency measured over 30dPOST /v1/run/email_finding.hunter_count
curl -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"}'| Field | Type | Example value |
|---|---|---|
| Request body | ||
| domain | string | "stripe.com"Company domain without a scheme or path, e.g. stripe.com. |
| type | enum | Count only personal mailboxes belonging to a named person, or only generic ones such as info@ and support@. |
| Response | ||
| data | object | |
| data.departmentCounts | object | Contacts per department. |
| data.departmentCounts.communication | integer | Contacts in the communication 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.operations | integer | Contacts in the operations 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. |
| Price | ||
| Price per request | USD | $0.001 |
| Price /1k req | USD | $1.00 |
FAQ
About the Email Finding Hunter count API
The AnyAPI Email Finding Hunter count API returns Email Finding hunter count data as normalized JSON from one POST call to /v1/run/email_finding.hunter_count. Count how many contacts a company domain has, split by personal and generic mailboxes and broken down by department and seniority. Scope a domain for $1 per 1,000 requests before paying per contact. AnyAPI returns one normalized schema whichever source serves it. It costs from $1 per 1,000 requests, in US dollars with no subscription and no monthly minimum. Over the last 30 days, 100.0% of Email Finding hunter count calls through AnyAPI succeeded, with a median response time of 1.4 seconds across 3 measured calls.
It costs from $1 per 1,000 requests, in US dollars with no subscription and no monthly minimum. You fund one USD wallet, each call draws it down, and a failed request costs $0.
Count how many contacts a company domain has, split by personal and generic mailboxes and broken down by department and seniority. Scope a domain for $1 per 1,000 requests before paying per contact. The response is normalized JSON with the same envelope every AnyAPI endpoint returns, so parsing a second endpoint is a change of URL and nothing else.
Over the last 30 days, 100.0% of Email Finding hunter count calls through AnyAPI succeeded, with a median response time of 1.4 seconds across 3 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.