# Bulk Email Validator (`moving_beacon-owner1/my-actor-27`) Actor

We verify emails instantly—bad ones are filtered out, good ones stay. Improve deliverability, protect reputation, and reach real customers.

Clean your email lists fast. Our verification tool removes fake, invalid, and risky emails so only quality contacts remain.

- **URL**: https://apify.com/moving_beacon-owner1/my-actor-27.md
- **Developed by:** [Jamshaid Arif](https://apify.com/moving_beacon-owner1) (community)
- **Categories:** Lead generation, Automation, Integrations
- **Stats:** 7 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Email Verifier — Apify Actor (Python)

Bulk-verify email addresses with **automatic proxy rotation on every single request**.

### Features

- **Per-request proxy rotation** — each API call gets a unique session ID, forcing the Apify proxy pool to assign a different IP every time.
- **Auto proxy in schema** — the `proxyConfiguration` field uses the built-in `"editor": "proxy"` widget so users pick proxy groups (Residential, Datacenter, etc.) directly from the Apify UI.
- **Async concurrency** — process multiple emails in parallel with `asyncio` + `httpx`.
- **Automatic retries** — 429 responses trigger exponential back-off with a fresh proxy on each retry.
- **Clean dataset output** — results are pushed to the default dataset with status, reason, and which proxy was used.

### Input Example

```json
{
    "emails": [
        "user@example.com",
        "hello@company.io"
    ],
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": ["RESIDENTIAL"]
    },
    "max_concurrency": 5,
    "delay_between_requests": 1000,
    "max_retries": 3
}
```

### How Proxy Rotation Works

Every call to `proxy_config.new_url(session_id)` uses a **unique** session
string built from a millisecond timestamp + attempt number. Apify's proxy pool
maps each distinct session to a different upstream IP, so every request
automatically exits through a fresh proxy — no manual rotation logic needed.

### Output

Each verified email produces a dataset record:

| Field          | Description                            |
|----------------|----------------------------------------|
| `email`        | The address that was checked           |
| `status`       | Verification result (valid / invalid …)|
| `reason`       | Detailed reason string                 |
| `disposable`   | Whether the domain is disposable       |
| `accept_all`   | Whether the server is a catch-all      |
| `free`         | Whether it's a free provider           |
| `proxy_used`   | Masked proxy URL used for the request  |
| `attempts`     | How many attempts were needed          |
| `timestamp`    | ISO timestamp of verification          |

### Deployment

```bash
apify push
```

# Actor input Schema

## `emails` (type: `array`):

List of email addresses to verify.

## `proxyConfiguration` (type: `object`):

Proxy settings — a fresh proxy is rotated on every single request automatically.

## `max_concurrency` (type: `integer`):

Maximum number of concurrent verification requests.

## `delay_between_requests` (type: `integer`):

Milliseconds to wait between requests to avoid rate limiting.

## `max_retries` (type: `integer`):

Number of times to retry a failed verification before giving up.

## Actor input object example

```json
{
  "emails": [
    "test@example.com"
  ],
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  },
  "max_concurrency": 5,
  "delay_between_requests": 1000,
  "max_retries": 3
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "emails": [
        "test@example.com"
    ],
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("moving_beacon-owner1/my-actor-27").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "emails": ["test@example.com"],
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("moving_beacon-owner1/my-actor-27").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "emails": [
    "test@example.com"
  ],
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call moving_beacon-owner1/my-actor-27 --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,moving_beacon-owner1/my-actor-27"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/nide14f77DRM27tkq/builds/bzb9zYZxc0XFEGBjd/openapi.json