Batch people email verify
Run job:people.email.verify.batch through the looot API: 2 providers, from $0.004 per result. Inputs, prices, output shape and code for curl, JavaScript and Python.
Batch people email verify.
Job id people.email.verify.batch, in Enrichment (People & contact data). As of 2026-10-07, 2 providers serve it through 2 tools. Run job:people.email.verify.batch and looot picks one of them; with fallback on, a miss moves on to the next. See Jobs.
Inputs
Fields the job’s tools take, most shared first. Any key you send passes through unchanged.
| Name | Type | Taken by | Required by | Description |
|---|---|---|---|---|
disable_catchall_verify |
string | 1 of 2 | 0 | (Optional) Defaults to 0. When set to 1, BounceBan performs only basic SMTP verification. This may leave catch-all emails or those protected by ESGs (Email Security Gateways) unverified. For these addresses, the API will return result: 'unknown', score: -1, and the credit cost is 0. |
email |
array | 1 of 2 | 1 | Email addresses |
emails |
array | 1 of 2 | 1 | (Required) A list of emails for verification. |
greylisting_bypass |
string | 1 of 2 | 0 | (Optional) Configures the retry delay for SMTP verification when an email address is temporarily rejected due to greylisting. Learn more about greylisting here: https://en.wikipedia.org/wiki/Greylisting_(email). Default is auto. > auto: The default and recommended setting. This option automatically adjusts the retry delay to balance verification speed with the success rate. We typically use a shorter delay for smaller lists and a… |
mode |
string | 1 of 2 | 0 | (Optional) Verification mode to apply for all the emails in the bulk verification task. Default is regular. > regular: The default option for email verification. It does not assume that the domain of the email owner’s current company website matches the domain of the email being verified. > deepverify: DeepVerify operates on the assumption that the domain of the email owner’s current company website matches the domain of the email being verified. This assumption can improve the succ… |
name |
string | 1 of 2 | 0 | (Optional) The name for the task. If not provided, a task name will be automatically generated. |
url_finished |
string | 1 of 2 | 0 | (Optional) A webhook target URL specified to receive task completion events in real-time through an HTTP POST request. A webhook event will be triggered as soon as the whole task is completed. In case of a failed webhook event delivery, the system will attempt to resend the event up to two additional times within a short interval. > The webhook event will also include the event-type: bulk.task_finished header so you can differentiate between different events. > Please note that the… |
Providers and prices
| Provider | Tool | Price |
|---|---|---|
| BounceBan | bounceban-bulk-submit |
$0.004 per result |
| Scrubby | scrubby-bulk-submit |
$0.0078 per result |
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-submit 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","input":{"emails":[]},"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",
input: {
emails: [],
},
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",
"input": {
"emails": [],
},
"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. 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. For bounceban-bulk-submit that is emails.