Skip to main content
POST
Validate Email Addresses
This endpoint validates email addresses using two different methods: direct email validation or file-based validation. You can either provide individual email addresses or reference a previously uploaded file.

Validation Methods

Validate individual email addresses by providing them directly in the request.

How it Works

1

Choose Validation Method

Decide whether to validate individual emails directly or use a file-based approach
2

For File-Based: Upload File First (Optional)

If using file-based validation, first upload your CSV or XLSX file using the File Upload endpoint to obtain the file_id
3

Configure Validation Options

Set your desired validation options (syntax, DMARC, SMTP, MX records)
4

Submit Validation Request

Send either emails array OR file_id (not both)
5

Receive Results

Get validation results for the submitted emails

Request Parameters

Either/Or Requirement: You must provide either emails OR file_id, but not both in the same request.

Direct Email Validation

  • emails: Array of email addresses to validate
  • options: Validation options object

File-Based Validation

  • file_id: ID from a previously uploaded file
  • file_tag: Tag for categorizing the validation type
  • options: Validation options object

Validation Options

Configure which validation checks to perform:
  • validate_syntax: Checks email format and structure (default: true)
  • validate_smtp: Performs SMTP server validation (default: false)
  • check_dmarc: Validates DMARC policy records (default: false)
  • validate_mx: Checks MX record existence (default: false)

Example Workflows

Direct Email Validation

File-Based Validation

Credits Consumption: Validation consumes credits based on the number of emails and validation options selected. More comprehensive validation uses more credits.
Bulk Processing: For validating large lists of emails, use the file-based approach with the File Upload endpoint for better performance and easier management.

Authorizations

X-API-KEY
string
header
required

API key for authentication

Body

application/json

Email validation request payload

emails
string<email>[]

Array of email addresses to validate (required for direct validation)

Example:
file_id
integer

ID of the uploaded file (obtained from file upload response) - required for file-based validation

Example:

740

options
object

Validation options

file_tag
enum<string>

Tag for categorizing the file processing type (required when using file_id)

Available options:
clean,
validate,
analyze
Example:

"validate"

Response

Email validation results

results
object[]
stats
object
file_id
string | null

File ID for batch processing

credits_used
integer

Number of credits consumed

remaining_processing
integer

Remaining emails to process

batch_size
integer

Size of the current batch