Skip to main content
Email Validation helps you decide whether an address should enter your product, contact list, or sending workflow. MailGlyph checks syntax, domain health, MX records, disposable domains, personal domains, plus addressing, random-looking local parts, typo suggestions, and SMTP mailbox status when available. Use a secret API key (sk_...) for all Email Validation API and SDK calls.
Never run Email Validation from browser code with a secret key. Call MailGlyph from your backend or serverless function.

Validate one address

Use single-email validation when a user signs up, submits a form, or changes an email address.
A successful response includes an overall valid boolean and detailed signals:

Interpret results

Use valid for the first decision, then inspect the detailed fields for product-specific rules.
Treat Catch All and Grey-listed as deliverable but lower-confidence results. They consume one validation credit because MailGlyph completed SMTP-level validation.

Validate a file

Use bulk validation for contact imports, list cleanup, or scheduled hygiene jobs. Upload a TXT, CSV, or XLSX file up to 90MB.
The response is a job record. Store the id and poll it from your backend.

Poll and download results

When status is COMPLETED and readyForDownload is true, download the results:
Download filters are all, valid, invalid, unknown, and catchall. Filtered downloads are CSV only. XLS is available only when filter=all.

Continue jobs that need credits

Bulk jobs reserve credits from the detected email count. If a job pauses with ACTION_REQUIRED, add credits in the dashboard, then continue it:
Unknown and duplicate emails are not charged in the final reconciliation.

Check credits and ledger

Check the current project balance:
Review recent credit activity with cursor pagination:
Ledger responses do not include raw email addresses.

Use the SDKs

The official SDKs expose an Email Validation client for single and bulk validation: For endpoint details, see the Email Validation API reference.