Documentation

Getting Started

Free Analysis
Pricing
FAQ
Threat Level Guide
Result Codes
List Profile Report
Threat Intelligence Center
Best Practices
Data Export Specs
Country Disposition

API

API Overview
Verification/Threats API
Threats API ►
IVT/ Bots API
Bulk FTP Transfer
Bulk API List Submission

Threats API Overview

Our Hygiene 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 cleansing an individual email address using standard HTTP methods.

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/fastfeed.aspx?CODE=000001&PWD=password1&<paramlist>

Required Data Fields

Parameters need to be separated by "&"

&CODE= 6 Digit numeric, acccount 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

Optional Client Pass-thru Fields

Parameter's need to be separate by "&" = param1=value1&param2=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 as shown below.

https://post.impressionwise.com/fastfeed.aspx?code=000001&pwd=askme&email=testme@impressionwise.com&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/fastfeed.aspx?code=000001&pwd=password1&email=noexist@testme.com

Upon successful posting of an email address, you can expect to receive the following response.

Response = EMAIL=noexist@testmelink.com&RESULT=INVALID&TTP=2.41

Possible result parameter/values include:

&RESULT= "See below section Result Code section for additional detail"
&TTP= "Time it took to process value represented in seconds"
&NPD= "See below section Net Protect Detail section for additional detail"
&CC= "See below section Country Code Detail section for additional detail"

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 (sometimes more than 10 seconds). Due to this possible condition, you will receive a result code of RETRY. Upon reception of this response, please continue your HTTP submissions thru to completion of the entire data set to be submitted.. Once complete, please retry any/all responses with "RETRY" or as shown below:

Response = EMAIL=noexist@testmelink.com&RESULT=RETRY&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. As a result, you will mitigate any risk associated with emailing to potentially "bad" addresses and you will experience additional opens, higher click through rates, increased conversions, and more revenue while protecting your online reputation.

Current Version

Version 1.0

Result Specifications

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)
	Quarantine. Once active traps gone dormant may become reactivated during a 90 day period. Yet actively considered certified.	Quarantine
	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	Do Not Send
	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

Version 1.0 Result Specifications

Description		Response	Guidance
	Certified Domestic. US-based email address with no known reason to expect a delivery failure or harm to email senders online reputation.	CertDom	Send
	Certified International. Non-US-based email address with no known reason to expect a delivery failure or harm to email senders online reputation.	CertInt	Send
	Network Protected. Managed SMTP filtering applications known to be highly collaborative, notifications sent to leading DNSBL sites in real-time.	NetProtect	Send ONLY if Recipient was organically acquired with user- based submission evidence OR has purchase activity within last 90 days (open/click activity excluded)
	Key. Complex pattern recognition and threat string algorithms designed to remove intra-domain recipients employed by that domain for use as spam traps.	Key
	Quarantine. Once active traps gone dormant may become reactivated during a 90 day period. Yet actively considered certified.	Quarantine
	Parked Site Intelligence. Email addresses that after careful evaluation has been established to be least likely to be responsive or engage.	Parked	Do Not Send
	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
	Invalid. Defined as the inability to actually deliver an email message to intended recipients, 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. Email address has known association of having direct ownership or control over the resources involved with the reception of a message leading to its submission to one or more DNSBL sites.	Trap

Net Protect (NPD) Codes (optional)

To address specific deliverability challenges, use the network protected codes provided below to allow for individual classification suppression.

NA = Not applicable or address is not a network protected domain

010 = AppRiver
011 = Barracuda
012 = Google/Postini-McAfeeASAP.com
013 = Ironport
014 = NAI-McAfee
015 = Outblaze
016 = Securence
017 = Symantec-BrightMail
018 = Symantec-MessageLabs
019 = SymantecMail
022 = Invalument
025 = ZeroSpam.ca
026 = RBLSMTPD
027 = CatchAll
028 = CommTouch
029 = CloudMark
030 = Government; .gov, .mil, .edu, .us
034 = Trend Micro
035 = Kundenserver
036 = ProofPoint Threat Intelligence (SORBS parent)
037 = Microsoft Message Security (bigfish,frontbridge)
038 = Microsoft Frontbridge
039 = Blocklist.de Reporting Sites
041 = SpamCop Enabled User Network
042 = Cisco Netprotect
043 = XMission Envelope

The list of codes above, while infrequent, are subject to change. When a change occurs, generally a notification will be sent prior to any changes go live.

Usage and Guidance

Network Protected Domains, and the recipients belonging to, are considered to be deliverable. However, the managed SMTP SaaS's are known to be highly collaborative, checking and notifying other leading industry DNSBL sites in real-time if email sent to an anti-spam solution is deemed spam. This section is designed to provide NOTICE ONLY as to which domains are being managed by a particular third party, anti-spam solution and aid in the delivery of your email.

Recommended Usage: The anti-spam solution classifications are specifically designed to aid in deliverability challenges. For example, if you are unable to get any email through to any domain protected by a Barracuda appliance due to Barracuda labeling your email as spam, then using the Barracuda export would provide options not normally available. The sender could elect to suppress this domain grouping completely to protect the deliverability to the remaining certified domains within your list. The more popular option would be to take all the network protected domain groupings and send to them after you have sent all other data marked as good or certified to ensure optimal delivery footprint.

Country Code Detail (optional)

Due to the large number of country codes, a comma-delimited text file has been created for easy access and installation of code library into any existing application. This code library can be found at https://www.impressionwise.com/kb/CountryCodes.txt.

The country codes are subject to change. While changes or new changes are rare, please check back monthly to ensure the version you downloaded is current.

Domain Origination Note: Sourced from IANA’s database of TLD extensions, proprietary views as provided by domain registrars and Regional Internet Registries (AfriNIC, APNIC, ARIN, LACNIC, RIPE). Assessment is based off the geographic location of the originating IP that the MX record points to establish if domain is of domestic US or international origin. Supplemental confirmation utilizing corresponding RIR's SWIP and Rwhois data where possible.

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!