Exciting New Features Added to Our Email Verification API - Version 2.4

The latest release of our email verification API comes packed with some cool new features, including the ability to recognize parked or inactive mail exchangers, configurable waiting times, relaxed HTTP 429 status codes, and improved completion callback options. Read on to find out more!

February 21, 2023

Hey there!

We're super stoked to let you know that we've just released version 2.4 of our email verification API for all you awesome developers out there! If you are not a developer, there is no need to fret as all the features mentioned below are readily available in our web-based client area.

So, we've added some really cool new features to our email verification engine that we think you're gonna love:

Parked / inactive mail exchangers

Now our API can recognize parked or inactive mail exchangers, which are associated with email traffic collection and resale. We've integrated a new status code called MailExchangerIsParked to help you avoid accepting email addresses hosted by these kinds of exchangers on your sign-up forms or contact lists.

Configurable waiting time

We've also made it possible for you to adjust the waiting time while submitting and retrieving email verification jobs, so you can speed up the email verification processing and minimize the number of polling requests. This new configuration option allows you to enqueue data and leave the actual results handling to another component or microservice of your architecture.

Here is how, for instance, you can verify a single email address through our developers API using cURL, enabling the server to delay the initial response for up to 3 seconds through the waitTime query string parameter and allowing to provide the verification concurrently with the first response, if possible:

curl -u username:password \
    -H "Content-Type: application/json" \
    -d "{ entries: [ { inputData: 'batman@gmail.com' } ] }" \

On the other side, passing the value 0 through the waitTime query string parameter forces the Verifalia API to avoid waiting for the job completion and immediately returns an HTTP 202 status code, meaning the verification job has been enqueued successfully.

Relaxed HTTP 429 status code

We used to limit the number of concurrent API invocations on our API endpoints, but we've made some improvements to our service architecture and can now handle a much higher volume of email verification submissions. So we've waived the previous limit on the number of concurrent email verification submissions and are now applying a much more relaxed API limit.

New completion callback options

With version 2.4 of our API, we've improved our completion callback processing to return the user-defined name of a job along with its callback, so you can pass a custom per-job token and get it in the callback itself without having to retrieve the job snapshot. We are also now allowing to bypass the server certificate validation while performing the callback POST request - although, for security reasons, this should only be used during the development and testing phase of your integration.

For example, here is how you can instruct the Verifalia API to pass the user-defined job name while issuing the completion callback, by forcing it to obey to the new callback schema version 1.1:

curl -u username:password \
    -H "Content-Type: application/json" \
    -d "{ entries: [ { inputData: 'batman@gmail.com' } ],
		    callback: { url: 'https://somewhere/foo/bar', version: '1.1' }
        }" \

You are already in love with it, aren't you?


If you want to know more about these awesome new API features, be sure to check out our developers documentation and feel free to contact us anytime if you need any help.

Need Help?

We're here to assist you.

Visit Our Help Center
Explore our collection of technical and non-technical articles about Verifalia's services.
Send Us a Message
Reach out to us with any questions or comments. Support is always free of charge.

Want to chat?
Click the button below to chat live with one of our support team right now.