Verify emails in Clay

Setup

1. Create an API key at simpleverifier.com/api-keys. It starts with sv_live_. API access comes with selected paid plans; a key on a plan without it gets a 402 that says so.
2. In your Clay table, click Add column, search for HTTP API and choose it.
3. Set the method to GET and the endpoint to https://simpleverifier.com/api/v1/verify?email=/Email, inserting your email column where /Email appears.
4. Add a header named Authorization with the value Bearer followed by your key. Clay stores it as an account credential, so it is not repeated per column.
5. Run the column on a few rows first. Each call can take up to about 30 seconds on a slow mail server, so keep auto-run off until you have checked the output.
6. Add a formula or filter column on the status field to keep only valid rows. Map reason and send_advice if you want the explanation beside each row.

Using the result

Route on the status field: valid means the mail server confirmed the mailbox, risky means delivery could not be confirmed (catch-all domain, role address, provider that hides mailbox status), invalid means it will bounce or is a throwaway address. Keep risky out of cold sequences unless you accept the bounce risk.

Full endpoint reference, error codes and an OpenAPI file are in the API docs. For lists of thousands of addresses, upload a CSV on the verify page instead.

Common questions

Which plans include API access for Clay?

API access comes with selected paid plans, listed on the pricing page. A key on a plan without API access gets a 402 that says so. Each key can make 120 calls a minute.

Is there a native SimpleVerifier provider in Clay?

Not yet. Today you connect it with Clay's HTTP API column, which works with any REST API and a Bearer key.

How fast can I call it?

Up to 120 calls a minute per API key. Clay retries on a 429; the Retry-After header says how long to wait.