Email Validation Score API

API ID 15180

Score an email with syntax, MX, disposable-domain, role-account, free-provider, and typo checks. No message is sent.

197 ms avg response

API Documentation

Endpoints

Request
Validates an email address passed as a query parameter and returns a 0-100 score, a verdict and the syntax, MX, disposable and role checks.
Endpoint ID: 40587
GET https://zylalabs.com/api/15180/email+validation+score+api/40587/validate+get
INPUT PARAMETERS

Validate Get — Endpoint Features

Object Description
email Required The email address to validate, for example [email protected].

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

email
API EXAMPLE RESPONSE
JSON
{
    "ok": true,
    "data": {
        "email": "[email protected]",
        "normalized": "[email protected]",
        "syntax_valid": true,
        "domain": "gmail.com",
        "mx_found": true,
        "mx_records": [
            {
                "priority": 5,
                "host": "gmail-smtp-in.l.google.com"
            },
            {
                "priority": 10,
                "host": "alt1.gmail-smtp-in.l.google.com"
            },
            {
                "priority": 20,
                "host": "alt2.gmail-smtp-in.l.google.com"
            },
            {
                "priority": 30,
                "host": "alt3.gmail-smtp-in.l.google.com"
            },
            {
                "priority": 40,
                "host": "alt4.gmail-smtp-in.l.google.com"
            }
        ],
        "mx_provider": "Google Workspace",
        "disposable": false,
        "role_account": false,
        "free_provider": true,
        "suggestion": null,
        "did_you_mean": null,
        "catch_all": "unlikely",
        "smtp_probe": "disabled",
        "score": 80,
        "verdict": "valid",
        "signals": [
            "syntax_valid",
            "mx_found",
            "free_provider"
        ]
    },
    "meta": {
        "request_id": "4a3128886e8e4028ad9b845e0c5fb1ed",
        "api": "email-validation",
        "version": "1",
        "elapsed_ms": 11,
        "llm_used": false,
        "cache_hit": false,
        "warnings": [],
        "plan": null
    }
}
Validate Get — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/15180/email+validation+score+api/40587/[email protected]' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request
Validates one email address sent as a JSON body and returns a 0-100 score, a verdict and the syntax, MX, disposable and role checks.
Endpoint ID: 40588
POST https://zylalabs.com/api/15180/email+validation+score+api/40588/validate+post
INPUT PARAMETERS

Validate Post — Endpoint Features

Object Description
Request Body Required Json

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

API EXAMPLE RESPONSE
JSON
{
    "ok": true,
    "data": {
        "email": "[email protected]",
        "normalized": "[email protected]",
        "syntax_valid": true,
        "domain": "gmail.com",
        "mx_found": true,
        "mx_records": [
            {
                "priority": 5,
                "host": "gmail-smtp-in.l.google.com"
            },
            {
                "priority": 10,
                "host": "alt1.gmail-smtp-in.l.google.com"
            },
            {
                "priority": 20,
                "host": "alt2.gmail-smtp-in.l.google.com"
            },
            {
                "priority": 30,
                "host": "alt3.gmail-smtp-in.l.google.com"
            },
            {
                "priority": 40,
                "host": "alt4.gmail-smtp-in.l.google.com"
            }
        ],
        "mx_provider": "Google Workspace",
        "disposable": false,
        "role_account": false,
        "free_provider": true,
        "suggestion": null,
        "did_you_mean": null,
        "catch_all": "unlikely",
        "smtp_probe": "disabled",
        "score": 80,
        "verdict": "valid",
        "signals": [
            "syntax_valid",
            "mx_found",
            "free_provider"
        ]
    },
    "meta": {
        "request_id": "84612ca167c94b32874dc0aec2fe0341",
        "api": "email-validation",
        "version": "1",
        "elapsed_ms": 20,
        "llm_used": false,
        "cache_hit": false,
        "warnings": [],
        "plan": null
    }
}
Validate Post — CODE SNIPPETS

curl --location --request POST 'https://zylalabs.com/api/15180/email+validation+score+api/40588/validate+post' --header 'Authorization: Bearer YOUR_API_KEY' 

--data-raw '{"email":"[email protected]"}'

    
Request
Validates a batch of email addresses sent as a JSON body and returns a score and verdict for each one.
Endpoint ID: 40589
POST https://zylalabs.com/api/15180/email+validation+score+api/40589/validate+bulk
INPUT PARAMETERS

Validate Bulk — Endpoint Features

Object Description
Request Body Required Json

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

