LexisNexis Email Search

LexisNexis Email Search uses an individual’s email address and available identity information to find associated LexisNexis records. The response can help your team validate an email, compare the associated name and address with the application, and understand how broadly the email is linked to LexisNexis identities. This is an individual-entity service in the KYC category. It is separate from LexisNexis KYC, which provides KYC Search and KYC Report services.

Requirements

Application field	Requirement	Notes
Business legal name	Required	Identifies the end-user company in the LexisNexis request.
Owner email	Optional	This is the primary value used for the email-centric search and is recommended for a useful result.
Owner first and last name	Optional	Helps associate the email with the expected person.
Owner address	Optional	Helps match and compare the identity associated with the email.
Owner SSN	Optional	Strengthens identity matching when available.
Owner date of birth	Optional	Strengthens identity matching when available.
Business address and telephone	Optional	Included as end-user context when available.

LexisNexis permits the individual SearchBy fields to be empty, but an email and supporting identity information are recommended for a useful result.

Configure the search

Option	Values	Meaning
Search tier	`Basic` or `Premium`	Selects the LexisNexis search tier. Premium requires the corresponding account entitlement.
Search type	`EAA`, `EIA`, or `EIC`	`EAA` appends an email address, `EIA` appends identity information, and `EIC` checks an email identity.
Marketing use	`0` or `1`	Declares whether the search is for marketing use.

The Dashboard defaults to Basic, EAA, and marketing use enabled. When no options are supplied through the service API, the backend defaults are Premium, EAA, and marketing use enabled.

Configure LexisNexis Email Search in Data Orchestration

In the Lendflow Dashboard, open Builders > Data Orchestration.
Create or edit a template.
Add LexisNexis Email Search from the KYC category.
Configure the search tier, search type, and marketing-use option.
Configure the conditions that should use the returned email or address information.
Connect each outcome to the next block.
Save and publish the template.

See Data Orchestration for the complete template-building workflow.

Run the service through the API

Data services run through a published Data Orchestration template. Your integration needs:

An integration token with permission to access the application and run Data Orchestration.
The application ID.
A published template containing LexisNexis Email Search.
The template ID.
The applicable workflow stage_id when the template is assigned to a specific stage.

Call Execute Data Orchestration for the application.
Include template_id and application_id. Include stage_id when applicable.
Confirm that the response contains data.executed: true.
Monitor the run with List Data Orchestration Logs and Get Data Orchestration Log.
Retrieve the application’s enrichment data after processing finishes.

Sample response

The exact response structure below is based on the response stored by Lendflow’s current LexisNexis integration. LexisNexis’s public product documentation confirms the result categories, but its detailed Email Search API schema requires product access.

{
  "EmailSearchV2ResponseEx": {
    "@xmlns": "http://webservices.seisint.com/WsAccurint",
    "response": {
      "Header": {
        "Status": 0,
        "QueryId": "example-query-id",
        "TransactionId": "example-transaction-id"
      },
      "RecordCount": 1,
      "Records": {
        "Record": [
          {
            "LexId": "example-lexid",
            "Original": {
              "EmailAddress": "OWNER@EXAMPLE.COM"
            },
            "Cleaned": {
              "EmailAddress": "OWNER@EXAMPLE.COM",
              "Name": {
                "First": "JANE",
                "Last": "DOE"
              },
              "Address": {
                "StreetAddress1": "123 MAIN ST",
                "City": "ANYTOWN",
                "State": "NY",
                "Zip5": "10001"
              }
            },
            "EmailStatus": "valid",
            "NumEmailPerLexid": 4,
            "NumLexIdPerEmail": 1,
            "LNDateFirst": {
              "Year": 2018,
              "Month": 4,
              "Day": 16
            },
            "LNDateLast": {
              "Year": 2026,
              "Month": 7,
              "Day": 5
            }
          }
        ]
      }
    }
  }
}

Response attributes

Attribute	Type	Meaning
`EmailSearchV2ResponseEx`	Object	Root LexisNexis Email Search response.
`@xmlns`	String	LexisNexis XML namespace represented in the JSON response.
`response`	Object	Contains the request header and returned records.
`Header.Status`	Number	Provider status code returned in the LexisNexis response header.
`Header.QueryId`	String	LexisNexis identifier for the query.
`Header.TransactionId`	String	LexisNexis identifier for the transaction.
`RecordCount`	Number	Number of email-associated records returned.
`Records.Record`	Array	Matching identity records.
`LexId`	String	LexisNexis LexID associated with the returned identity.
`Original`	Object	Email and related values as originally reported to LexisNexis.
`Original.EmailAddress`	String	Email address as originally reported in the source record.
`Cleaned`	Object	Normalized identity information associated with the email.
`Cleaned.EmailAddress`	String	Normalized email address.
`Cleaned.Name`	Object	Normalized name parts.
`Cleaned.Name.First`	String	Normalized first name.
`Cleaned.Name.Last`	String	Normalized last name.
`Cleaned.Address`	Object	Normalized address associated with the email.
`Cleaned.Address.StreetAddress1`	String	Formatted street-address line.
`Cleaned.Address.City`	String	City associated with the normalized address.
`Cleaned.Address.State`	String	State associated with the normalized address.
`Cleaned.Address.Zip5`	String	Five-digit ZIP code.
`EmailStatus`	String	Email deliverability status. Lendflow fixtures contain `valid` and `unknown`; LexisNexis also documents invalid-email results.
`NumEmailPerLexid`	Number	Number of emails associated with this LexID.
`NumLexIdPerEmail`	Number	Number of LexIDs associated with this email.
`LNDateFirst`	Object	Date LexisNexis first observed the association.
`LNDateLast`	Object	Date LexisNexis most recently observed the association.
`Year`, `Month`, `Day`	Numbers	Components of a LexisNexis date object.

The response can also include BestInfo, vendor reporting dates, additional status information, company information, and more detailed address components.

No results and errors

Result	Meaning
`RecordCount: 0`	LexisNexis found no email-associated records.
`No email search results found.`	Lendflow’s expected no-result status for an empty record set.
`Authorization failed.`	LexisNexis authentication failed.
Premium-access error	The configured LexisNexis account is not entitled to the Premium search tier. Select Basic or update the account entitlement.
`Something went wrong while processing the request.`	The provider request failed without a more specific returned message.

FAQ

How is Email Search different from LexisNexis KYC?

Email Search is a single email-centric lookup. LexisNexis KYC uses separate person-search and comprehensive-report services.

Is the owner's email technically required?

The request validator permits the search fields to be empty, but an owner email is strongly recommended because this service is designed to search and validate email-associated identity information.

Why did a Premium search fail?

Premium searches require the corresponding LexisNexis account entitlement. Select the Basic tier or confirm Premium access with your LexisNexis administrator.

Does RecordCount zero mean the service failed?

No. It means the request completed but LexisNexis returned no matching records.