Integrations
Make integration
Check an email address in any Make scenario with Make’s own HTTP app, then map the status, reason and action into the next module or a router filter. No app to install: one module and your API key.
- Status: Setup guide
- Make’s HTTP app, nothing to install
URL https://api.email-validation.org/v1/validate
Method POST
Headers Authorization: Bearer ev_live_…
Body type Raw
Content type JSON (application/json)
Request content {"email": "<the address, mapped in>"}
Parse response YesAt 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
- People who build Make scenarios for sign-ups, leads or orders and want each address checked on the way through.
- You need
- A Make scenario with a module that 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.
Check new leads
Validate a lead’s address before the scenario adds it to your CRM, your sheet or your mailing list.
Filter with a router
Send valid addresses down one route and the rest down another, with a filter on status or action.
Catch typos
did_you_mean suggests a correction when an address looks like a typo of a common domain; map it into a reply or a review step.
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 the HTTP module
Add the HTTP app’s Make a request module, with the URL
https://api.email-validation.org/v1/validateand method POST.Add your key
Add the header
AuthorizationwithBearerand your API key. Never put the key in the URL: such requests are refused.Send the address
Body type Raw, content type JSON, and the request content
{"email": "…"}with the address mapped in.Parse the response
Turn on Parse response, so status, reason and action can be mapped in later modules or a router filter.
Good to know.
- Map
status,reason,actionanddid_you_meaninto later steps; statuses and reasons explains each value. - Use a key made for Make, with a daily credit cap, so a looping scenario cannot spend more than you expect.
- 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