Integrations
Zapier integration
Check an email address inside any Zap, then let a Filter or Paths step decide what happens next: add the contact, flag it for review or stop. It uses Zapier’s own Webhooks by Zapier app, so there is nothing to install.
- Status: Setup guide
- Webhooks by Zapier, nothing to install
Method POST
URL https://api.email-validation.org/v1/validate
Data {"email": "<the email field from your trigger>"}
Headers Authorization: Bearer ev_live_…
Content-Type: application/jsonAt 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
- Teams that already move sign-ups, leads or orders through Zapier and want a bad address caught before it reaches the CRM or the mailing list.
- You need
- A Zap whose trigger gives you an email address, and an API key made for it, with a daily credit cap.
- 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.
Clean form sign-ups
Check each new form sign-up and only pass on the addresses whose status is valid.
Protect your CRM
Validate a lead’s address before the Zap creates the contact, and flag the rest for a person to review.
Route by result
With Paths, send valid addresses one way, catch_all and unknown another, and stop invalid and disposable ones.
Set it up. 4 steps.
The short version of the full setup guide, which stays the reference when a step does not match what you see.
Add a Webhooks step
Add an action step with the Webhooks by Zapier app and choose Custom Request (or POST).
Point it at the API
Method POST, URL
https://api.email-validation.org/v1/validate, and the data{"email": "…"}with the email field from your trigger.Add your key
Headers:
AuthorizationwithBearerand your key, andContent-Typewithapplication/json.Test, then filter
Test the step, then use the returned status and action in a Filter or Paths step, for example only continue when status is valid.
Good to know.
- Map
status,reason,actionanddid_you_meaninto later steps; statuses and reasons explains each value. - Use a key made for Zapier, with a daily credit cap, so a looping Zap cannot spend more than you expect. Never put the key in the URL: such requests are refused.
- For EU data residency, send the request to
https://api-eu.email-validation.orginstead: the same key works on both. - For a whole list at once, send it as one bulk list and get a webhook when it is done.
- 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