---
ref: tool:bouncer/create-verification-batch
name: Create a verification batch
company: company:bouncer
workflows: [workflow:verify-email-list-before-sending]
access: [mcp, api]
tags: [capability:verify-emails, category:data-provider, has:api, has:mcp]
docs: https://docs.usebouncer.com/api-reference/batch/batch-create
updated: 2026-10-09
---

# Create a verification batch

Queues a list of up to 100,000 email addresses for verification and returns a batchId, the number of addresses and the duplicates found.

Note: Send `[{"email": "…"}]`. Batches of 1,000 to 10,000 are recommended, and an account's batches run one after another. Returns `402` when credits run short. Poll the batch's status, then download its results.

## Set up

Use the first option your agent supports.

### MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

```json
{ "mcpServers": { "bouncer": { "url": "https://api.usebouncer.com/mcp" } } }
```

Call the MCP tool `create_batch`.

Server URL: https://api.usebouncer.com/mcp

### API (official)

- Base URL: https://api.usebouncer.com
- Endpoint: `POST /v1.1/email/verify/batch`
- Auth: send the header `x-api-key: $BOUNCER_API_KEY`
- Get a key: https://app.usebouncer.com
- Docs: https://docs.usebouncer.com/quick-start

Note: Create the key in the app's API section. Batch jobs run one after another per account, so a 100,000-address batch delays the next one.

Before anything else, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

## Rules

- Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
- Never print API keys.