Skip to main content

Middesk Business Match

Middesk Business Match searches Secretary of State business-name records using the application’s legal name and formation state. It returns possible matches and relative name-match scores; it does not create or verify a full Middesk Business. The Workflow Builder block is Middesk, and its service ID is middesk_business_search.

Requirements

The search uses the formation state, not the business-address state.

API flow

  1. Call Enrich Business Credit Application.
  2. Set provider to middesk_business_search. This service has no provider-specific request options.
  3. Optionally include stage_id; 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[]=middesk_business_search.
The API queues a background job. The provider call itself completes synchronously inside that job, after which Lendflow stores the request, response, and provider HTTP status.

Data Orchestration availability and flow

Middesk Business Match is available in Data Orchestration under Match > Middesk > Name Search.
  1. Add the Middesk Name Search service step.
  2. Configure a condition against the best returned score, from 0 through 1.
  3. If a successful business-search prerequisite is absent, Data Orchestration runs middesk_business_search synchronously before evaluating the condition.
  4. A template can optionally use the successful result to replace the application’s business legal name with the best candidate name.

What the service returns

Representative response

Response attributes

Errors and statuses

  • Missing business_legal_name or an unresolved formation_state fails validation before the Middesk request.
  • An inactive or invalid Middesk integration prevents a successful provider call.
  • Middesk HTTP errors are stored with their response body and status code, and Lendflow marks the queued job as failed.
  • A successful response with data: [] means no candidate was found; it is not a transport failure.
  • Success means the search response was stored. It does not mean the business passed KYB verification.

FAQ

No. middesk_business_search only returns possible business-name matches. The separate middesk service creates and verifies a Middesk Business.
It uses the application’s formation state after Lendflow resolves it to a supported state code.
It is a high relative name-match score on Middesk’s 0-through-1 scale. Lendflow does not define one score as an automatic underwriting decision.
Yes. When that action is configured and its condition succeeds, the template can apply the best returned candidate name to the application business.