Export people email verify batch
Run job:people.email.verify.batch.export through the looot API: 1 provider, from $0 per call. Inputs, prices, output shape and code for curl, JavaScript and Python.
Export people email verify batch.
Job id people.email.verify.batch.export, in Enrichment (People & contact data). As of 2026-10-07, 1 provider serve it through 1 tool. Run job:people.email.verify.batch.export and looot picks one of them; with fallback on, a miss moves on to the next. See Jobs.
Inputs
This job has one tool, so it takes that tool’s fields. Any key you send passes through unchanged.
| Name | Type | Required | Description |
|---|---|---|---|
criteria |
object | no | Specifies emails to retrieve based on verification state (deliverable, undeliverable , risky, or unknown) and attributes. |
id |
string | no | (Required) The unique identifier of a completed bulk email verification task. Generating the download link usually takes a few seconds. For larger tasks, the process may take longer: <strong>100,000 emails</strong>, approximately 30 second; <strong>400,000 emails</strong>, approximately 2 minutes. If the download link is unavailable after your initial request, wait a few seconds and try again. To prevent excessive requests, limit attempts for the same export to <strong>15 req… |
keep_all_rows |
boolean | no | (Optional) When set to true, all rows from the source .CSV file, including those without an email address, will be included in the downloaded .CSV file. Email verification results will not be provided for emails that do not meet your specified filters. Please note that this feature only applies to tasks created through the /v1/verify/bulk/file endpoint. Default value is false. |
Providers and prices
| Provider | Tool | Price |
|---|---|---|
| BounceBan | bounceban-bulk-export |
$0 per call |
A call that fails at the provider costs $0. See What’s free.
Output
The run’s result holds the provider’s answer. Signed in, looot inspect bounceban-bulk-export 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":"job:people.email.verify.batch.export","input":{"id":"<id>"},"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: "job:people.email.verify.batch.export",
input: {
id: "<id>",
},
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": "job:people.email.verify.batch.export",
"input": {
"id": "<id>",
},
"wait": 30,
},
timeout=90,
)
run = response.json()
print(run["status"], run.get("result"))To pin one provider, send its tool id as endpointId instead of job:people.email.verify.batch.export. The shared input names above are for the job: run only; a tool id takes that tool’s own field names, listed on its page, and refuses the shared ones when they differ.