How do I verify emails in Make.com?

There is no dedicated Make app for Valid Email Checker, and you do not need one. Make.com ships with a generic HTTP module that can call any REST API, and our verification endpoint is a standard REST call. You point the HTTP module at our API, pass an address, and branch your scenario on the result — verify new sign-ups, clean leads before they hit your CRM, or filter out disposable addresses in real time.

Step 1 — Get an API key

Open the dashboard and go to the Developer page to generate an API key. Copy it somewhere safe — you will paste it into Make as a Bearer token. API access unlocks after your first credit purchase.

Step 2 — Add the HTTP module

1. In your scenario, click the + to add a module and search for HTTP. Choose Make a request.
2. Set Method to POST and URL to https://app.validemailchecker.com/api/verify-single.
3. Set Authentication type to No authentication — you pass the key with a header, not Make’s built-in auth (do not pick Basic auth or OAuth 2.0).
4. Under Headers, click Add a header and enter name Authorization, value Bearer <API_KEY> (replacing <API_KEY> with your key). To reuse the key across scenarios, create an API Key Auth connection instead — parameter name authorization, key Bearer <API_KEY>, placement Header.
5. Set Body content type to application/json and Body input method to JSON string, then enter the request body, mapping the address from an earlier module: {"email":"{{email}}"}.
6. Set Parse response to Yes and run the scenario once. The HTTP module returns the parsed JSON so downstream modules can reference fields like status and is_valid.

POST https://app.validemailchecker.com/api/verify-single
Authorization: Bearer <API_KEY>
Content-Type: application/json

{"email":"user@example.com"}

The response includes status (a deliverable address comes back as "safe"), is_valid (boolean), is_disposable, risk_score, and credits_used. Add a Router or Filter after the HTTP module and branch on status — for example, only continue to your "add to CRM" path when status equals safe.

Single vs. bulk

The setup above uses the single endpoint /api/verify-single — real-time, one address per call, ideal for verifying records as they pass through a scenario. That is the right default for most automations. See Make your first API call for the full single-verify reference.

If you need to clean a whole list at once, use the bulk flow instead: POST an array to /api/verify-bulk ({"emails":[...],"name":"..."}), which returns a task_id, then poll GET /api/get-results/{task_id} until the job finishes. In Make, that is two HTTP modules with a short delay or a follow-up scenario between them. See the Bulk endpoint reference for the polling pattern.

Cost

One credit per email verified — the same rate as everywhere else. Using Make.com adds no extra charge; you are simply calling the same API. If a result comes back as Unknown (we could not reach a definitive answer), that credit is automatically refunded, so you only pay for conclusive verifications.