Dun & Bradstreet Business Match
Dun & Bradstreet Business Match searches D&B for organizations that match the business stored on a Lendflow application. The Workflow Builder block runs servicednb_bm_l1 for business entities and returns candidate organizations with match-quality details.
Requirements
Only the business legal name and country are required by the current D&B request validator. Additional valid values improve the provider’s match context.Run through the application enrichment API
- Call
PUT /api/applications/{application_id}/enrichthrough Enrich Business Credit Application. - Set
providertodnb_bm_l1. - Do not send service-specific
options; Business Match has no configurable options. - Include
stage_idonly when the application workflow requires a specific underwriting stage. - Confirm that the response contains
data.onqueue: true. - Poll Get Commercial Data with
services[]=dnb_bm_l1.
data.onqueue: true confirms that Lendflow queued the job; it does not mean D&B returned a candidate.
The commercial-data endpoint returns this service in a stored-validation wrapper:
- Provider result:
data.commercial_data.dnb.bm_l1.response - Stored request:
data.commercial_data.dnb.bm_l1.request - Latest lifecycle message:
data.statuses.dnb.bm_l1 - Provider HTTP status:
data.commercial_data.dnb.bm_l1.status_code
response in the commercial_data object, not under request_data.
Data Orchestration availability and flow
The Dun & Bradstreet Business Match block is available in Workflow Builder’s underwriting Match group for business entities. It runsdnb_bm_l1.
- Add Dun & Bradstreet Business Match to a business underwriting workflow.
- Ensure the required business name, country, and D&B access are available before the block runs.
- Connect the block before any downstream step that needs a D-U-N-S Number, then save and publish the workflow.
- Execute the published orchestration through Execute Data Orchestration with
template_id,application_id, andstage_idwhen applicable. - Confirm that the response contains
data.executed: true. - Monitor the asynchronous run with List Data Orchestration Logs.
- Read the stored result and status from the commercial-data paths above.
What the service returns
Representative response
This abbreviated response follows Lendflow’s current D&B fixture. Business and contact values are sanitized.Response attributes
Candidate identity and ranking
Addresses and operating status
Match quality
Errors and statuses
FAQ
Which inputs are required?
Which inputs are required?
Business legal name and business-address country are required. Address, telephone, email, D-U-N-S Number, and country-specific registration number are optional but can improve match context.
Does data.onqueue true mean a match exists?
Does data.onqueue true mean a match exists?
No. It only confirms that Lendflow queued the asynchronous job. Poll the commercial-data endpoint and inspect
statuses.dnb.bm_l1 and commercial_data.dnb.bm_l1.response.matchCandidates.Where is the stored D&B request?
Where is the stored D&B request?
It is at
data.commercial_data.dnb.bm_l1.request. This service is an exception to the usual request_data placement.Does Business Match save the D-U-N-S Number?
Does Business Match save the D-U-N-S Number?
Yes, when the first candidate contains a D-U-N-S Number, Lendflow saves it on the application’s business for downstream D&B services.
How should I handle null and empty values?
How should I handle null and empty values?
Treat both as unavailable provider data. D&B can return
null for scalar fields and empty arrays for unpopulated collections such as mailing-address components, websites, trading names, and principals.