verifi.email

API Documentation

Welcome to the verifi.email API documentation. Our REST API allows you to easily validate email addresses with high accuracy and performance.

Authentication

To use the verifi.email API, you need an API key. You can obtain a key by signing up for an account. Include your API key in all requests by appending the token=<your-api-key> query param.

Validate a single email

Validate a single email address to determine its deliverability and validity.

Request

GET /v1/validate

Query Parameters

Parameter	Description
`token`	Your API token
`email`	The email address to validate
`format[valid]`	(optional) Formats the response's valid field when true. e.g. `format[valid]=YES`
`format[-valid]`	(optional) Formats the response's valid field when false. e.g. `format[-valid]=NO`

Response

Returns a JSON object with validation results.

Domain health check

This API helps you assess the health of your domain by providing scores and actionable recommendations for essential email authentication protocols, including DKIM, DMARC, SPF, and BIMI. With this information, you can enhance your domain's email security and deliverability.

Request

POST /v1/domain/check

Query Parameters

Parameter	Description
`token`	Your API token
`domain`	The domain you would like to check. Without `https://` or `www`.
`selector`	(optional) When choosing a DKIM selector, select a unique identifier that aligns with your email provider, such as "google" for Google or "default" for others. This helps ensure that your DKIM signature can be correctly verified by recipients.

Response

Returns a JSON object describe the health of your domain, including recommendations.

Response Codes

Our API uses conventional HTTP response codes to indicate the success or failure of an API request.

Code	Description
`200`	OK - Everything worked as expected
`400`	Bad Request - Invalid parameters or request format
`401`	Unauthorized - Invalid API key
`402`	Payment Required - Account has exceeded quota or is past due
`429`	Too Many Requests - Rate limit exceeded
`500`	Server Error - Something went wrong on our end

Rate Limits

Rate limits vary by plan. The current rate limit is returned in the response headers:

Header	Description
`X-RateLimit-Limit`	Number of requests allowed in the time window
`X-RateLimit-Remaining`	Number of requests remaining in the current window
`X-RateLimit-Reset`	Unix timestamp when the rate limit resets

Code Examples

JavaScript

Python

Need Help?

If you have any questions or need assistance with our API, please contact our support team at [email protected].