Global Email:V3 Deprecation
Jump to navigation
Jump to search
Melissa Data has recently announced the deprecation of Global Email V3 service with the transition to our V4 service. The new version has additional features and improvements to help improve email accuracy, speed, stability and more feature updates in the future.
Improvements
- This service has several improvements, including:
- Improved Speeds
- We made significant investments in our email validation cloud infrastructure, focusing on stability, reliability and speed improvements.
- Improved Disposable Domain Detection
- We implemented an automatic disposable domain feed and expanded our database of known disposable domains.
- Improved MX Level Validation
- We have made improvements at the MX server level to identify issues at the domain level more accurately, resulting in quicker validations for invalid mail servers. We leverage additional logic to determine if the provider is having a temporary outage at the domain level.
- Improved Domain Correction
- We made significant improvements and reworked our domain correction algorithm with the goal of reducing false corrections. We plan to expand domain corrections to include more popular domains on a periodic basis.
- Improved DeliveryConfidenceScore Accuracy
- We’ve implemented new, dynamic logic to improve the accuracy of the delivery confidence scores.
- With major changes to our email validation architecture, it is no longer feasible for Melissa Data to support the older Global Email V3 Web Service. The Global Email V3 Web Service is being deprecated and the service will no longer be accessible after February 6th, 2023. We are confident you will find that our Global Email V4 Web Service can do everything the old service did, and more. Please switch over to our new web service as soon as possible.
Access and License
- All existing Global Email Web Service subscribers will automatically be given access to our Global Email V4 web service. When using the V4 service, the same License Key can be used. All royalties according to the subscription agreement will remain the same.
Data Differences
- To ensure no loss of data, all data fields in Global Email V3 will also be available in Global Email V4. These fields are:
- Version
- Transmission Reference
- Transmission Results
- Total Records
- Record ID
- Results
- Email Address
- Mailbox Name
- Domain Name
- Top Level Domain
- Top Level Domain Name
- Date Checked
- Additionally, the Global Email V4 Web Service comes with the following data fields:
Response Field Description EmailAgeEstimated The estimated minimum age of the email in days based on historical data. The value is zero when we lack historical data on a given email. DeliverabilityConfidenceScore Returns the probability [0-100]% of an email sent to this mailbox will be successfully delivered. DomainAgeEstimated The estimated age of the domain in days. DomainExpirationDate The date the domain expires/expired in the YYYY-MM-DDTHH:MM:SS format. DomainCreatedDate The date the domain was created in the YYYY-MM-DDTHH:MM:SS format. DomainEmail The email associated with the domain. DomainOrganization The organization associated with the domain. DomainAddress1 The street address associated with the domain. DomainLocality The locality associated with the domain. DomainAdministrativeArea The administrative area associated with the domain. DomainPostalCode The postal code associated with the domain. DomainCountry The country associated with the domain. DomainCountryCode The country code associated with the domain. DomainAvailability Check to see if the domain is available for purchase. DomainPrivateProxy Check if the domain is behind a private proxy. PrivacyFlag The top level domain may be sensitive to privacy laws. Returns Y for yes and N for no. MXServer Returns which Mail Exchange (MX) Server was used to validate the email. DomainAuthenticationStatus Returns security protocols used on the receiving mail server DomainTypeIndicator Predicts if email belongs to a personal or business/organization email by analyzing the domain. BreachCount* (Coming soon late 2022 or early 2023) Returns the known number of breaches that this email account has been involved in. *Available late 2022 or early 2023
- When switching over to Global Email V4 Web Service, you automatically have access to the new fields.
Protocols and URL/Endpoints
- Global Email V4 is now only limited to REST for requests. SOAP is no longer supported. You can perform batch querying only in POST JSON or XML. There is only one service point for both REST and JSON.
Protocol URL REST, JSON/XML https://globalemail.melissadata.net/V4/WEB/GlobalEmail/doGlobalEmail
REST Transition
- The REST request for Global Email V4 remains the same, except for service endpoints. Here is a comparison between the old service and the new service:
Global Email V3
Global Email V4
- Note: The response for both REST and POST JSON/XML will always return as JSON or XML depending on the format option parameter that is set.
- The reference guide and sample code in the Global Email V4 wiki pages also show how to correctly make a REST request and parse the JSON or XML response.
SOAP and XML Transition
- The SOAP Protocols in Global Email V4 Web Service have been deprecated and are currently not available at this time. This is a design decision made in order to accommodate JSON, which is a relatively newer technology and has grown in popularity.
- JSON offers a more flexible web service response structure and supports a dynamic structure in the response. This allows for a more optimal response with less overhead. It also allows for the addition of new output elements without having to re-consume the web service, which is typically an issue when bound by a statically defined structure or WSDL.
JSON Protocol
- The JSON Protocol provides an intuitive and simple way to define the requests and responses.
- Below is an example of a JSON request to our Global Email V4 Web Service:
{
"TransmissionReference": "string",
"CustomerID": "string",
"Options": "string",
"Records": [
{
"RecordID": "string",
"Email": "string"
},
- Below is an example of a JSON response:
{
"Version":"string",
"TransmissionReference":"string",
"TransmissionResults":"string",
"TotalRecords":"string",
"Records":[{
"RecordID":"string",
"DeliverabilityConfidenceScore":"string",
"Results":"string",
"EmailAddress":"string",
"MailboxName":"string",
"DomainName":"string",
"TopLevelDomain":"string",
"TopLevelDomainName":"string",
"DateChecked":"string",
"EmailAgeEstimated":"string",
"DomainAgeEstimated":"string",
"DomainExpirationDate":"string",
"DomainCreatedDate":"string",
"DomainUpdatedDate":"string",
"DomainEmail":"string",
"DomainOrganization":"string",
"DomainAddress1":"string",
"DomainLocality":"string",
"DomainAdministrativeArea":"string",
"DomainPostalCode":"string",
"DomainCountry":"string",
"DomainCountryCode":"string",
"DomainAvailability":"string",
"DomainPrivateProxy":"string",
"PrivacyFlag":"string",
"MXServer":"string"
}]
}
- Similar to the request, the response is formatted in the same way with each variable clearly and intuitively labeled in the JSON Response. All previous data fields in the Global Email V3 Web Service are accessible in V4.
Interpreting Results
- The complete list of result codes for Global Email V4 Web Service can be found here: Global Email Result Codes.
- The result codes for V3 and V4 are identical with the exception of the following:
- Result code ES02 is no longer present. Please use EEXX codes instead to identify bad emails.
- We now recommend leveraging the deliverability confidence scores to decide your business logic for email validations. Please see Deliverability Confidence Score for more information. However, the existing result codes may still be used if you prefer to fine tune the logic based on the multiple statuses or flags.