Skip to main content

LexisNexis KYB

LexisNexis KYB searches for a business and can retrieve a configurable business report for the selected entity. Use Search to compare possible business matches and obtain LexisNexis business identifiers. Use Report to retrieve the selected business’s available identity, industry, filings, assets, relationships, and other requested sections. The active Workflow Builder block ID is lexisnexis_kyb, its visible label is LexisNexis KYB, and it is available for business entities in the KYB underwriting group. LexisNexis publicly describes its SmartLinx business content as linking business, commercial, and public-record data. The exact TopBusinessSearch and TopBusinessReport API schemas require credentialed product documentation. The response shapes and field names on this page are therefore confirmed against Lendflow’s current integration fixtures; only the broader product capabilities are confirmed by public LexisNexis SmartLinx Business Report materials.

Operations

Search and Report have separate request data, responses, timestamps, and Lendflow lifecycle statuses. Running Report can therefore create both a Search run and a Report run.

Requirements

Report

Search-to-Report business selection

Lendflow resolves the Report subject in this order:
  1. If the business has a stored sele_id, Lendflow sends that value as SeleID, OrgID, and UltID.
  2. Otherwise, Lendflow uses the complete BusinessIds object from the first Search record.
  3. If no Search identifiers are stored, Report runs Search first and stores the first record’s identifiers under the business’s top-business match.
  4. If Search returns RecordCount: 0, Report cannot continue and Lendflow records No search results found..
Search can return multiple possible matches, but automatic Report selection uses the first record unless the business already has a selected sele_id. Confirm the intended entity before relying on a report.

Report options

Report accepts 28 user-selectable options. Each selected key is sent to LexisNexis with value 1; unselected keys are omitted. The Dashboard displays the labels below and requires at least one selection when a user runs Report manually. The option labels describe requested sections, not guaranteed results. Entitlements, source coverage, and the selected business determine which sections and records are returned.

Defaults and API names

Lendflow also sends BusinessReportFetchLevel: "S" on every Report request. This value is fixed and is not user-configurable.

Run through the application enrichment API

  1. Call Enrich Business Credit Application for the application.
  2. Set provider to lexis_nexis_kyb_search or lexis_nexis_kyb_report.
  3. For Report, optionally include options.lexisNexisKybOptions with one or more values from the table above.
  4. Include the applicable underwriting stage_id when required by the application’s workflow.
  5. Confirm that the response contains data.onqueue: true.
  6. Poll Get Commercial Data with services[]=lexis_nexis_kyb_search and/or services[]=lexis_nexis_kyb_report.
  7. Read the operation-specific status under data.statuses.lexis_nexis and the provider payload under data.commercial_data.lexis_nexis.
data.onqueue: true means Lendflow queued the asynchronous job. It does not mean LexisNexis finished or found a business. The business-credit v1 wrapper uses Enrich Business Credit Application. Put the service IDs in requested_products and use lexis_nexis_kyb_options for Report options.

Run with Data Orchestration

The Search and Report services are available through the lexisnexis_kyb business block in Data Orchestration.
  1. In the Lendflow Dashboard, open Builders > Data Orchestration.
  2. Create or edit a template and add the applicable LexisNexis KYB operation from the KYB category.
  3. Configure the conditions and connect each outcome, then save and publish the template. Data Orchestration uses the default Include Industries Report option.
  4. Call Execute Data Orchestration with template_id and application_id. Include stage_id when applicable.
  5. Confirm that the response contains data.executed: true.
  6. Monitor the asynchronous run with List Data Orchestration Logs and Get Data Orchestration Log.
  7. Retrieve enrichment data after the prerequisite service finishes.
data.executed: true means the orchestration run was accepted. Orchestration log statuses are started, interrupted, finished, and error; these describe the workflow run, not the LexisNexis result.

What the service returns

Search returns up to 20 records beginning with the first record and uses a 50-mile radius in the current Lendflow request. Report content varies with the selected options. A section can be absent, an object can be empty, an array can be empty, or a scalar can be null when the provider has no value or the section was not requested. Absence alone does not mean the overall request failed.

Representative response

This sanitized example combines the current Lendflow commercial-data wrapper with fields confirmed in exact Search and default Include Industries Report fixtures.

Response attributes

Lendflow wrapper

Provider Search response

Provider Report response

Stored Report request

Provider results and Lendflow statuses

Provider result fields answer questions about the matched business. Lendflow statuses answer whether the asynchronous integration ran and stored a response.

Provider result fields

Lendflow lifecycle statuses and errors

See Data Provider Status Messages for shared status guidance.

FAQ

Search returns possible business matches and their LexisNexis identifiers. Report uses one set of identifiers to retrieve the selected report sections. They are separate services with separate statuses and responses.
Yes. If the business does not already have stored LexisNexis top-business identifiers, Lendflow runs Search before Report. If Search returns no records, Report cannot continue.
Lendflow uses the business’s stored sele_id when present. Otherwise, it uses the complete BusinessIds object from the first Search record.
If Report options are omitted or empty, the backend uses IncludeIndustries. The Dashboard’s manual run requires the user to select one or more options, while Run with all models selects all 28.
A selected option requests a section but does not guarantee records. The section can be absent or empty because of account entitlement, source coverage, or no data for the selected business.
No. Success means Lendflow stored the provider response. Read IsActive, IsDefunct, match indicators, and the requested report sections to interpret the business result.
Not completely. LexisNexis’s public materials confirm the product’s broader business-record and linking capabilities, but the detailed TopBusinessSearch and TopBusinessReport schemas require product access. The response shape on this page is fixture-confirmed against Lendflow’s current integration.
No. data.onqueue: true and data.executed: true acknowledge scheduling. Poll the applicable enrichment or Data Orchestration status until processing reaches a terminal state.