Documentation
Getting Started
Free AnalysisPricing
FAQ
Threat Level Guide
Result Codes
List Profile Report
Threat Intelligence Center
Best Practices
Data Export Specs
Country Disposition
API
API OverviewVerification/Threats API ►
Threats API
Credits Balance API
Bulk FTP Transfer
Bulk API List Submission
Verification/Threats API Overview
Our API can be seamlessly integrated into your signup or onboarding process with just a single request. This high speed processing option is designed for continuous, real-time, data cleansing for verifying an individual email address using standard HTTP POST methods and JSON formatted responses.
Structure and Definition for Inbound Submissions
Our API requires you to authenticate each individual request. Below is an example of a basic URL structure request, just substitute with the provided account, associated password along with any optional parameters.
Structure: https://post.impressionwise.com/verifyme.aspx?CODE=000001&PWD=password1&<paramlist>
Required Data Fields
Parameter's need to be separate by "&"
&CODE= 6 Digit Alpha-numeric, account code provided by Impressionwise = 000001
&PWD= Alpha-numeric, security code provided by Impressionwise = password1
&EMAIL= Recipient email address to be submitted for processing = noexist@testme.com
&TIMEOUT= Maximum time allowed to process value represented in seconds, range = 2-15 (default 6)
Optional System Fields
&MX= To receive the MX domain information for an email address = 1
Optional Client Pass-thru Fields
Parameter's need to be separate by "&" = param1=value1¶m2=value2&...
&fname=test
&lname=me
&addr1=123 sw 150 ave
&addr2=
&city=miami
&state=FL
&zip=33222
&country=USA
&phone=3057645678
&gender=m
&optinsite=www.impressionwise.com
&optindate=2010-02-10
&optinip=34.44.55.32
&other1=
&other2=
** Maximum of 20 "other" variables.
URL Structure Example
A properly formatted URL post would resemble the following example:
https://post.impressionwise.com/fastfeed.aspx?code=000001&pwd=askme&email=testme@impressionwise.com&timeout=10&fname=test&lname=me&addr1=123 sw 150 ave &addr2=&city=miami&state=FL&zip=33222&country=USA&phone=3057645678&gender=m&optinsite=www.impressionwise.com&optindate=2010-02-10&optinip=34.44.55.32
Parameters and Usage
To verify an email address simply use the request shown in the sample below substituting the required parameters with provided credentials and email address you want to verify.
Sample = https://post.impressionwise.com/verifyme.aspx?CODE=000001&PWD=password1&EMAIL=noexist@testme.com&TIMEOUT=10
Upon successful posting of an email address, you can expect to receive the following response.
JSON Response = {"EMAIL":"noexist@testmelink.com","RESULT":"SUPPRESS","CLASS":"INVALID","TTP":2.41}
Possible result parameter/values include:
&RESULT= "See below section Result Code section for additional detail"
&CLASS= "See below section Classification Sub-Code section for additional detail"
&TTP= "Time it took to process value represented in seconds"
&MXROOT= "MX domain name as per posted DNS"
&EPS= "Future for Engagement Propensity Score, numeric value between 1-100, if parameter is present"
&DPS;TTP= ”Future Delivery Preference Score, numeric value between 1-120, if parameter is present”
Error Handling
From time to time you may experience an API error. It is important to watch out for these and handle them appropriately. Specifically, if your submission contains an invalid account code or password the result response would be WRONG_PSW.
Additionally, it has been our experience that with some smaller email hosts it is not uncommon for their reply to take an excessive amount of time to respond (more than 15 seconds). Due to this possible condition, we allow you to specify a maximum timeout period in which you are willing to wait for a response. If this value is exceeded you will receive a result code of DISCRETIONARY. Upon reception of this response in addition to TTP value that exceeds the TIMEOUT value specified, please continue your HTTP submissions thru to completion of the entire data set to be submitted. Once complete, please RETRY any/all responses with meeting this condition, and if the response is the same (another TIMEOUT), we recommend to retry with a higher TIMEOUT value. Example shown below:
JSON Response = {"EMAIL":"noexist@testmelink.com","RESULT":"DISCRETIONARY","CLASS":"TIMEOUT","TTP":1.33}
If you receive any other response other than those previously shown, please contact support.
Result Codes
The recommended guidelines presented below will ensure you are adhering to email best practices, enabling more emails to reach the inbox. While Impressionwise is known for providing industry leading levels of detail, we have combined over 240 threat metrics into 3 intuitive result codes for ease of use.
Resuls Description/ Guidance |
Result Code |
|
Do Not Email. All addresses in this file should be entirely removed from your active mailing list as they have been classified as “Do Not Email”. These addresses contain various reputation and deliverability threats and should be avoided. You may use this list as a suppression file to be uploaded to your ESP for ease of use. This code contains the following threat classifications: Trap, Mole, Quarantine, Seed (Bots/Role/Disposable/Seed/Dormant), Key, Parked, Invalid. | SUPPRESS | |
Discretionary. We are able to conclude that these email addresses do not represent a threat to your online reputation, yet we are unable to conclusively verify that these addresses are deliverable. In order to provide to you additional detail and insight into the results obtained, we also include the following sub-classifications: Catch-All, Greylisted, Connection Timeout and Indeterminate. We advise sending this group initially on a separate network (domain/IP) to confirm bounce ratio is within acceptable norms before sending through your main sending network. | DISCRETIONARY | |
Certified Good to Send. Email address with no known reason to expect a delivery failure or harm to email senders online reputation. | CERTIFIED |
Classification Sub-Codes
Impressionwise’s threat intelligence platform provides additional insight and detail to a wide range of email-based threats. These threats, ranging in severity, are broken down into classifications.
Description |
Response |
Guidance |
|
Certified. All email addresses in this file have been certified good to send from a delivery reputation perspective, yet recipient-level bounce status has not been verified. With this understanding, you may upload this list to your ESP and send to each address with full confidence. | Certified | Send | |
Key. Protect against high-risk traffic sources. Our digital forensics analytics is designed to identify complex, non-human, machine-generated email accounts that historically use a variety of tactics to generate massive amounts of non-converting impressions | Key | Send ONLY if Recipient was organically acquired with user- based submission evidence OR has purchase activity within last 90 days (open/click activity excluded) | |
Role Accounts. Role-based email addresses (e.g. admin@, help@, sales@) are email addresses that are not associated with a particular person, but rather with a company, department, position or group of recipients. | Role | ||
Disposable Email Accounts. As their naming suggests, these addresses are intended to be used and discarded. Disposable email addressing (DEA) refers to an approach where a unique email address is used for every contact or entity. The benefit is that if anyone compromises the address or utilizes it in connection with email abuse, the address owner can easily cancel (or "dispose" of) it without affecting any of their other contacts. | Disposable | ||
Discretionary. We are able to conclude that these email addresses do not represent a threat to your online reputation, yet we are unable to conclusively verify that these addresses are deliverable. In order to provide to you additional detail and insight into the results obtained, we also include the following sub-classifications: Catch-All, Greylisted, Connection Timeout and Indeterminate. |
Catchall Greylist Indeterminate Connection Timeout |
We advise sending this group initially on a separate network (domain/IP) to confirm bounce ratio is within acceptable norms before sending through your main sending network | |
Quarantine. Once active traps gone dormant may become reactivated during a 90 day period. Yet actively considered certified. | Quarantine | Suppress | |
Parked Site Intelligence. Avoid sending email traffic to millions of unused and parked domains. Since parked domains have previously not been configured for email or web service by the owner, any email sent to these domains is by definition, invalid and considered unsolicited or spam. All email received is often auto-forwarded to a central catch-all account to be black-holed or distributed to various blacklist providers. | Parked | ||
Seed. Third party oversight email address used for general monitoring of company's network resources. Removal of litigators and collaborative anti-spam activists historically known to purposely seed their email address(es) for the purpose of litigation. | Seed | ||
Proxies/ Bots. Protect against high-risk traffic sources. Our digital forensics analytics is designed to identify complex, non-human, machine-generated email accounts that historically use a variety of tactics to generate massive amounts of non-converting impressions. | Bot | ||
Invalid. Defined as the inability to actually deliver an email message to intended recipient's receiving domain per RFC standards. | Invalid | ||
Mole. Collaborating recipient submission-based or domain-level, anti-spam solution with no current, direct ownership of resources involved. Yet historical evidence firmly establishes a relationship to one or more DNSBL sites. | Mole | ||
Trap. Purpose-built, Spam-trap, or Honeypot e-mail address. Any e-mail messages sent to this address are immediately considered unsolicited. | Trap |
General Disclaimer: Every reasonable effort is made to locate all known threat and delivery classification elements mentioned herein, yet due to the constantly changing and dynamic nature of the online environment, we can not guarantee the results or deliverable will be free of any/all traps, threat or delivery classification elements identified within this report.
While every attempt has been made to ensure that the information in this document is accurate and complete, some typographical errors or technical inaccuracies may exist. Impressionwise does not accept responsibility for any kind of loss resulting from the use of information provided.
Questions? Please feel free to contact us with any questions or specific customization requirements you may have regarding our automated, data cleansing feed services to ensure a successful evaluation or use of our services and let the results speak for themselves!