# Make Integration: Email Validation

URL: https://email-validation.org/integrations/make/
Updated: 2026-11-06

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

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.

[Read the full setup guide](https://email-validation.org/docs/guides/no-code/#make) [Get an API key](https://email-validation.org/signin/)

- Status: Setup guide
- Make’s HTTP app, nothing to install

**HTTP: Make a request** One module

Module settings

```text
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   Yes
```

## At 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](https://email-validation.org/app/api-keys/) made for it, with a [daily credit cap](https://email-validation.org/docs/authentication/#limits).
- **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](https://email-validation.org/docs/guides/no-code/#make)

## 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](https://email-validation.org/docs/guides/no-code/#make), which stays the reference when a step does not match what you see.

1. **Add the HTTP module**: Add the HTTP app’s Make a request module, with the URL `https://api.email-validation.org/v1/validate` and method POST.
2. **Add your key**: Add the header `Authorization` with `Bearer` and your API key. Never put the key in the URL: such requests are refused.
3. **Send the address**: Body type Raw, content type JSON, and the request content `{"email": "…"}` with the address mapped in.
4. **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`, `action` and `did_you_mean` into later steps; [statuses and reasons](https://email-validation.org/docs/statuses/) 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](https://email-validation.org/docs/eu-data-residency/), send the request to `https://api-eu.email-validation.org` instead: the same key works on both.
- For a whole list at once, send it as one [bulk list](https://email-validation.org/docs/guides/no-code/#bulk) and get a [webhook](https://email-validation.org/docs/webhooks/) when it is done.
- Try it first with `accepted@sandbox.email-validation.org` and the other [test addresses](https://email-validation.org/docs/test-addresses/): each returns the result its name says and costs nothing.

## Related

- [The full Make setup guide](https://email-validation.org/docs/guides/no-code/#make)
- [Zapier integration](https://email-validation.org/integrations/zapier/)
- [n8n integration](https://email-validation.org/integrations/n8n/)
- [The validate endpoint](https://email-validation.org/docs/api/validate/)
- [All integrations](https://email-validation.org/integrations/)