Introduction

MailVerify360 service offers a robust solution for ensuring email authenticity, crucial for modern businesses looking to maintain the integrity of their communication and safeguard against fraud. Through the MailVerify360 API, businesses can automate the process of email verification, integrating these checks directly into their sign-up processes, email marketing campaigns, or any other systems where email authenticity is critical.

This documentation will guide you through every step and provide you with all the necessary information to easily integrate the MailVerify360 API into your applications or platforms. Here, you'll find detailed instructions on how to get started, utilize the API, handle potential errors, and much more, designed to get you up and running in no time.

Key Features

MailVerify360 stands out with its comprehensive suite of features aimed at verifying email authenticity. Key features include:

  1. Disposable Email Detection: MailVerify360 identifies disposable and temporary email addresses, helping you maintain a high-quality user base by preventing spam and free trial abuse, as well as enhancing the integrity of every email on your platform.
  2. Email Provider Insights: Our service provides detailed information on email service providers, distinguishing between paid and free services. This insight allows for a deeper understanding of your contacts' authenticity and potential value.
  3. Deliverability Confirmation: We confirm the deliverability of email addresses, verifying they are active and capable of receiving messages. This feature is crucial for optimizing engagement and reducing bounce rates in your email campaigns.
  4. Blacklist Monitoring: MailVerify360 checks mail server IPs against over 100 DNS-based email blacklists (DNSBLs or RBLs). Ensuring your emails reach their intended recipients by avoiding blacklisted servers increases delivery success rates.
  5. MX Record Analysis: Our service analyzes mail exchange (MX) records to provide insights into the email routing infrastructure. Understanding MX records aids in assessing email deliverability and server reliability.
  6. Hourly Updated Databases: MailVerify360 maintains databases that are updated hourly with the latest information on disposable email providers, spam domains, and blacklisted servers. This ensures your verifications are based on the most current data, significantly boosting the accuracy of your email validation efforts and protecting your interactions from emerging threats.

These features are designed to equip your business with the tools needed for effective email authenticity verification and management.

API Authentication

MailVerify360 employs API keys to authenticate requests. Your API key remains valid across all subscription levels. Whether you upgrade, downgrade, or modify your subscription, the same key continues to authenticate your requests without interruption.

Tip

API keys are pivotal to maintaining the security of your transactions with MailVerify360. It is imperative to treat your API key as confidential information. Store your API key in a secure location. Consider using environment variables or encrypted database entries to keep the key safe.

How to Obtain Your API Key
  1. If you haven't already, sign up for an account on our platform. If you're an existing user, simply log in.
  2. From the Dashboard, navigate to the API key management page using the sidebar.
  3. You will find an option to generate your unique API Key.

Warning

For security reasons, our system stores only a hashed version of your API key. This means you won't be able to view or download the key later. Please make sure to save your API key securely when it is displayed. If you lose the key, you will need to regenerate a new one, which will invalidate the previous key.

Structuring Your API Requests

With your API key, you're now equipped to make requests. Construct your endpoint URL by incorporating both pieces of information as follows:

Replace YOUR_API_KEY with your actual key.

Rate Limit

In order to ensure optimal performance and service stability, MailVerify360 implements rate limits on API requests. This measure is crucial for managing sudden surges in traffic and maintaining service quality for all users. For subscriptions subject to rate limits, API responses include three headers to help you monitor your usage:

  • RateLimit-Limit: The total number of requests permitted per minute under your current plan.
  • RateLimit-Remaining: The number of requests left for the current minute window.
  • RateLimit-Reset: The time (in epoch seconds) when the rate limit window resets.

Errors

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

  • 2xx Response Codes: These codes indicate that your request was successful. A 200 OK response, for example, means that the requested operation was successful and you should expect the relevant data in the response.
  • 4xx Response Codes: If you receive a response code in this range, it typically indicates an issue with the request you sent. This could be due to missing information, incorrect parameters, or other client-side errors. For example:
    • A 400 Bad Request might signal a missing required parameter.
    • A 404 Not Found suggests the API endpoint isn't available.

    Along with the status code, responses will include a JSON body providing more context. For instance, if you provide an invalid API key, you might receive a 401 Unauthorized response accompanied by:

  • 5xx Response Codes: Encountering one of these indicates there's an internal problem with MailVerify360's servers. These are rare but can happen. A code like 500 Internal Server Error suggests a generic server-side issue.
A list of possible errors are:
Status Error Code Description
400 InvalidBatchRequestFormat The batch request does not conform to the expected JSON array format. Ensure the input consists of a valid JSON array of email addresses.
400 TooManyEmailAddress The batch request contains more than the permissible limit of 10 email addresses. Reduce the number of emails in the request and try again.
401 MissingApiKey The required api-key query parameter is absent in the request. Include this parameter with a valid API key for authentication.
401 InvalidApiKey The provided api-key does not match any existing user account. Check the API key for any inaccuracies or consult the account dashboard.
403 NoSubscription There is no active subscription associated with the provided credentials. An active subscription plan is required to access the API's features.
403 SubscriptionExpired The subscription to MailVerify360 service has expired. Renewal or purchase of a new subscription is required for continued service access.
404 NoSuchApiExists The requested API endpoint is either invalid or does not exist. Verify the endpoint's path and check the documentation for available endpoints.
429 RateLimitExceeded The allowable request frequency per minute for the current subscription level has been surpassed.
500 ApiServerError There is an internal error in the api server while processing your request.

