---
title: "BounceBan / Verify email"
description: "BounceBan tool bounceban-verify on looot: input fields, $0.004 per call, output shape, and code to run it with curl, JavaScript or Python."
sidebar:
  hidden: true
---

{/* Generated by scripts/generate-api-reference.mjs from data/api-reference.json. Do not edit. */}

**Overview:** This endpoint is designed for advanced users requiring granular control over BounceBan server connections. **Timeout & Async Handling:** This request has a **15-second timeout**. If verification completes within this window, the result is returned immediately. If verification exceeds 15 seconds, the API returns a `200 OK` response containing a transaction `id` and the status `verifying`. You can retrieve the final result in two ways: * **Polling:** Use the returned `id` to query the `v1/verify/single/status` endpoint. * **Webhook:** specific a `url` parameter in your initial request to receive the result via webhook. **Alternative for Long Connections:** If your infrastructure supports long-held GET connections (e.g., Clay, n8n), we recommend using the **W

- **Tool id:** `bounceban-verify`
- **Provider:** [BounceBan](/providers/bounceban)
- **Job:** [Verify an email address is deliverable](/reference/jobs/people-email-verify) (`people.email.verify`)
- **Price:** $0.004 per call. A call that fails at the provider costs $0.

## 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`. &gt; `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 |

## Output

The run's `result` holds the provider's answer. Signed in, `looot inspect bounceban-verify` prints its fields.

## Run it

Every call needs your API token in `LOOOT_TOKEN`; [Sign in](/get-started/sign-in#use-the-token-in-scripts-and-agents) 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:

<CodeGroup>

```bash curl
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","input":{"email":"jane.doe@example.com"},"wait":30}'
```

```js JavaScript
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",
    input: {
      email: "jane.doe@example.com",
    },
    wait: 30,
  }),
});
const run = await response.json();
console.log(run.status, run.result);
```

```python Python
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",
        "input": {
            "email": "jane.doe@example.com",
        },
        "wait": 30,
    },
    timeout=90,
)
run = response.json()
print(run["status"], run.get("result"))
```

</CodeGroup>

To let looot pick among every provider of this job instead, send `job:people.email.verify` as `endpointId`; see [the job page](/reference/jobs/people-email-verify).
