The pattern that works in every tool
There are two ways to add verification. For leads that flow through an automation one at a time, call the API with an HTTP request step and branch on the result. For a batch you already have, upload a CSV, download the results and import only the addresses you want. The first is automatic, the second is simpler for one-off lists.
Either way, decide what each result does before you build anything. A status is a decision aid, so write the rule down first: deliverable goes to the sequence, undeliverable is dropped, risky goes to a small separate batch, and unknown is retried later. Building the branch after you know the rule takes minutes.
The HTTP request to configure
In Clay, Make and Zapier, the verification call is a GET request to the VeriDock API with your key as a bearer token. The response is JSON with a status, a reason, a score and sometimes a typo suggestion. Map status and reason to columns or variables in your workflow, and branch on status.
Use a test key (vd_test_) while you build. Test keys never use credits, so you can run the workflow on sample data and check the branching before you spend anything.
GET https://app.veridock.io/v1/verify?email=jane@acme.com
Authorization: Bearer YOUR_API_KEY
# Response fields to map: status, reason, score, suggestion
# status is one of: deliverable, undeliverable, risky, unknownClay, Make and Zapier
In Clay, add an HTTP API column that calls the endpoint with the lead's email, then add a formula or conditional run so that only rows with a deliverable status move on to the next enrichment or to your export. Keeping the verification result in its own column makes it easy to filter and to audit later.
In Make, use the HTTP module to make a request, then a router with one route per status. In Zapier, use a Webhooks by Zapier GET step followed by a Filter or Paths step. In both, send undeliverable addresses nowhere, and send risky ones to a separate list or sheet instead of the main sequence. Our Zapier, Make and n8n guide has the exact fields for each.
- Clay: HTTP API column, then filter or conditionally run downstream columns on status.
- Make: HTTP module, then a router with a route for each status.
- Zapier: Webhooks by Zapier GET, then Filter or Paths on status.
- All three: store status and reason with the lead so you can see why a decision was made.
Smartlead and other sequencers: verify before import
For a sequencer such as Smartlead, the safest point to verify is before the leads go in. Export the list, run it through a bulk check, and import only the addresses you want to send to. That keeps bad addresses out of your sending history entirely, instead of removing them after they have already bounced.
Treat it as a routine, not a rescue. Check every list before it goes into a campaign, keep risky addresses in a separate batch so a bad result hurts only that batch, and add every hard bounce to a suppression list that outlives any one campaign.
Never merge the risky bucket back into your main send. Keeping it separate is what lets a weak batch hurt only itself.
Routing each result
Deliverable addresses are your main list. Undeliverable addresses are removed for good. Risky covers catch-all domains, role addresses such as info@ and disposable addresses, and the reason field tells you which. Unknown means the mail server did not answer clearly, so retry after a day. VeriDock does not bill unknown results, and re-checking an address within 30 days is free.
- deliverable: send in your normal sequence.
- undeliverable: drop it and never retry from another mailbox.
- risky with reason catch_all or role: a small separate batch, or skip.
- risky with reason disposable: drop it.
- unknown: retry later instead of guessing.
Key takeaways
0/5Try it on a real address
Run syntax, DNS, MX, disposable, and role checks on any address. No signup needed.
Enter an address and press Check.
Runs real syntax, DNS and mail-server checks.
This demo checks syntax, domain, mail server, disposable and role-address rules. Sign up free for live mailbox checks.
Frequently asked questions
Verify addresses with one API call.
250 free checks to start, no card required. Unknown results are never billed.