API EXAMPLE RESPONSE
JSON
{
    "ok": true,
    "data": {
        "count": 2,
        "results": [
            {
                "email": "[email protected]",
                "normalized": "[email protected]",
                "syntax_valid": true,
                "domain": "gmail.com",
                "mx_found": true,
                "mx_records": [
                    {
                        "priority": 5,
                        "host": "gmail-smtp-in.l.google.com"
                    },
                    {
                        "priority": 10,
                        "host": "alt1.gmail-smtp-in.l.google.com"
                    },
                    {
                        "priority": 20,
                        "host": "alt2.gmail-smtp-in.l.google.com"
                    },
                    {
                        "priority": 30,
                        "host": "alt3.gmail-smtp-in.l.google.com"
                    },
                    {
                        "priority": 40,
                        "host": "alt4.gmail-smtp-in.l.google.com"
                    }
                ],
                "mx_provider": "Google Workspace",
                "disposable": false,
                "role_account": false,
                "free_provider": true,
                "suggestion": null,
                "did_you_mean": null,
                "catch_all": "unlikely",
                "smtp_probe": "disabled",
                "score": 80,
                "verdict": "valid",
                "signals": [
                    "syntax_valid",
                    "mx_found",
                    "free_provider"
                ]
            },
            {
                "email": "[email protected]",
                "normalized": "[email protected]",
                "syntax_valid": true,
                "domain": "github.com",
                "mx_found": true,
                "mx_records": [
                    {
                        "priority": 0,
                        "host": "github-com.mail.protection.outlook.com"
                    }
                ],
                "mx_provider": "Microsoft 365",
                "disposable": false,
                "role_account": false,
                "free_provider": false,
                "suggestion": null,
                "did_you_mean": null,
                "catch_all": "unlikely",
                "smtp_probe": "disabled",
                "score": 85,
                "verdict": "valid",
                "signals": [
                    "syntax_valid",
                    "mx_found"
                ]
            }
        ]
    },
    "meta": {
        "request_id": "11fe28125c7741c7bf0d5e86c7d2288d",
        "api": "email-validation",
        "version": "1",
        "elapsed_ms": 28,
        "llm_used": false,
        "cache_hit": false,
        "warnings": [],
        "plan": null
    }
}
Validate Bulk — CODE SNIPPETS

curl --location --request POST 'https://zylalabs.com/api/15180/email+validation+score+api/40589/validate+bulk' --header 'Authorization: Bearer YOUR_API_KEY' 

--data-raw '{"emails":["[email protected]","[email protected]"]}'

    

API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Email Validation Score API simply include your bearer token in the Authorization header.

Headers
Header Description
Authorization Required Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.

Starts at
$10,000/Year


  • Custom Volume
  • Custom Rate Limit
  • Specialized Customer Support
  • Real-Time API Monitoring

Overview

Score an email with syntax, MX, disposable-domain, role-account, free-provider, and typo checks. No message is sent.

Email Validation Score API FAQs

It checks syntax, MX records, a bundled disposable-domain list, role accounts such as info@ and support@, free mailbox providers, and lookalike typos such as gmial.com.

A 0-100 score, a verdict of valid, risky or invalid, and the signals behind the score, including a typo suggestion when one is found.

No. The API never sends a message. An optional SMTP RCPT probe is off by default and never sends message data.

Bulk validation accepts up to 25 addresses per call, and a bulk call counts as one request against your monthly quota.

Send GET /v1/[email protected] with your X-Api-Key header. The JSON response includes the score, verdict and the signals behind it.

The GET Info endpoint provides API information and metadata. Use it to discover general service details before calling validation endpoints. Its response is separate from validation results and does not evaluate an email address.

It accepts one email address in a JSON request body. The response contains one validation object with the submitted email, normalized address, domain, score, verdict, and individual validation signals.

Both validate one email and return comparable results. GET receives the address as a query parameter, such as `[email protected]`; POST receives it in JSON. Choose GET for simple URL-based requests and POST when sending structured request bodies.

`normalized` is the API’s standardized form of the submitted address, useful for consistent storage and comparison. `domain` is the portion after the `@`, such as `gmail.com`, and is used for MX, disposable-domain, and provider checks.

`mx_found` indicates whether the domain publishes mail-exchange records. When available, `mx_records` lists each record’s priority and host, while `mx_provider` identifies the detected mail provider, such as Google Workspace. An absent MX result indicates the domain may not accept email.

These fields identify a possible spelling correction when the address or domain resembles a known provider but contains a typo. A null suggestion means no correction was detected. Treat suggestions as review guidance rather than an automatic replacement.

Iterate through the `results` array and evaluate each address using its score, verdict, and signals. For example, retain high-scoring addresses, review risky ones, and correct or reject invalid entries. Do not assume every item in a successful bulk response has the same result.

General FAQs

To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.

You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.

The free trial lasts for 7 days and allows you to make up to 50 API requests.

No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.

Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.

Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world's most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

You can monitor your API usage through the response headers included with every request:

x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.

The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.

Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.

Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

Please have a look at our Refund Policy: https://zylalabs.com/terms#refund


Related APIs