Clay logo

LeadMagic has made more than one billion API calls with Clay and won The Unstoppable Wheel award.

Recap
LeadMagicDocs

Validate Email

Verify email addresses with SMTP checks and engagement signals. Returns clear valid, invalid, or unknown statuses.

POSThttps://api.leadmagic.io/v1/people/email-validation
Try this endpointOpen the API playground

Addresses you submit stay yours. Validating an address does not add it to LeadMagic's contact database, and submitted addresses are never sold or made available to other customers. This applies whether you call the API directly or through a partner integration. See the Data Use Policy.

Endpoint Details

MetricValue
Cost0.25 credits per definitive validation
Calculation4 definitive validations = 1 credit
Free Outcomesunknown results and malformed inputs rejected with HTTP 400

You only pay for definitive results (valid, invalid). Inconclusive results (unknown) are always free, including mailboxes on accept-all domains we cannot individually verify, timeouts, and upstream outages.

A well-formed address can still be undeliverable. For example, an address on a reserved domain can return a definitive invalid without an SMTP probe and costs 0.25 credits. Synchronous requests with malformed addresses return HTTP 400 and use no credits.


Quick Example


Request Parameters

email
string
required

The email address to validate. Must be a properly formatted email address.


Response

email
string

The validated email address (normalized)

email_status
string

Validation result: valid, invalid, or unknown

credits_consumed
number

Credits used for this request (0.25 for valid/invalid, 0 for unknown)

message
string

Human-readable status message

mx_record
string

Primary MX record for the domain

mx_provider
string

Email provider (Google Workspace, Microsoft 365, etc.)

mx_gateway
string

Security gateway vendor name (null if none)

mx_gateway_type
string

Security gateway type (null if none)

mx_security_gateway
boolean

Whether a security gateway is present

Example Response


Status Codes

valid

Typically safe to email

Mail server accepted the address at check time. Not a delivery guarantee (catch-all and policy can still change). Costs 0.25 credits.

invalid

Do NOT email - Will bounce

The mail server confirmed that the mailbox does not exist, or the address is known to be undeliverable (for example, it uses a reserved domain). Costs 0.25 credits.

unknown

Inconclusive - Could not determine validity

Couldn't reach the mail server, the SMTP conversation was inconclusive, or the domain accepts all mail so the mailbox cannot be individually verified. FREE (no charge).

Route verification results in a list or Clay workflow

API resultSuggested routingCredits
validEligible for your sending policy after consent and suppression checks.0.25
invalidSuppress the address and look for a corrected address if needed.0.25
unknownHold for review. Recheck when the underlying evidence or service status changes.0

In Clay, retain email_status and credits_consumed in separate columns. Gate any export or sequencer push on the final decision. To compare verifiers, use the same sampled addresses and report each provider's resolution rate, agreement with reference labels, and cost per resolved address. Include the unknown share and test date.

Accept-all (catch-all) domains

When a domain accepts mail for any local part and LeadMagic cannot individually verify the mailbox, the result is unknown and free. There is no separate catch-all status or flag: resolve these addresses later or route them through Email Finder.

Malformed input

For a synchronous request, the API rejects malformed input before checking the mailbox.

CaseExampleResult
Missing @ symboljohncompany.comHTTP 400 (free)
Whitespace inside the addressjohn@comp any.comHTTP 400 (free)
Missing domainjohn@HTTP 400 (free)
Consecutive dotsjohn..doe@company.comHTTP 400 (free)
Missing top-level domainjohn@companyHTTP 400 (free)

Handle HTTP 400 as an input error. Correct the address before resubmitting it. There is no email_status result for a rejected request.

Instant invalid (no SMTP probe)

A well-formed address that is known to be undeliverable can return invalid without an SMTP probe. For example, john@example.invalid uses a reserved top-level domain and returns HTTP 200 with email_status: "invalid" at a cost of 0.25 credits.


Success Messages

MessageStatusCost
Email is valid.valid0.25
Email is invalid.invalid0.25
Invalid email: … (definitive result, e.g. a reserved domain)invalid0.25
Unable to verify email status.unknownFREE

Best Practices

A basic client-side format check can catch obvious mistakes before an API call. Malformed inputs that reach the API are rejected with HTTP 400 and use no credits.

Always validate lists you sourced elsewhere (CRM exports, purchased lists, sign-ups) before sending: invalid emails hurt your sender reputation. Emails returned by Email Finder are already validated on the way out, so you never need to re-validate those.

For unknown results, consider retrying later or using Email Finder to verify the specific address exists before adding to campaigns.

For large lists, batch your requests to stay within rate limits. Use the response headers to monitor your remaining quota.

Every response includes X-Credits-Remaining so you can track spending without extra API calls.

Some mail servers answer slowly, so set your HTTP client timeout to at least 30 seconds. A timeout or 5xx response can leave the outcome unknown: check the request and credit history before sending another validation. Keep the request ID if you need help from support. A Retry-After header tells you when to try again, but does not establish whether the previous request completed.


Use Cases

List Cleaning

Validate email lists before campaigns to reduce bounces and protect sender reputation.

Form Validation

Validate emails at point of capture to ensure data quality from the start.

CRM Hygiene

Regularly validate CRM contacts to maintain deliverability rates.

Lead Scoring

Use validation status as a lead quality signal in your scoring models.


Fair Use and policy

All API use is subject to Fair Use, published plan allowances, and provider, security and abuse safeguards. Low yield alone is advisory and does not change published outcome billing.

Credit balances and recorded validity are shown in Billing and Credits history. Existing credits keep their recorded terms. Negotiated agreements retain their written credit terms. See Terms of Service and Credits & Pricing.