Skip to main content
Experian Business Quick Search finds candidate U.S. businesses from one application value and returns Experian Business Identification Numbers (BINs), names, addresses, telephone numbers, contacts, and provider ranking values. The Workflow Builder block is ExperianQuickSearch, and its service ID is experian_business_quick_search.

Requirements

The selected search source must resolve to a non-empty string.

API flow

  1. Call Enrich Business Credit Application.
  2. Set provider to experian_business_quick_search.
  3. Optionally set options.searchString to one of the values above. stage_id is optional; when supplied, it must be a valid underwriting workflow-stage UUID for the application.
  4. Treat {"data":{"onqueue":true}} as queue acceptance, not a completed search.
  5. Poll Get Commercial Data with services[]=experian_business_quick_search.
The API queues a background job. That job authenticates with Experian, performs the provider request, stores the response, and updates the business’s Experian BIN from the first returned result when available.

Data Orchestration availability and flow

Experian Business Quick Search is available in Data Orchestration under Match > Experian > Quick Search.
  1. Add the Experian Quick Search service step and configure a condition that checks whether a business match exists.
  2. Choose the quick-search source when needed. Data Orchestration defaults to the business legal name.
  3. If prerequisite Quick Search data is absent, Data Orchestration runs the service synchronously before evaluating the condition.
  4. The condition evaluates the first non-empty result. An empty result or Experian’s no-records message evaluates as no match.

What the service returns

Representative response

Response attributes

Errors and statuses

  • An unsupported options.searchString value fails Lendflow request validation.
  • A selected application value that resolves to null or an empty string fails provider-request validation.
  • Inactive or invalid Experian credentials, a missing subcode, authentication failures, and provider HTTP errors cause the queued job to fail.
  • No candidates produces No Business found - {business name}. This is different from a provider transport error.
  • Success means Lendflow stored the search results. It is not an underwriting decision.

FAQ

Lendflow uses business_legal_name when options.searchString is omitted.
No. data.onqueue=true only confirms that the background job was queued. Poll Commercial Data until the lifecycle message reaches a terminal state.
Yes. When Experian returns a candidate, Lendflow stores the BIN from the first result on the business.
Yes. It can fetch missing prerequisite data synchronously and evaluate whether the first result contains a business match.