Append verified email addresses to U.S. contact records by searching our database of more than 1.8 billion listings using existing contact fields such as first name, last name, city, state, and postal address.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Making a Request
The AppendEmail method leverages the same low level search functions and data sources used in our Batch Email Append service. Pass your existing contact information such as first name, last name, city, state, and physical address to look-up the email address(es) associated with your customer.
Postal Address Input and Parsing
All postal address input is automatically parsed and corrected using our address standardization app. This ensures the highest possible match rate and reduces matching issues. The endpoint requires a street address and city/state/postal code or city/state or postal code.
Output Email Address Verification
All output email addresses are verified in real-time by pinging the ISP to determine deliverability status with 90% accuracy. Output email addresses are also scanned by a real-time SPAM detection algorithm that protects sender reputation by performing over 240 independent, real-time scans analyzing your data for all known problematic or non-deliverable email addresses.
HTTP HeadersThe "content-type" in the HTTP header must be set to "application/json", otherwise an HTTP 400 Bad Request response will be returned.
Response Definitions
A single response may include multiple Email addresses. A match level is returned for each email address to indicate the context in which the match was made.
| Field name | Type | Description |
|---|---|---|
| string | Fully verified email address | |
| FirstName | string | Listing identity's first name |
| LastName | string | Listing identity's last name |
| MatchLevel | string | Indicates the [MatchLevel] (https://docs.accurateappend.com/reference/matchlevel-consumer-1) under which the match was found. |
MatchLevel
The MatchLevel response field indicates how well the request fields sent to the API match the response fields. For example, a MatchLevel returned of E1 might be considered an exact match whereas a return of E2 reveals that the first name of the individual does not necessarily match the request fields. Click to see the MatchLevel codes and descriptions.
HTTP Error Messages
Click to see a complete listing of error messages and codes.