Search the Omeda Knowledge Base

< All Topics

Email Validity Lookup API


This API provides the ability look up the validity of an email address using Email Address.  The response will include the information regarding the email validity provided by the email validity vendor for a given email address.

General Technical Requirements

The following technical requirements apply to all requests for this API.

Base Resource URI



brandAbbreviation is the abbreviation for the brand. emailAddress is the email address for which we are requesting customer information.

HTTP Headers

The HTTP header must contain the following element: x-omeda-appid a unique id provided to you by Omeda to access your data. The request will fail without a valid id.

Content Type

The content type is application/json. JSON application/json

JSON is the preferred data exchange format, because it is lightweight and, in most cases, faster to process and utilizes less bandwidth. There are many available open-source JSON libraries available. See for details.

Supported HTTP Methods

There is one HTTP method supported:

  1. GET : See W3C’s GET specs for details.

Lookup All Email Validity Codes for Email Address

Retrieves all Email Validity Codes for the email address.

Field Definition

The following table describes the data elements present on the response from the API.

In addition to the below elements, a SubmissionId element will also be returned with all responses. This is a unique identifier for the web services response. It can be used to cross-reference the response in Omeda’s database.

Element NameAlways Returned…Data TypeDescription
EmailValiditiesYesArrayeach EmailValidities element contains the detail for the specific customer.
SubmissionIdYesStringa unique identifier for the web services response. It can be used to cross-reference the response in Omeda’s database.

Customers Elements

Element NameAlways Returned…Data TypeDescription
ValidationDateYesStringDate of when the Email Address was validated by Vendor.
VendorCodeYesStringCode that signifies the validity of the Email Address provided by Vendor.
VendorCodeDescriptionYesStringValidity Code description.
VendorNameYesStringName of Email Validity Vendor.


HTTP Response Codes

It is possible that multiple customers are returned for the same email address. If only one is found, a 200 OK status is returned. If more than one is found, a 300 Multiple Choices status is returned.

200 OKThe request has succeeded. See Example Response below.
300 Multiple ChoicesThis response will be returned when more than one customer was found for that email address. Response body will contain a list of all customers that have that email address.
403 ForbiddenTypically, this error occurs when the credentials are erroneous. Potentially, an incorrect x-omeda-appid.
404 Not FoundThis response occurs when the email address submitted was not found.
500 Internal Server ErrorIn the rare case that there is a server-side problem, this response will be returned. This generally indicates a problem of a more serious nature, and submitting additional requests may not be advisable. Please contact your Omeda Account Representative if the issue continues.


         "ValidationDate":"2020-04-10 08:49:19"
         "VendorCode": "V"
         "VendorCodeDescription": "valid"
         "VendorName": "FreshAddress"

         "ValidationDate":"2019-02-15 10:43:59"
         "VendorCode": "SUCCESS"
         "VendorCodeDescription": "success"
         "VendorName": "Synthio"
         "ValidationDate":"2019-01-02 00:00:00"
         "VendorCode": "ACCEPTALL"
         "VendorCodeDescription": "acceptall"
         "VendorName": "Synthio"


         "Error":"Email address not found."
Possible Error Messages

In the event of an error, an error response will be returned. Here are some of the possible responses you might receive.

Email address {emailAddress} not found.
Table of Contents
Scroll to Top