Experian Bankruptcies

Use this service to retrieve bankruptcy summary and filing-detail records associated with an Experian business.

Requirements

Application field	Requirement	Notes
Business country	Required	Provide the business country code. This service supports United States business information.
Business legal name	Conditional	Required when the application does not already have a Business Identification Number (BIN).
Business city	Conditional	Required when the application does not already have a BIN.
Business state	Conditional	Required when the application does not already have a BIN. Use the two-letter state code.
Business street, ZIP code, telephone, and EIN	Optional	These fields can improve Business Match results when Lendflow must obtain a BIN.
Business Identification Number (BIN)	Conditional	Required to run Bankruptcies. If it is unavailable, Lendflow runs Experian Business Match and uses the result with the highest numeric reliability code. The service does not run if Business Match returns no result.

API flow

The dashboard starts a manual run with PUT /api/int/applications/{application_id}/enrich and provider experian_bankruptcies. This is an internal dashboard route, not a supported public integration endpoint.

Add the experian_bankruptcies attribute to a published Data Orchestration template.
Call POST /api/applications/{application_id}/data_orchestration/execute through Execute Data Orchestration with a bearer token, template_id, application_id, and stage_id when the template requires a specific underwriting stage.
The endpoint schedules the orchestration and returns {"data":{"executed":true}}, not the Experian result.
Retrieve the result with GET /api/applications/{application_id}/commercial_data through Get Commercial Data, using services[]=experian_bankruptcies. Read the provider result from data.commercial_data.experian.bankruptcies, status from data.statuses.experian.bankruptcies, latest date from data.dates.experian_bankruptcies, and stored request from data.request_data.experian.bankruptcies.

The orchestration attribute checks saved bankruptcy data first. If its required value is absent, it runs the Experian prerequisite synchronously. Data Orchestration requests detail and disables summary by default; Lendflow can retain previously stored top-level bankruptcy result sections when a later run returns another section.

Value	Dashboard data path
Response	`commercialData.experian.bankruptcies`
Status	`commercialData.statuses.experian.bankruptcies`
Submitted request	`commercialData.request_data.experian.bankruptcies`

The provider request always includes bin and subcode. A normal direct service run requests bankruptcySummary: true and bankruptcyDetail: true.

Data Orchestration availability

Capability	Availability
Primary attribute	`experian_bankruptcies` (`Bankruptcies`)
Prerequisite behavior	Runs Experian Bankruptcies only when the needed saved section is absent
Execution	Synchronous prerequisite
Reuse	Existing saved data is reused when it satisfies the selected attribute

What the service returns

Result area	What it contains	How to interpret it
`businessHeader`	Identity data for the business associated with the BIN.	Confirm that the result belongs to the intended business.
`bankruptcySummary`	Bankruptcy indicator and count.	Distinguish an explicit `false` or `0` from a missing value.
`bankruptcyDetail`	Filing date, chapter/action, document number, court, and owner for each filing.	Each array item is one provider record.
`bankruptcyIndicator`	Top-level indicator used by Data Orchestration.	`true` means bankruptcy information is reported.

Representative response

{
  "businessHeader": {
    "bin": "000000000",
    "businessName": "SAMPLE INDUSTRIES",
    "address": {"city": "AUSTIN", "state": "TX", "zip": "78701"},
    "customerDisputeIndicator": false
  },
  "bankruptcySummary": {
    "bankruptcyCount": 1,
    "bankruptcyIndicator": true
  },
  "bankruptcyDetail": [
    {
      "owner": null,
      "dateFiled": "2021-08-17",
      "legalType": "BANKRUPTCY",
      "legalAction": "CHAPTER 11",
      "documentNumber": "SAMPLE-CASE",
      "filingLocation": "US BANKRUPTCY COURT"
    }
  ],
  "bankruptcyIndicator": true
}

Response attributes

Summary and identity

Attribute	Type	Meaning	Possible values or units	When returned
`businessHeader.bin`	String	Experian BIN.	Experian identifier.	When Experian identifies the business.
`businessHeader.businessName`	String	Name associated with the matched record.	Business name.	When available.
`businessHeader.address`	Object	Address associated with the matched record.	Street, city, state, ZIP, and ZIP extension may appear.	When available.
`businessHeader.customerDisputeIndicator`	Boolean	Whether the business disputed profile information.	`true` or `false`.	When supplied by Experian.
`bankruptcySummary.bankruptcyCount`	Number	Bankruptcy records on file.	Count.	When summary was requested and returned.
`bankruptcySummary.bankruptcyIndicator`	Boolean	Whether summary data reports a bankruptcy.	`true` or `false`.	When summary was requested and returned.
`bankruptcyIndicator`	Boolean	Top-level bankruptcy signal.	`true` or `false`.	When supplied by Experian.

Filing details

Attribute	Type	Meaning	Possible values or units	When returned
`bankruptcyDetail[].dateFiled`	String	Filing date.	`YYYY-MM-DD`.	For each filing when available.
`bankruptcyDetail[].legalType`	String	Record type.	Typically `BANKRUPTCY`.	For each filing.
`bankruptcyDetail[].legalAction`	String	Bankruptcy chapter or action.	For example, `CHAPTER 7`, `CHAPTER 11`, or `CHAPTER 13`.	For each filing when available.
`bankruptcyDetail[].documentNumber`	String	Filing or case identifier.	Court-specific identifier.	When available.
`bankruptcyDetail[].filingLocation`	String	Court or filing location.	Court name or jurisdiction.	When available.
`bankruptcyDetail[].owner`	String or null	Owner named on the record.	Name.	Frequently `null`; do not interpret null as no filing.
`bankruptcyDetail[].liabilityAmount`	Number or null	Reported liabilities.	Currency amount in provider units.	Only when Experian supplies it.
`bankruptcyDetail[].assetAmount`	Number or null	Reported assets.	Currency amount in provider units.	Only when supplied.
`bankruptcyDetail[].exemptAmount`	Number or null	Reported exempt amount.	Currency amount in provider units.	Only when supplied.

Statuses and errors

Signal	Meaning
Commercial-data status is `Started`	The service started but has not recorded completion or failure.
Commercial-data status is `Success`	The latest run completed; inspect `data.commercial_data.experian.bankruptcies`.
Commercial-data status contains an error	The run failed and the status includes its error message.
Orchestration status `6`, `1`, `5`, `2`, `4`, or `3`	Scheduled, started, paused, finished, missing data, or error, respectively.
No Business Match result	Lendflow stops before the bankruptcy request because it could not obtain a BIN.
Invalid credentials, subcode, or provider response	The service records the failure; provider messages are normalized from Experian’s error payload when available.

An empty bankruptcyDetail array means no detail records were returned. A missing array or null field means that section or value was not supplied and must not be treated as an explicit zero or false.

FAQ

Does Data Orchestration always call Experian?

No. The selected attribute reuses saved bankruptcy data when its prerequisite is already satisfied.

Why can the summary be absent in a Data Orchestration run?

The Data Orchestration prerequisite requests detail and disables summary by default. A normal direct service run requests both sections.

Does this service require an Experian BIN?

Yes. Lendflow automatically runs Experian Business Match when the BIN is missing.

Is a null owner the same as no bankruptcy?

No. owner is often not reported. Use the indicator, count, and detail array to interpret the result.