Name: Email Validation API: Verify & Cleanse Email Addresses
Brand: devtoolbox
SKU: api-devtoolbox-email-validator-api
Availability: InStock
Author: API Market


# ✅ Email Validation API

## Overview
The Email Validation API provides a comprehensive solution for verifying email addresses in real-time. It goes beyond simple syntax checks by performing multi-layered validations, including MX record verification, disposable email detection, typo suggestions, and confidence scoring. This ensures high data quality and reduces bounce rates, leading to improved deliverability and campaign performance.

## Features

*   **Syntax Validation**: Checks email format according to RFC 5322 specifications, providing detailed error messages for malformed addresses.
*   **MX Record Verification**: Performs real-time DNS lookups to confirm the recipient domain has valid mail exchange servers configured and is capable of receiving email.
*   **Disposable Email Detection**: Identifies temporary or throwaway email addresses from a regularly updated blocklist of 50+ known disposable email providers.
*   **Typo Suggestions**: Offers smart suggestions for common misspellings of popular email domains (e.g., gmial.com to gmail.com).
*   **Confidence Scoring**: Returns a 0-100 confidence score based on the combined results of all validation checks, enabling informed decisions about email quality.
*   **Bulk Validation**: Validate up to 100 email addresses in a single API call using parallel processing for optimized throughput.

## Use Cases

*   **E-commerce User Registration:** Validate email addresses during signup to minimize bounces and improve customer communication. Catch typos early to ensure order confirmations and shipping updates reach the intended recipients.

*   **Marketing Lead Generation:** Clean and verify prospect email lists prior to launching marketing campaigns.  Identify invalid and disposable emails to maximize campaign ROI and protect sender reputation.

*   **SaaS Platform Onboarding:** Verify the validity of email addresses provided by new users during the sign-up process.  Block disposable emails to prevent fraudulent accounts and trial abuse.

## Visual Examples

Here is an example of an output showing an invalid email
```json
{
    "email": "test@malformed",
    "valid": false,
    "score": 0,
    "checks": {
        "format": {
            "valid": false,
            "reason": "email.invalid_format"
        },
        "domain": {
            "exists": false,
            "hasMx": false,
            "mxRecords": []
        },
        "flags": {
            "isDisposable": false,
            "isRoleBased": false,
            "isFreeProvider": false
        },
        "suggestion": null
    }
}
```

Here is an example of an output showing a valid email.
```json
{
    "email": "test@gmail.com",
    "valid": true,
    "score": 100,
    "checks": {
        "format": {
            "valid": true,
            "reason": "email.valid_format"
        },
        "domain": {
            "exists": true,
            "hasMx": true,
            "mxRecords": [
                "gmail.com.mx",
                "alt1.gmail-smtp-in.l.google.com",
                "alt2.gmail-smtp-in.l.google.com",
                "alt3.gmail-smtp-in.l.google.com",
                "alt4.gmail-smtp-in.l.google.com",
                "gmail-smtp-in.l.google.com"
            ]
        },
        "flags": {
            "isDisposable": false,
            "isRoleBased": false,
            "isFreeProvider": true
        },
        "suggestion": null
    }
}
```

## Pricing

*   1 API unit equals 1 email address processed.
*   GET requests to check prediction status (GET /api/v1/magicapi/email-validator-api/predictions/{id}) are free and don't count toward API unit usage.
*   Different pricing tiers are available based on usage volume.

## API Documentation

### Base URL

All API requests should be made to: `https://prod.api.market/api/v1/magicapi/email-validator-api`

### Authentication

Authentication is handled via API key. Include your API key in the request header:

```
x-api-market-key: YOUR_API_MARKET_KEY
```

### Endpoints

#### 1. /meta

*   **Method:** GET
*   **Description:** Retrieves API metadata, including version, supported features, and the number of disposable email providers in the blocklist.
*   **Request:**

    ```bash
    curl -X GET "https://prod.api.market/api/v1/magicapi/email-validator-api/meta" -H "x-api-market-key: YOUR_API_MARKET_KEY"
    ```

