Clay Email Verification Integration — Verify Lead Emails Directly in Clay Tables

EmailVerify.io integrates with Clay via Clay's built-in HTTP API enrichment feature — no dedicated platform connection needed. In any Clay table, add an HTTP API enrichment pointed at https://app.emailverify.io/api/v1/validate. Map the email column to the 'email' parameter and add your EmailVerify.io API key as the 'apikey' parameter. Clay calls the API for each row and populates a result column with verification data.

Two parameters are required: 1) apikey — your EmailVerify.io API key (generate it in your EmailVerify.io account under the API section); 2) email — the email address column to verify (in Clay, press '/' to select the column containing email addresses). Full endpoint: https://app.emailverify.io/api/v1/validate — Method: GET.

The API returns a JSON object for each email. Key fields: status (valid / invalid / catch-all / disposable / unknown), sub_status (specific reason code — mailbox_not_found, smtp_timeout, catch_all, disposable_domain, role_based, free_email, etc.), free_email (true or false), disposable (true or false), and mx_found (true or false). In Clay, expand the result cell to see all fields, then create new columns referencing specific nested values.

Catch-all domains accept all incoming emails regardless of whether the specific mailbox exists — making it impossible to confirm if a particular address is deliverable. For outbound prospecting, catch-all emails carry moderate risk. If volume is small: include but monitor bounce rates closely. If running high-volume cold email: exclude to protect your sender domain. Most Clay users filter for status = 'valid' only to protect high-volume sender domains from bounce-triggered suspensions.

After running the EmailVerify.io enrichment in Clay: click the filter icon on your Clay table, add a filter on your result column, and set the condition: status equals 'valid'. Your table now shows only verified, deliverable leads. Alternatively, create a new column that extracts just the status value using Clay's dot notation (e.g. [enrichment_column.status]), then filter on that column.

Yes. In Clay, you can configure HTTP API enrichments to run automatically when new rows are added to a table — depending on your Clay automation and workflow settings. This allows you to build a workflow where new leads sourced from LinkedIn, Apollo, or other sources are automatically verified as soon as they appear in your Clay table.

Cold email tools like Instantly, Smartlead, and Outreach send from your sending domain. If invalid emails generate hard bounces, your domain's sender reputation degrades — leading to email providers filtering your messages to spam even for valid recipients. Verifying in Clay before exporting to your sequencing tool ensures you never load invalid emails into your outreach campaigns, keeping your bounce rate near 0% and your sender domain healthy.

Setting up the Clay HTTP API enrichment requires no paid tier of EmailVerify.io beyond the credits consumed per verification. New users receive free credits to test the integration. Note: Clay itself has subscription tiers that affect the number of enrichment runs available. Check your Clay plan limits alongside your EmailVerify.io credit balance when planning large verification runs.

Recommended Clay workflow: 1) Source leads from LinkedIn Sales Navigator, Apollo, or scraped data into a Clay table. 2) Find emails using Clay's email finder enrichments (Hunter, Apollo, Snov.io, etc.). 3) Verify using EmailVerify.io HTTP API enrichment — filter for status = valid. 4) Add remaining enrichment (company data, personalisation tokens, intent data). 5) Export only verified, enriched leads to your sequencing tool. This waterfall approach maximises deliverability and sender domain health for high-volume outbound programs.