Validate Email
Verify email addresses with SMTP checks and engagement signals. Returns clear valid, invalid, or unknown statuses.
https://api.leadmagic.io/v1/people/email-validationTry this endpointOpen the API playground
Deciding how to verify? See the Email Verification product page or the guide How to Verify an Email Address: 5 Methods That Actually Work.
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
- Pricing
- Rate Limits
| Metric | Value |
|---|---|
| Cost | 0.25 credits per definitive validation |
| Calculation | 4 definitive validations = 1 credit |
| Free Outcomes | unknown results and malformed inputs rejected with HTTP 400 |
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
The email address to validate. Must be a properly formatted email address.
Response
The validated email address (normalized)
Validation result: valid, invalid, or unknown
Credits used for this request (0.25 for valid/invalid, 0 for unknown)
Human-readable status message
Primary MX record for the domain
Email provider (Google Workspace, Microsoft 365, etc.)
Security gateway vendor name (null if none)
Security gateway type (null if none)
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 result | Suggested routing | Credits |
|---|---|---|
| valid | Eligible for your sending policy after consent and suppression checks. | 0.25 |
| invalid | Suppress the address and look for a corrected address if needed. | 0.25 |
| unknown | Hold 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.
| Case | Example | Result |
|---|---|---|
Missing @ symbol | johncompany.com | HTTP 400 (free) |
| Whitespace inside the address | john@comp any.com | HTTP 400 (free) |
| Missing domain | john@ | HTTP 400 (free) |
| Consecutive dots | john..doe@company.com | HTTP 400 (free) |
| Missing top-level domain | john@company | HTTP 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
| Message | Status | Cost |
|---|---|---|
Email is valid. | valid | 0.25 |
Email is invalid. | invalid | 0.25 |
Invalid email: … (definitive result, e.g. a reserved domain) | invalid | 0.25 |
Unable to verify email status. | unknown | FREE |
Best Practices
Pre-validate format client-side
Pre-validate format client-side
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.
Validate before sending campaigns
Validate before sending campaigns
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.
Handle unknown results
Handle unknown results
For unknown results, consider retrying later or using Email Finder to verify the specific address exists before adding to campaigns.
Batch your validations
Batch your validations
For large lists, batch your requests to stay within rate limits. Use the response headers to monitor your remaining quota.
Use response headers for monitoring
Use response headers for monitoring
Every response includes X-Credits-Remaining so you can track spending without extra API calls.
Allow time for validation
Allow time for validation
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.