# Postman Collection for the API

URL: https://email-validation.org/docs/guides/postman/
Updated: 2026-11-13

> Documentation index: https://email-validation.org/llms.txt

Try every API request from Postman: our collection holds one request per API operation, with descriptions, example
bodies and saved example answers, and two environments, one for each API host. Download the files below and import
them into your own workspace.

**Status: setup guide.** The collection is not in the Postman API Network yet, so there is no public workspace to fork
from and no Run in Postman button. The downloads below are the same collection, generated from our
[API reference](https://email-validation.org/docs/api-reference/), and updated whenever the API changes.

## Download the files

- [The collection](https://email-validation.org/downloads/postman/email-validation.postman_collection.json): every request, in folders
  (Validation, Account, Bulk jobs, Service, MCP, A2A).
- [The US environment](https://email-validation.org/downloads/postman/email-validation-us.postman_environment.json): requests go to `https://api.email-validation.org`.
- [The EU environment](https://email-validation.org/downloads/postman/email-validation-eu.postman_environment.json): requests go to `https://api-eu.email-validation.org`,
  where addresses are validated in the EU and their results stored there ([EU data residency](https://email-validation.org/docs/eu-data-residency/)).

Both environments hold an empty `apiKey`: no key is in any file.

## Import and send your first request

1. In Postman, click **Import** and drop in the collection and one or both environment files.
2. Pick the environment **email-validation.org (US)** or **email-validation.org (EU)** at the top right.
3. Create a key on the [API keys page](https://email-validation.org/app/api-keys/) and paste it into the environment's `apiKey` **current
   value**. Keep the initial value empty: initial values are shared with everyone in your workspace. The variable is
   of type secret, so Postman masks it.
4. Open **Validation > Validate an email address** and click **Send**. Its body checks
   `accepted@sandbox.email-validation.org`, a free [test address](https://email-validation.org/docs/test-addresses/): the answer is `valid`, reason
   `accepted`.

The key goes in the `Authorization` header as a bearer token, set once for the whole collection
([authentication](https://email-validation.org/docs/authentication/)). The status, latency and OpenAPI requests need no key and send none.

## Bulk lists

1. **Bulk jobs > Create a bulk job** sends a list of addresses as JSON. Its test script keeps the new job's id in the
   collection variable `jobId`.
2. **Get a bulk job** shows the job's status and progress. The job starts on its own; to review it first, enable the
   create request's `start` parameter with the value `false`, then use **Start a bulk job** when the job is `ready`.
3. When the status is `completed`, **Download bulk results (CSV)** returns the results file.

A create request sent twice creates two lists, so send it once per list. Use test addresses in your lists while you
try it: they are free in bulk jobs too. More: [bulk jobs](https://email-validation.org/docs/bulk/).

## Two requests that always use the US host

**Validate an email address (query string)** and **Get the A2A agent card** go to `https://api.email-validation.org` in both environments: the
EU host does not offer them. On the EU host, validate with **Validate an email address** (the address in a `POST`
body).

## Keep the collection current

The collection follows the [OpenAPI document](https://api.email-validation.org/openapi.json). After an API change, download it again and import
it with **Replace** to keep your environments and current values.