*   **Response (Example):**

    ```json
    {
      "version": "1.0.0",
      "features": [
        "syntax_validation",
        "mx_record_verification",
        "disposable_email_detection",
        "typo_suggestions",
        "confidence_scoring",
        "bulk_validation"
      ],
      "disposable_provider_count": 50
    }
    ```

#### 2. /validate

*   **Method:** GET/POST
*   **Description:** Validates a single email address with comprehensive analysis. The GET method takes the email as a query parameter, while the POST method takes a JSON body.
*   **GET Request Example:**

    ```bash
    curl -X GET "https://prod.api.market/api/v1/magicapi/email-validator-api/validate?email=test@example.com" -H "x-api-market-key: YOUR_API_MARKET_KEY"
    ```

*   **POST Request Example:**

    ```bash
    curl -X POST "https://prod.api.market/api/v1/magicapi/email-validator-api/validate" -H "Content-Type: application/json" -H "x-api-market-key: YOUR_API_MARKET_KEY" -d '{"email": "test@example.com"}'
    ```

*   **Response (Example):**

    ```json
    {
      "email": "test@example.com",
      "valid": true,
      "score": 95,
      "checks": {
        "format": {
          "valid": true,
          "reason": "email.valid_format"
        },
        "domain": {
          "exists": true,
          "hasMx": true,
          "mxRecords": [
            "mail.example.com"
          ]
        },
        "flags": {
          "isDisposable": false,
          "isRoleBased": false,
          "isFreeProvider": false
        },
        "suggestion": null
      }
    }
    ```

#### 3. /bulk

*   **Method:** POST
*   **Description:** Validates up to 100 email addresses in a single request.  The request body should contain either an array of email strings or an object with an "emails" property containing the array.
*   **Request Example (Array of Emails):**

    ```bash
    curl -X POST "https://prod.api.market/api/v1/magicapi/email-validator-api/bulk" -H "Content-Type: application/json" -H "x-api-market-key: YOUR_API_MARKET_KEY" -d '["test1@example.com", "test2@gmail.com", "invalid@malformed"]'
    ```

*   **Request Example (Object with Emails Property):**

    ```bash
    curl -X POST "https://prod.api.market/api/v1/magicapi/email-validator-api/bulk" -H "Content-Type: application/json" -H "x-api-market-key: YOUR_API_MARKET_KEY" -d '{"emails": ["test1@example.com", "test2@gmail.com", "invalid@malformed"]}'
    ```

*   **Response (Example):**

    ```json
    {
      "total": 3,
      "valid": 2,
      "invalid": 1,
      "results": [
        {
          "email": "test1@example.com",
          "valid": true,
          "score": 95,
          "checks": {
            "format": {
              "valid": true,
              "reason": "email.valid_format"
            },
            "domain": {
              "exists": true,
              "hasMx": true,
              "mxRecords": [
                "mail.example.com"
              ]
            },
            "flags": {
              "isDisposable": false,
              "isRoleBased": false,
              "isFreeProvider": false
            },
            "suggestion": null
          }
        },
        {
          "email": "test2@gmail.com",
          "valid": true,
          "score": 100,
          "checks": {
            "format": {
              "valid": true,
              "reason": "email.valid_format"
            },
            "domain": {
              "exists": true,
              "hasMx": true,
              "mxRecords": [
                "gmail.com.mx",
                "alt1.gmail-smtp-in.l.google.com",
                "alt2.gmail-smtp-in.l.google.com",
                "alt3.gmail-smtp-in.l.google.com",
                "alt4.gmail-smtp-in.l.google.com",
                "gmail-smtp-in.l.google.com"
              ]
            },
            "flags": {
              "isDisposable": false,
              "isRoleBased": false,
              "isFreeProvider": true
            },
            "suggestion": null
          }
        },
        {
          "email": "invalid@malformed",
          "valid": false,
          "score": 0,
          "checks": {
            "format": {
              "valid": false,
              "reason": "email.invalid_format"
            },
            "domain": {
              "exists": false,
              "hasMx": false,
              "mxRecords": []
            },
            "flags": {
              "isDisposable": false,
              "isRoleBased": false,
              "isFreeProvider": false
            },
            "suggestion": null
          }
        }
      ]
    }
    ```

