Hunter
platform:HunterExplore published endpoints and request contracts for Hunter.
- Endpoints
- 15In this collection
- Providers
- 1Unique providers
- Requests
- —Loading...
- Success rate
- —Loading...
- Response P50
- —Loading...
Available APIs
Hunter — Domain Search (POST)
Use POST for nested location filters. The body can be JSON or URL-encoded form data. Boolean filters in this execution profile accept canonical true/false only; other provider aliases remain in the original documentation.
Hunter — Discover People (GET)
Discover people matching filters This GET execution profile accepts only natural-language query, limit and offset. Use POST for structured filters.
Hunter — Discover (POST)
Find companies matching a structured filter set. This operation is free.
Hunter — Multi-Domain Search (POST)
Search professional email addresses across many companies at once using a structured filter set. Returns masked rows — no email address or phone number; use the reveal endpoint to unmask. This masked survey operation is free. At least one filter is required. Filters may be sent in the request body (JSON or form-encoded) or as query-string parameters; the body is therefore optional. Boolean filters in this execution profile accept canonical true/false only; other provider aliases remain in the original documentation.
Hunter — Email Verifier (GET)
Check the deliverability of an email address. A `valid` or `accept_all` email address is also saved automatically to your leads, and a lead you already have gets the new verification result. This is enabled by default and can be disabled for your account. The saved lead leaves out a phone number that is on a data broker deletion list, such as California's DROP.
Hunter — Domain Search (GET)
Find email addresses by domain Boolean filters in this execution profile accept canonical true/false only; other provider aliases remain in the original documentation.
Hunter — Domain Finder (POST)
Find the domain for a company via POST
Hunter — Combined Enrichment (GET)
Enrich a person and company
Hunter — Email Count (GET)
Return aggregate counts without revealing individual email addresses. This operation is free.
Hunter — Domain Finder (GET)
Find the domain for a company
Hunter — Multi-Domain Search Reveal (POST)
Reveal emails from a multi-domain search
Hunter — Discover People (POST)
Discover people using request-body filters
Hunter — Email Enrichment (GET)
Enrich a person
Hunter — Company Enrichment (GET)
Enrich a company
Hunter — Email Finder (GET)
Supply a LinkedIn handle, or supply a domain/company plus either a full name or first and last name. A found email address is also saved automatically to your leads. This is enabled by default and can be disabled for your account. The saved lead keeps the verification status this response reports. It leaves out a phone number that is on a data broker deletion list, such as California's DROP.
Common questions
How are Hunter APIs priced?
Each endpoint publishes its own rate and billing unit. Compare the selected implementation and request-specific conditions; a collection starting price is not a quote for every request.
How do I authenticate Hunter requests?
Use your OpenAny API key from a secure environment variable for supported account-based calls. Never paste secrets into prompts, documentation examples or public logs.
Are all implementations interchangeable?
No. Read each endpoint request schema, response examples and limitations before execution. Different suppliers may expose different fields and behavior; approve the budget before a paid call.
Use Hunter with your agent
Inspect endpoint contracts and confirm availability and pricing before a paid call.