HomeGuidesVerify emails in Clay
How to verify emails in Clay
Add an HTTP API column in Clay, set it to GET our verify address with your email column on the end, and send your API key as a saved header. Run it on one row, then the rest. Pull verified into its own column and filter on it. Found emails need this step too.
Free while in beta. No card needed.
Key takeaways
- The setup: one HTTP API column, one saved header with your key.
- The result: a verified true or false on every row, ready to filter.
- The order: find, then verify. A found email isn't checked yet.
Last updated 16 Nov 2026
Before you start
Clay keeps lead lists in a table. This guide covers email verification there, and the email finder step before it. Rows are people and columns are facts about them. You'll add a column that asks our service about each row's email.
You need an API key. Sign up for a free account, open API keys in the dashboard and make one named "Clay". Using a separate key means you can delete it on its own. See Create and manage API keys.
Add the verify column
Open your table
It needs a column that holds emails.
Add an HTTP API column
Click to add a column and choose an enrichment (a column that fetches new data for each row). Search for HTTP API and pick it. It opens on the AI Generate tab, so click Configure instead.
Set the method and address
Set the method to
GET. In the URL box, typehttps://api.emailfinderverifier.com/api/v1/verify?email=and then insert your email column right after the equals sign. Type a slash and pick the column.Add your key as a saved header
Don't type the key straight into Headers. Clay shows those as plain text, so anyone who opens the column can read them. Use a saved header account instead. Add one with the header name
X-API-Keyand your API key as the value, then pick it in the column.Run one row first
Run the column on a single row and check the answer looks right. Then run the rest.
Pull out the answer
Pull
verifiedinto its own column. Then filter your table on it. Keep the rows where it's true.
Find, then verify
To find emails first, add another HTTP API column. Use https://api.emailfinderverifier.com/api/v1/find as the URL. Add three query parameters, first_name, last_name and domain, and map each to the matching column. Pull email out of the answer.
Then point your verify column at that found email. Two columns, one key, in this order. Only the rows that come back verified should go to your sequencer. See Find, then verify and Add finding to your waterfall.
Read the results
verified |
What it means | What to do |
|---|---|---|
true |
We confirmed the mailbox. Catch-all domains can come back true too. | Keep. Send. |
false |
We couldn't confirm it. It may be a bad address, or a real one we can't confirm. | Leave it out. Check again in a few days. |
When something goes wrong
| What you see | What to do |
|---|---|
A 429 error |
You went too fast. New accounts can send 1 request per second. Lower the batch size (how many rows run at once) or add a short delay. |
A 401 error |
The key is wrong or deleted. Check the header name is X-API-Key and the value is the whole key. |
| Empty answers | Check the email column is mapped and the rows aren't blank. |
If you don't use Clay
The same two requests work in n8n, Make, Zapier, Google Sheets, your own code or Claude. See n8n, Make, Zapier and Google Sheets. Without any tool, upload a CSV in Verify or find a list, up to 5,000 rows a run. See clean an email list.
Get your API key and add the column. Free while in beta.
Sign up for free01FAQ
Questions, answered
01Do I need a paid Clay plan?
Check Clay's own plan pages for what the HTTP API column needs. We only need your key and the two web addresses above.
02Can I run this on a whole table at once?
Yes, but keep batches small. Our speed limit on new accounts is 1 request per second, so a long table takes time.
03Does it work on catch-all domains?
Yes. A catch-all email can come back verified. See how to verify a catch-all email.
04Is the found email already verified?
No. Add the verify column after the find column.
05Is my key safe in Clay?
Use a saved header account so the key stays hidden. Use a separate key for Clay and delete it if it ever leaks.
06What if I want more speed?
Ask us in Slack. See Get support.
09Keep going
Where to next
- GTM engineers and Clay buildersTwo HTTP columns in Clay or n8n: find the work email, then verify it. One key.
- Enrichment platforms and data productsUse EFV as one more provider step, or talk to us about running it under your own name.
- Cold email agenciesCheck each client's list before it touches a mailbox you spent weeks warming up.
09Start today
Add verify to your Clay table
Sign up with email or Google. No card. Your key and a ready-made first request are waiting. Need more later? Message us on Slack.