Datazapp API Documentation

Reverse Email Append API

Submit email addresses, SHA256 hashes, or MD5 hashes to return associated consumer or business data, including name, address, city, state, ZIP, phone, company, job title, and LinkedIn details when available.

Version: 1.0.0
Method: POST
Format: JSON

Get Started

The Reverse Email Append API allows you to submit email addresses or encrypted email hashes and return associated identity, postal, phone, and business profile data when a match is available.

Use AppendType to specify whether your input is SHA, MD5, or plain email. You can also use Isb2bOnly to request business-only records.

API Endpoint

Replace the placeholder below with your assigned Datazapp API endpoint URL.

Endpoint - you'll get this from your account manager
<datazapp api endpoint URL>

Reverse Email Append API Request

Submit your API key, append module, append type, B2B preference, and email or hashed email input.

JSON Request Body
{
  "ApiKey": "<Your API KEY>",
  "AppendModule": "EncryptedEmailAppendAPI",
  "AppendType": 5,
  "Isb2bOnly": 1,
  "Data": [
    {
      "Email": "[email protected]"
    }
  ]
}
JSON Request Body - SHA Input
{
  "ApiKey": "<Your API KEY>",
  "AppendModule": "EncryptedEmailAppendAPI",
  "AppendType": 1,
  "Isb2bOnly": 0,
  "Data": [
    {
      "Email": "sha256_hash_here"
    }
  ]
}
JSON Request Body - MD5 Input
{
  "ApiKey": "<Your API KEY>",
  "AppendModule": "EncryptedEmailAppendAPI",
  "AppendType": 2,
  "Isb2bOnly": 0,
  "Data": [
    {
      "Email": "md5_hash_here"
    }
  ]
}

Request Parameters

Parameter Required Type Description
ApiKey Yes String Your assigned Datazapp API key.
AppendModule Yes String Use EncryptedEmailAppendAPI.
AppendType Yes Integer Determines whether your input is SHA, MD5, or plain email.
IsPhoneOnly No String / Boolean True returns only matching records with cell or phone data. False returns all matching records.
Isb2bOnly Yes Integer Use 1 for business-only records or 0 for non-business-only matching.
Data Yes Array Contains the submitted email or encrypted email records.
Email Yes String Email address, SHA hash, or MD5 hash depending on the selected AppendType.

AppendType Values

1 — SHA Input Use when submitting SHA encrypted email values.
2 — MD5 Input Use when submitting MD5 encrypted email values.
5 — Email Input Use when submitting plain email addresses.

API Response

A successful response includes a header, token, matched data records, order amount, count, and processing time.

JSON Response
{
  "header": {
    "Status": 0,
    "Message": null
  },
  "ResponseDetail": {
    "App": 0,
    "Token": "QxxxxB",
    "Data": [
      {
        "Company": "W***********IES",
        "JobTitle": "MAR*************ATIVE",
        "Industry": "",
        "LinkedInURL": "linkedin.com/in/l*****17****1b",
        "CompanyWebsite": "",
        "CompanyCountry": "united states",
        "Matched": true,
        "FirstName": "L***A",
        "LastName": "S***P",
        "Address": "",
        "City": "P****X",
        "State": "AZ",
        "ZIP": "",
        "Country": "united states",
        "Email": "1*******om",
        "emailHash": null,
        "Cell": "",
        "CellDNC": "",
        "Phone": "",
        "PhoneDNC": ""
      }
    ],
    "OrderAmount": "$x.xx",
    "Count": 1,
    "Message": null,
    "ProcessedTime": "xxx milliseconds"
  },
  "Status": true,
  "Message": null
}

Response Fields

Field Type Description
header.StatusIntegerIndicates header status.
header.MessageStringIndicates error type, when applicable.
ResponseDetail.AppIntegerApplication reference value returned by the system.
ResponseDetail.TokenStringSystem-generated reference token.
ResponseDetail.DataArrayReturned reverse email append result records.
CompanyStringName of the company the person is associated with.
JobTitleStringPerson’s job title or designation at the company.
IndustryStringIndustry associated with the company.
LinkedInURLStringLinkedIn profile URL of the person.
CompanyWebsiteStringWebsite of the company.
CompanyCountryStringCountry where the company is located.
MatchedBoolean / StringIndicates whether the submitted record matched.
FirstNameStringFirst name of the matched person.
LastNameStringLast name of the matched person.
AddressStringAddress associated with the matched person.
CityStringCity associated with the matched person.
StateStringState associated with the matched person.
ZIPStringZIP or ZIP+4 associated with the matched person.
CountryStringCountry associated with the matched person.
EmailStringReturned email address.
emailHashStringReturned hashed email value, when available.
CellStringCell phone number associated with the matched person.
CellDNCStringCell phone DNC indicator, such as Yes or No.
PhoneStringLandline phone number associated with the matched person.
PhoneDNCStringLandline DNC indicator, such as Yes or No.
OrderAmountStringAmount charged for returned matches.
CountString / IntegerNumber of matched records.
ProcessedTimeStringTotal API processing time.
StatusBoolean / StringIndicates overall request status.
MessageStringNull when successful, or error detail when applicable.

Errors

The API may return one of the following error messages if the request cannot be completed.

Module does not exist.The specified module does not exist or the AppendModule name is invalid.
User not found.The API key is invalid or the user associated with the API key was not found.
Getting 401 Error.The user does not have access to this API.
Append Request not found.The specified append request could not be found or the token is invalid.
Improper JSON Data. Please check.The JSON data in the request does not match the expected format.
It seems like API has an issue. Please contact Support.There may be an issue with the API. Contact Datazapp support for assistance.

Recent Post

Categories