Integrations
Postman integration
Try every request of our API from Postman with a collection that holds one request per operation, with descriptions, example bodies and saved example answers. Two environments, one for the US host and one for the EU host, keep your key in a masked variable that no downloaded file contains.
- Status: Setup guide
- US and EU environments, no key in any file
Import email-validation.postman_collection.json
email-validation-us.postman_environment.json
Environment email-validation.org (US)
apiKey ev_live_… (current value only)
Send Validation > Validate an email address
Body {"email": "accepted@sandbox.email-validation.org"}
Answer valid, reason acceptedAt a glance.
- Status
- Setup guide. Not listed on a marketplace yet: you set it up yourself in a few steps, below and in the full guide.
- For
- Developers who want to see each request and answer before writing code, and anyone who tests an integration, a bulk list or the EU host by hand.
- You need
- Postman, the collection and at least one environment file from the guide, and an API key made for it, with a daily credit cap. Add the Bulk lists permission to try the bulk requests.
- Costs
- 1 credit = 1 validated address, as with any API request. Free: unknown results, API errors, malformed addresses and test addresses on sandbox.email-validation.org.
- Full guide
- Read the full setup guide
Typical uses.
Try every request
The collection has a folder each for Validation, Account, Bulk jobs, Service, MCP and A2A, with example bodies and saved answers, so you can see what each request returns before you call it from code.
Run a bulk list by hand
Create a bulk job keeps the new job’s id in a collection variable, so Get a bulk job and Download bulk results (CSV) work on it without copying anything.
Compare the US and EU hosts
Switch the environment at the top right to send the same request to the EU host, where addresses are validated in the EU and their results stored there.
Set it up. 5 steps.
The short version of the full setup guide, which stays the reference when a step does not match what you see.
Download the files
Download the collection and the US environment, the EU environment or both from the guide. The collection is not in the Postman API Network yet, so there is no public workspace to fork.
Import them
In Postman, click Import and drop in the collection and the environment files.
Pick an environment
Choose email-validation.org (US) or email-validation.org (EU) at the top right.
Paste your key
Create a key on the API keys page and paste it into the environment’s
apiKeycurrent value. Keep the initial value empty: initial values are shared with everyone in your workspace.Send your first request
Open Validation, Validate an email address and click Send. Its body checks
accepted@sandbox.email-validation.org, a free test address: the answer isvalid, reasonaccepted.
Good to know.
- The key goes in the Authorization header as a bearer token, set once for the whole collection. The status, latency and OpenAPI requests need no key and send none.
- A create request sent twice creates two bulk lists, so send it once per list. To review a job before it starts, enable the create request’s start parameter with the value false, then use Start a bulk job when the job is ready.
- Two requests always go to the US host, in both environments: Validate an email address (query string) and Get the A2A agent card. On the EU host, validate with the request that sends the address in a
POSTbody. - The collection follows our OpenAPI document. After an API change, download it again and import it with Replace to keep your environments and current values.
- Try it first with
accepted@sandbox.email-validation.organd the other test addresses: each returns the result its name says and costs nothing.
Updated · Maintained by the email-validation.org team