Hunter / Find email addresses at a domain (POST)
Hunter tool hunter-domain-search-post on looot: input fields, $0.00245 per result, output shape, and code to run it with curl, JavaScript or Python.
Finds email addresses for a domain, with parameters in the request body so it can take nested location filters. Send domain or company; seniority, department, job_titles and limit filter it.
- Tool id:
hunter-domain-search-post - Provider: Hunter
- Job: Find all contacts and email addresses at a company domain (
people.domain.search) - Price: $0.00245 per result. A call that fails at the provider costs $0.
Inputs
| Name | Type | Required | Description |
|---|---|---|---|
location |
string | no | |
aggregations |
boolean | no | |
company |
string | no | |
decision_maker |
string | no | A boolean filter. Query-string clients may use the documented case-insensitive aliases. |
department |
string | no | Comma-separated department values from Hunter’s live position taxonomy (not a frozen enum). ~ matches people with no department. Unknown values are ignored; a list with no remaining valid values returns 400 (invalid_department). Example: “sales,marketing” |
domain |
string | no | |
job_titles |
string | no | |
limit |
integer | no | |
offset |
integer | no | |
required_field |
string | no | |
saved_leads |
boolean | no | |
seniority |
string | no | Comma-separated seniority values from Hunter’s live position taxonomy (not a frozen enum). Unknown values are ignored; a list with no remaining valid values returns 400 (invalid_seniority). Example: “senior,executive” |
source_type |
string | no | |
type |
string | no | |
verification_status |
string | no |
Output
The run’s result holds the provider’s answer. Signed in, looot inspect hunter-domain-search-post prints its fields.
Run it
Every call needs your API token in LOOOT_TOKEN; Sign in shows how to get one. Each run also needs a new idempotency key, so a retry never pays twice. With wait: 30 the answer comes back inline when the run ends within 30 seconds. Otherwise you get the running run back: poll GET /v1/runs/<runId>.
Example input with placeholder values:
curl -X POST "https://api.looot.ai/v1/runs" \
-H "Authorization: Bearer $LOOOT_TOKEN" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{"endpointId":"hunter-domain-search-post","input":{"seniority":"senior,executive","department":"sales,marketing"},"wait":30}'const response = await fetch("https://api.looot.ai/v1/runs", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.LOOOT_TOKEN}`,
"Content-Type": "application/json",
"Idempotency-Key": crypto.randomUUID(),
},
body: JSON.stringify({
endpointId: "hunter-domain-search-post",
input: {
seniority: "senior,executive",
department: "sales,marketing",
},
wait: 30,
}),
});
const run = await response.json();
console.log(run.status, run.result);import os
import uuid
import requests
response = requests.post(
"https://api.looot.ai/v1/runs",
headers={
"Authorization": f"Bearer {os.environ['LOOOT_TOKEN']}",
"Idempotency-Key": str(uuid.uuid4()),
},
json={
"endpointId": "hunter-domain-search-post",
"input": {
"seniority": "senior,executive",
"department": "sales,marketing",
},
"wait": 30,
},
timeout=90,
)
run = response.json()
print(run["status"], run.get("result"))To let looot pick among every provider of this job instead, send job:people.domain.search as endpointId; see the job page.