canonical: https://jentic.com/apis/hunter.io/hunter # Hunter API Jentic publishes the only available OpenAPI specification for Hunter API, keeping it validated and agent-ready. Discover professional email addresses for any company domain, generate the most likely email for a specific person given their name and company, and verify email deliverability before sending. The API exposes 4 endpoints covering domain-wide email search, individual email generation, deliverability verification, and account usage tracking. ## For AI agents Find professional email addresses by company domain, generate likely emails from name and domain, and verify deliverability. Covers domain search, email finder, and email verification. ## Scope Does not handle email sending, CRM management, or person profile enrichment beyond email - use for email discovery and verification only. ## Capabilities - Discover all professional email addresses associated with a company domain - Generate the most likely email address for a specific person given their first name, last name, and company domain - Verify whether an email address is deliverable before sending outreach - Retrieve account usage information including remaining request credits - Paginate through large result sets with limit and offset parameters for domain searches ## Use cases ### AI Agent Email Discovery via Jentic AI agents building outreach campaigns can find professional email addresses through Jentic by searching for email discovery operations. The agent passes a company domain and receives all known email addresses with their confidence scores, enabling automated prospect list building without manual research. Example prompt: Search Jentic for 'find email addresses by domain', load the Hunter /domain-search schema, and query with domain='intercom.com' to retrieve all associated email addresses ### Personalised Sales Outreach Email Generation Sales reps and SDR automation tools generate the most likely email address for a specific prospect by providing their first name, last name, and company domain. Hunter's email pattern recognition returns the generated email with a confidence score, eliminating guesswork in cold outreach. Example prompt: GET /email-finder with domain='hubspot.com', first_name='Brian', last_name='Halligan' to generate the most likely professional email address ### Email Verification Before Campaign Send Marketing and sales platforms verify email deliverability before sending campaigns to protect sender reputation and reduce bounce rates. The email verifier endpoint checks MX records, SMTP responses, and pattern matching to classify addresses as deliverable, risky, or undeliverable. Example prompt: GET /email-verifier with email='john@example.com' to check deliverability status and determine whether to include in the outreach campaign ### Domain-Wide Contact Discovery for Account Research Account-based sales teams research target companies by pulling all discoverable email addresses for a domain. The domain search endpoint returns up to 100 addresses per page with pagination support, along with associated names and departments, giving teams a complete contact map for account penetration. Example prompt: GET /domain-search with domain='salesforce.com' and limit=50 to retrieve the first 50 email addresses and associated names for that company ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /domain-search | Find all email addresses for a company domain | | GET | /email-finder | Generate probable email from name and domain | | GET | /email-verifier | Verify email deliverability | | GET | /account | Retrieve account information and usage | ## Key resources - **Domain Search** — Discover all email addresses associated with a company domain with pagination - **Email Finder** — Generate the most likely email for a person given first name, last name, and domain - **Email Verifier** — Check whether an email address is deliverable, risky, or invalid - **Account** — View account details and remaining API request credits ## Why Jentic - **Setup:** Wiring the Hunter API by hand means holding an API key, targeting api.hunter.io/v2, and passing the key as a query parameter on every domain search and verification call yourself. Through Jentic you install once, import the Hunter API from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** This API runs discovery and verification through fixed endpoints with the domain or email in the request parameters (/domain-search, /email-verifier), so limit the agent to the operations it needs, such as finding an email or verifying one. You choose the operations it may call, so reading the account endpoint is not included unless you add it. - **Credential handling:** Your Hunter API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'find professional emails at a company' or 'verify an email address', and Jentic returns the matching Hunter operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **FullContact Enrich API** — Enriches discovered emails with full person profiles including demographics and employment data - **People Data Labs API** — Provides email discovery as part of a broader person enrichment and search platform with 3+ billion records - **Clearbit Logo API** — Adds company logos to outreach materials alongside Hunter-discovered email contacts ## FAQ ### Why is there no official OpenAPI spec for Hunter API? Hunter does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Hunter API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Hunter API use? The Hunter API uses an API key passed as a query parameter named 'api_key' on every request. Through Jentic, this key is stored encrypted in the credential vault and appended to requests automatically - agents never handle the raw key. ### Can I find all email addresses at a company with the Hunter API? Yes. The /domain-search endpoint accepts a domain parameter and returns all email addresses found for that company. Use the limit parameter (max 100) and offset for pagination to retrieve large result sets. ### How does the email finder generate an email address? The /email-finder endpoint takes a domain, first_name, and last_name, then applies pattern recognition across known email formats for that domain. It returns the most likely email address along with a confidence score indicating match probability. ### How do I discover emails through Jentic? Install the SDK with pip install jentic and search for 'find email addresses at a company'. Jentic returns the Hunter /domain-search operation schema. Pass the target domain and Jentic handles auth (appending the api_key parameter) and returns the list of discovered emails. ### What does the email verifier check? The /email-verifier endpoint checks MX records, SMTP server responses, and known email patterns for the domain. It returns a status indicating whether the address is deliverable, risky (accept-all domain), or undeliverable, helping you clean lists before sending campaigns. ### Can I limit what my agent is allowed to do with the Hunter API? Yes. Because you run Jentic One yourself, you decide which of Hunter's fixed operations the agent may call, such as finding emails with /email-finder, searching a domain with /domain-search, or checking deliverability with /email-verifier. You can restrict it to only the endpoints it needs, so if the agent should just verify addresses it never touches domain search or the /account usage endpoint. Your own rules also govern the stored API key, which is injected at execution time rather than exposed to the agent.