BounceBan / Bulk results (all)
BounceBan tool bounceban-bulk-dump on looot: input fields, $0 per call, output shape, and code to run it with curl, JavaScript or Python.
Retrieve verification results for a bulk email verification task using a task ID in JSON format. Results are available within 90 days of verification. When making a request with the state parameter included, you might not receive all the verified results if the task is not yet finished. To obtain a comprehensive list of the verified emails that have been processed so far, you should omit the state parameter from your request.
- Tool id:
bounceban-bulk-dump - Provider: BounceBan
- Job: Results people email verify batch (
people.email.verify.batch.results) - Price: $0 per call. A call that fails at the provider costs $0.
Inputs
| Name | Type | Required | Description |
|---|---|---|---|
cursor |
string | no | (Optional) Provide this parameter to retrieve results from the next page. You can obtain the cursor value from the previous rquest response. If retrieve_all is set to 1, the page_size and cursor parameters will be ignored. |
id |
string | yes | Bulk email verification task ID. |
page_size |
integer | no | (Optional) Specify the number of emails to return per request. Default: 100. Maximum: 3,000. Minimum: 100. If retrieve_all is set to 1, the page_size and cursor parameters will be ignored. |
retrieve_all |
string | no | (Optional) Retrieve all emails for the task by setting this parameter to 1. Default: Disabled (empty). Important Notes: If retrieve_all is set to 1, the page_size and cursor parameters will be ignored. This parameter is only effective |
state |
string | no | Specifies emails to retrieve based on verification state (deliverable, undeliverable , risky, or unknown). If not set, all emails will be returned. When making a request with the state parameter included, you might not receive all the verif |
Output
The run’s result holds the provider’s answer. Signed in, looot inspect bounceban-bulk-dump 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":"bounceban-bulk-dump","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: "bounceban-bulk-dump",
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": "bounceban-bulk-dump",
"input": {
"id": "<id>",
},
"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.email.verify.batch.results as endpointId; see the job page.