APIs

MailVerify360 offers two primary API services designed to accommodate different needs and scales of email verification, for businesses of all sizes. Our API suite includes:

  1. Standard Lookup: Tailored for real-time verification of single email addresses. This API is ideal for instant validation needs, such as during user registration, contact form submissions, or any point of single email data capture.
  2. Batch Lookup: Designed for processing an array of emails simultaneously. This API suits bulk verification tasks, allowing applications to clean and validate their email lists efficiently with reduced http request overheads.

Standard Lookup

The Standard Lookup endpoint offers detailed geographical and network information associated with a specific IP address. This API is compatible with both IPv4 and IPv6 address formats.

Request Format:

Request parameters:

Parameter Required Description
emailAddress Yes The email address for which details are sought.
api-key Yes The unique API key generated from your dashboard. This must be included as a query parameter with every request.

Note

The email needs to be URL-encoded. For example, for [email protected] , the endpoint would be /verify/emails/worefim615%40gexige.com. However, in most cases, the library or the http client would take care of this.

API Response:

The response will be a JSON object detailing various attributes about the queried email address. The depth and specifics of the details might vary based on the available information. For an exhaustive list of potential response fields, please refer to the Response Format section.

Batch Lookup

The Batch Lookup endpoint allows querying of upto 10 email addresses in a single request. It returns a JSON array with detailed verification information for each provided email address.

Request Structure:
Request Body:

A JSON array of email addresses. The maximum number of emails that can be included in a single request is 10. If exceeded, a TooManyEmailAddress error response will be returned.

Example Request:
API Response:

The response will be a JSON object detailing various attributes about each of the email addresses. The depth and specifics of the details might vary based on the available information. For an exhaustive list of potential response fields, please refer to the Response Format section.

Response Format

The Standard Lookup API returns a response in the form of a JSON object that encapsulates detailed verification results for the queried email address. This response includes a variety of fields that detail the email's verification status, such as its validity, association with disposable email providers, domain information, and more.

In the case of the Batch Lookup API, the response structure is a JSON array, with each element being akin to the response from the Standard Lookup API for a single email address. This means that for batch queries, each email's verification data is presented as an item within this array.

Find below a list of all available fields in the response object explained.

Some fields in the response may be optionally present, contingent upon the information available for the queried email address. For instance, the securityPolicy field might not appear in every response, particularly if the corresponding DNS entry is lacking for that domain. The fields that may or may not be present are marked as optional in the following table.

Field Name Data Type Description Optional
valid Boolean Indicates whether the email address adheres to a valid format according to standard email formatting rules.
emailAddress String The email address that is currently being verified.
domain String Represents the domain portion of the email address being verified.
disposable Boolean Whether the email address comes from a disposable email provider. A true value indicates the email is temporary and potentially less trustworthy for long-term communication.
deliverable Boolean If the email address is linked to a valid inbox capable of receiving messages. This field helps gauge the practical usability of an email for communication purposes.
blacklisted Boolean If the email domain appears in any of the 100+ DNSBL our system tracks.
provider JSON Object Provides information about the email service provider of the address being verified. This object contains two subfields
provider.name String The name of the email service provider, such as Google or ProtonMail.
provider.type String The service type of the provider, which can be one of the following values:
  • Free
  • Paid
mx JSON Array Contains all Mail Exchange (MX) records associated with the domain of the email address being verified. Each element within this array is a JSON object that provides detailed information about an individual MX record.
mx[].host String The hostname of the mail server specified in the MX record.
mx[].ip String The IP address of the mail server.
mx[].priority Numeric Indicates the priority of the mail server, with lower numbers representing higher priority.
securityPolicy JSON Object Provides insights into the email domain's security configurations such as DMARC etc.
dmarc JSON Object Contains details about the domain's DMARC policy
dmarc.version String Specifies the version of the DMARC policy in use, typically "DMARC1" for current implementations.
dmarc.policy String The general policy recommended by the domain owner for handling emails that fail the DMARC check. Options like "none," "quarantine," and "reject" guide receiving servers on the action to take.
dmarc.subdomainPolicy String Indicates the policy for handling emails from subdomains that fail the DMARC check.
dmarc.dkimSignatureAlignment String Describes how strictly the domain aligns DKIM (DomainKeys Identified Mail) signatures. "Relaxed" alignment allows partial matches, while "strict" requires an exact match.
dmarc.spfAlignment String Specifies the SPF (Sender Policy Framework) alignment, determining how closely the sender's domain must match the domain in the "From" address. Like DKIM alignment, it can be "relaxed" or "strict."
dmarc.aggregateReportDestination String The email address where aggregate DMARC reports should be sent.
dmarc.forensicReportDestination String The email address to which forensic DMARC reports should be sent.
dmarc.reportingFormat String The format used for DMARC reports.
dmarc.reportingInterval String The interval, in seconds, at which DMARC aggregate reports should be sent to the designated recipient.
dmarc.percentage String Represents the percentage of emails to which the DMARC policy should be applied.

Code Samples

This section illustrates snippets to get you started with the MailVerify360 APIs. These samples are designed to demonstrate fundamental concepts and offer a quick understanding of how to integrate the API into your applications. However, it's essential to recognize that these examples are meant purely for educational purposes. If you're considering adapting any of these snippets for production, ensure that you understand the code thoroughly and have taken necessary precautions, like error handling and optimization, to meet the specific requirements and standards of your project.

cURL

Java

Python