
Count of emails on file for a domain, by type and department.
This API endpoint allows you to know how many email addresses we have for one domain or for one company.
Job email.domain.count
telipot run hunter.email.domain.count \
--input-json '{"domain":"stripe.com"}' \
--quotePrice
FreePriced· before it runs
hunter.email.domain.count
FreeYour plan
Whose account it uses
1The person asking
not needed2Your company’s Hunter plan
Selected identity for this example3Our account
not usedWhat it sends
{
"domain": "stripe.com"
}Your Hunter login is added for you. Your AI never sees it.
What it costs
Free
no charge from the provider
Preview the price first. --quote runs nothing.
For developers · run it
Shell · runs the task on the named account
telipot run hunter.email.domain.count \
--input-json '{"domain":"stripe.com"}'domain string | Domain to count. Give domain or company; domain wins when both are given. |
company string | Company name, used when the domain is unknown. At least 3 characters. |
type string · one of "personal", "generic" | Count only personal addresses, or only role-based (generic) ones. |
include_job_titles string | Any non-empty value adds data.job_titles, counts by job title. Listed in Hunter's OpenAPI, not on the docs page. |
data object | |
meta object |
Full output schema · JSONNested fields and constraints
Output JSON Schema
{
"type": "object",
"required": [
"data",
"meta"
],
"properties": {
"data": {
"type": "object",
"required": [
"total",
"personal_emails",
"generic_emails",
"department",
"seniority"
],
"properties": {
"total": {
"type": "integer"
},
"personal_emails": {
"type": "integer"
},
"generic_emails": {
"type": "integer"
},
"department": {
"type": "object",
"description": "Counts by department. Only emails with a known department are counted, so the sum can be below total.",
"additionalProperties": {
"type": "integer"
}
},
"seniority": {
"type": "object",
"description": "Counts by seniority. Only emails with a known seniority are counted, so the sum can be below total.",
"additionalProperties": {
"type": "integer"
}
},
"job_titles": {
"type": "object",
"additionalProperties": {
"type": "integer"
}
}
}
},
"meta": {
"type": "object",
"properties": {
"params": {
"type": "object"
}
}
}
}
}A real answer
No example captured yet: one is recorded when telipot catalog verify passes.

