Skip to content
looot docs
Esc
↑↓navigate↵open⌘Jpreview
On this page

BounceBan / Bulk results CSV link

BounceBan tool bounceban-bulk-export on looot: input fields, $0 per call, output shape, and code to run it with curl, JavaScript or Python.

You can use this API to export selected or all emails to an .csv file. If the request is successful, a downloadable public link will be returned. For security reasons, the link will expire after 4 hours of generation as it’s publicly available. You can always request a new file once the link expires. However, as the results for bulk email verification are available for only 90 days after verification, be sure to generate the file within the 90 days period. The endpoint is designed to export verified results only after the entire task has been completed. An error will be returned if the task is still in progress or incomplete.

Inputs

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.

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":"bounceban-bulk-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: "bounceban-bulk-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": "bounceban-bulk-export",
        "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.export as endpointId; see the job page.

Was this page helpful?