Articles on: API

API Migration from Email Checker

This information is specifically for users migrating from the Email Checker API.

Please review the following breaking changes listed below when migrating from Email Checker to Emailable. Our API will remain mostly the same and likely will require minimal or no changes for a majority of our users. All endpoints will remain the same unless otherwise stated below. There are no plans to deprecate this API at any time in the future beyond the changes listed here.

Please note that Email Checker API endpoints will only work when using API Keys migrated from Email Checker. Emailable API Keys will not work with Email Checker API endpoints.

Breaking Changes

General

Rate limits are now 25 / second / API Key for all endpoints. If you need higher rate limits, please contact support.

All endpoints are case-sensative. Please make sure you're using lowercase endpoints.

V1 API

Authentication

Acess Control List (ACL) authentication has been removed. If you need to use the API in a public setting, please migrate to the Emailable API and use a Public API key.

Batch API

PUT https://upload.emailverifyapi.com/batchapi/v1

GET https://upload.emailverifyapi.com/batchapi/v1

These endpoints have been removed. We recommend you switch to the Emailable Batch API, which returns a more comprehensive set of verification data.

Usage

https://api.emailverifyapi.com/api/a/v1?usage=1

The following changes will be reflected when requesting your usage:

The monthQuota and monthQuotaRemaining fields will now reflect your credit balance, because there are no monthly quotas in Emailable.

V3 API

Authentication

Acess Control List (ACL) authentication has been removed. If you need to use the API in a public setting, please migrate to the Emailable API and use a Public API key.

Real-Time API

GET https://api.emailverifyapi.com/v3/lookups/jsonp

GET https://api.emailverifyapi.com/v3/lookups/xml

JSONP and XML response formats have been removed.

Usage

GET https://api.emailverifyapi.com/v3/lookups/json?usage=1

The following changes will be reflected when requesting your usage:

The monthQuota and monthQuotaRemaining fields will now reflect your credit balance, because there are no monthly quotas in Emailable.

Non Breaking Changes

The following endpoints should function exactly how they did prior to the migration, besides the non breaking changes listed below.

If you encounter any differences that are not documented here, please email api-bugs@emailable.com with a detailed explanation of the difference. Please include the full request and response, including all headers and all information necessary for our team to replicate the issue.

V1 API

Real-Time API

GET https://api.emailverifyapi.com/api/a/v1

The emailAddressSuggestion key will return a suggestion if one is available, regardless of whether the correct parameter is sent in the request.

V3 API

Real-Time API

GET https://api.emailverifyapi.com/v3/lookups/json

The suggestion key will return a suggestion if one is available, regardless of whether the correct parameter is sent in the request.

Updated on: 07/29/2022

Was this article helpful?

Thank you!