Hunter
Authentication Type: API Key Description: Find email addresses associated with a domain, locate a specific person's email, and verify email deliverability using the Hunter.io API.
Authentication
To authenticate with Hunter, you'll need an API key from your Hunter.io account:
You'll need to provide:
- apiKey
string: Your Hunter.io API key
Security tip: Hunter provides separate API keys for different use cases. Use a dedicated key for your Cotera integration and rotate it if compromised.
Domain Search
Find all email addresses associated with a domain name. Returns contact details including names, job titles, seniority levels, departments, and social profiles. Useful for prospecting and building contact lists for a target company.
Operation Type: Query (Read)
Parameters:
- domain
string(required): Domain name to search for email addresses (e.g., "stripe.com") - type
string(nullable): Filter by email type: "personal" or "generic". Null returns both. - seniority
string(nullable): Comma-separated seniority filter: "junior", "senior", "executive" - department
string(nullable): Comma-separated department filter: "executive", "it", "finance", "management", "sales", "legal", "support", "hr", "marketing", "communication" - limit
number(nullable): Maximum number of email results to return (1-100, default 10)
Returns:
- domain
string: The searched domain - organization
string(nullable): Organization name associated with the domain - pattern
string(nullable): Most common email pattern for the domain (e.g., "{first}.{last}") - emails
array of objects: List of email addresses found- value
string: The email address - type
string: Email type: "personal" or "generic" - confidence
number: Confidence score from 0 to 100 - first_name
string(nullable): Contact's first name - last_name
string(nullable): Contact's last name - position
string(nullable): Contact's job title - seniority
string(nullable): Seniority level: "junior", "senior", or "executive" - department
string(nullable): Department the contact belongs to - linkedin
string(nullable): LinkedIn profile URL - twitter
string(nullable): Twitter handle
- value
Example Usage:
{
"domain": "stripe.com",
"department": "sales,marketing",
"seniority": "senior,executive",
"limit": 20
}
Email Finder
Find the most likely email address for a specific person given their first name, last name, and company domain. Returns the email with a confidence score and additional profile information including job title and social links.
Operation Type: Query (Read)
Parameters:
- domain
string(required): Domain name of the company (e.g., "stripe.com") - firstName
string(required): The person's first name (case-insensitive) - lastName
string(required): The person's last name (case-insensitive)
Returns:
- email
string(nullable): The most likely email address found - score
number: Confidence score from 0 to 100 - firstName
string: The person's first name - lastName
string: The person's last name - domain
string: The domain searched - position
string(nullable): The person's job title if found - company
string(nullable): The company name if found - linkedinUrl
string(nullable): LinkedIn profile URL if available - twitterHandle
string(nullable): Twitter handle if available
Example Usage:
{
"domain": "stripe.com",
"firstName": "Patrick",
"lastName": "Collison"
}
Email Verifier
Verify whether an email address is deliverable. Returns detailed verification results including deliverability status, confidence score, and technical checks such as MX records, SMTP server availability, and disposable email detection.
Operation Type: Query (Read)
Parameters:
- email
string(required): The email address to verify (e.g., "john@example.com")
Returns:
- email
string: The email address that was verified - result
string: Verification result: "deliverable", "undeliverable", "risky", or "unknown" - score
number: Confidence score from 0 to 100 - status
string: Detailed status: "valid", "invalid", "accept_all", "webmail", "disposable", "unknown" - disposable
boolean: Whether the email domain is a disposable email service - webmail
boolean: Whether the email is from a webmail provider (Gmail, Yahoo, etc.) - acceptAll
boolean: Whether the mail server accepts all email addresses - mxRecords
boolean: Whether MX records exist for the domain - smtpServer
boolean: Whether the SMTP server was found - smtpCheck
boolean: Whether the SMTP check passed - block
boolean: Whether the email is blocked
Example Usage:
{
"email": "patrick@stripe.com"
}
Common Use Cases
Sales Prospecting:
- Search for decision-makers at target companies by domain
- Filter by seniority and department to find the right contacts
- Combine Domain Search with Email Finder for targeted outreach
Lead Enrichment:
- Find email addresses for leads where you only have a name and company
- Verify existing email lists before launching outreach campaigns
- Enrich CRM records with verified email addresses
Email List Hygiene:
- Verify email addresses before sending cold outreach to improve deliverability
- Detect disposable and webmail addresses in your contact database
- Check MX records and SMTP validity to reduce bounce rates
Account-Based Marketing:
- Map out all contacts at target accounts using Domain Search
- Identify email patterns for companies to predict new contact emails
- Build department-specific contact lists for multi-threaded outreach