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

BounceBan / Verify email (waits for result)

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

This API is recommended for Clay, N8N, and any other services that use one single HTTP request for email verification). Note: This endpoint uses a different base URL than other BounceBan APIs. The full URL for this API is https://api-waterfall.bounceban.com/v1/verify/single. With this API, you don’t need to send a seperate api (/v1/verify/single/status) call to poll for verification result. Instead you just send the same request again if it times out. The API times out with status code 408 if verification is not completed within the specified timeout period (default 80 seconds, configurable via the timeout parameter). In this case, you should send the same request again - retries within 30 mins of the initial verification request for the same email won’t

Inputs

Name Type Required Description
disable_catchall_verify string no (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’
email string yes The email that needs to get verified.
mode string no (Optional) Setting the verification mode for the verification job. Default mode 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 doma
timeout integer no (Optional) The timeout duration in seconds for the verification request. The API will return a 408 timeout status code if verification is not completed within this timeframe. Default is 80 seconds. Important: Make sure the timeout value i

Output

The run’s result holds the provider’s answer. Signed in, looot inspect bounceban-verify-sync 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-verify-sync","input":{"email":"jane.doe@example.com"},"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-verify-sync",
    input: {
      email: "jane.doe@example.com",
    },
    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-verify-sync",
        "input": {
            "email": "jane.doe@example.com",
        },
        "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 as endpointId; see the job page.

Was this page helpful?