#### 4. /health

*   **Method:** GET
*   **Description:**  Performs a health check on the API to ensure it's running and available.
*   **Request:**

    ```bash
    curl -X GET "https://prod.api.market/api/v1/magicapi/email-validator-api/health" -H "x-api-market-key: YOUR_API_MARKET_KEY"
    ```

*   **Response:**  A successful response (200 OK) indicates the API is healthy.

## Status Codes

*   **200 OK:** Request successful. The API executed the request without issues.
*   **201 Created:** Resource successfully created (not used in this API).
*   **400 Bad Request:** Invalid input parameters or malformed request.  Review the request body and query parameters for errors.
*   **401 Unauthorized:** Missing or invalid API key. Ensure the `x-api-market-key` header is present and contains a valid API key.
*   **403 Forbidden:** Valid API key but insufficient permissions. The API key may not have the necessary access rights for the requested operation.
*   **404 Not Found:** Resource not found. The requested endpoint does not exist. Double-check the endpoint URL.
*   **429 Too Many Requests:** Rate limit exceeded. You have exceeded the allowed number of requests within the current time window.  Implement rate limiting and backoff strategies.
*   **500 Internal Server Error:** Server-side error.  An unexpected error occurred on the server.  Contact support if the issue persists.
*   **503 Service Unavailable:** Service temporarily unavailable.  The service is currently unavailable due to maintenance or overload.  Retry the request after a short delay.

## Rate Limits

Rate limits are based on your subscription tier. The free tier includes 100 requests/day. Paid plans offer higher throughput suitable for bulk validation workflows. When the rate limit is exceeded the API returns a 429 status code.

## Error Handling

The API returns error responses in JSON format.  The `error` object provides details about the error, including a code and a message.

```json
{
  "error": {
    "code": "invalid_parameter",
    "message": "The parameter 'email' is required",
    "status": 400
  }
}
```

Common errors and how to resolve them:

*   **invalid\_parameter:**  A required parameter is missing or invalid. Check the request and ensure all required parameters are present and of the correct type.
*   **invalid\_api\_key:**  The API key is invalid or missing.  Ensure the `x-api-market-key` header is included in the request and that the API key is valid.
*   **rate\_limit\_exceeded:**  The rate limit has been exceeded.  Reduce the number of requests or upgrade to a higher subscription tier.
*   **internal\_server\_error:** An unexpected error occurred on the server. Try the request again.  If the issue persists, contact support.

Recommended retry strategies for transient errors (e.g., 503 Service Unavailable):

*   Implement exponential backoff:  Wait for an increasing amount of time between retries to avoid overwhelming the server.


### Performance Optimization

*   Use the bulk validation endpoint (`/bulk`) for validating multiple email addresses to minimize the number of API calls.
*   Implement caching to store validation results for frequently checked email addresses.
*   Monitor your API usage and adjust your subscription tier as needed to avoid rate limiting.

## FAQ

**Q: What happens if I exceed my rate limit?**
A: You will receive a 429 Too Many Requests error. You should implement a retry mechanism with exponential backoff or upgrade to a higher subscription tier.

**Q: How often is the disposable email provider list updated?**
A: The disposable email provider list is updated regularly to ensure accurate detection of temporary email addresses.

**Q: What is the maximum number of email addresses I can validate in a single bulk request?**
A: You can validate up to 100 email addresses in a single bulk request.

**Q: What does the confidence score represent?**
A: The confidence score represents the overall validity of the email address, based on the combined results of all validation checks. A higher score indicates a higher likelihood that the email address is valid and deliverable.

## Contact Us

If you have any questions or need assistance, you can reach out to us through the embedded chat on the bottom right corner of the page or send an email to hello@api.market.
```

Validate email addresses with syntax, MX, disposable & typo checks. Improve deliverability, reduce bounces with our Email Validation API.