Experian Judgments

Use this service to retrieve judgment 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 Judgments. 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_judgments. This is an internal dashboard route, not a supported public integration endpoint.

Add the experian_judgments 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 required.
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_judgments. Read the provider result from data.commercial_data.experian.judgments, status from data.statuses.experian.judgments, latest date from data.dates.experian_judgments, and stored request from data.request_data.experian.judgments.

The orchestration attribute checks saved judgment 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 judgment result sections when a later run returns another section.

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

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

Data Orchestration availability

Capability	Availability
Primary attribute	`experian_judgments` (`Judgments`)
Prerequisite behavior	Runs Experian Judgments 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.
`judgmentSummary`	Judgment count and combined balance.	Zero is an explicit returned result; missing is unknown.
`judgmentDetail`	Filing date, action, document number, court, owner, liability amount, and plaintiff.	Each array item is one provider record.
`judgmentIndicator`	Top-level indicator used by Data Orchestration.	`true` means judgment information is reported.

Representative response

{
  "businessHeader": {
    "bin": "000000000",
    "businessName": "SAMPLE INDUSTRIES",
    "address": {"city": "AUSTIN", "state": "TX", "zip": "78701"},
    "customerDisputeIndicator": false
  },
  "judgmentSummary": {"judgmentCount": 1, "judgmentBalance": 12500},
  "judgmentDetail": [
    {
      "dateFiled": "2023-05-23",
      "legalType": "Judgment",
      "legalAction": "Filed",
      "documentNumber": "SAMPLE-CASE",
      "filingLocation": "SAMPLE COUNTY COURT",
      "owner": "SAMPLE INDUSTRIES",
      "liabilityAmount": 12500,
      "plaintiffName": "SAMPLE PLAINTIFF"
    }
  ],
  "judgmentIndicator": 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.
`judgmentSummary.judgmentCount`	Number	Judgments on file.	Count.	When summary was requested and returned.
`judgmentSummary.judgmentBalance`	Number	Combined judgment balance.	Currency amount in provider units.	When summary was requested and returned.
`judgmentIndicator`	Boolean	Whether judgment information is reported.	`true` or `false`.	When supplied by Experian.

Judgment details

Attribute	Type	Meaning	Possible values or units	When returned
`judgmentDetail[].dateFiled`	String	Filing date.	`YYYY-MM-DD`.	For each judgment when available.
`judgmentDetail[].legalType`	String	Record type.	Typically `Judgment`.	For each judgment.
`judgmentDetail[].legalAction`	String	Current filing action.	`Filed`, `Released`, or `Satisfied`.	When available.
`judgmentDetail[].documentNumber`	String	Filing identifier.	Court-specific identifier.	When available.
`judgmentDetail[].filingLocation`	String	Court or jurisdiction.	Name or location.	When available.
`judgmentDetail[].owner`	String or null	Owner named on the action.	Name.	When available.
`judgmentDetail[].liabilityAmount`	Number or null	Debtor liability.	Currency amount in provider units.	When available.
`judgmentDetail[].plaintiffName`	String or null	Plaintiff named in the judgment.	Name.	When available.
`judgmentDetail[].customerDisputeIndicator`	Boolean	Whether the record is disputed.	`true` or `false`.	When supplied by Experian.

Statuses and errors

Signal	Meaning
Commercial-data status is `Started`	The service started but has not completed or failed.
Commercial-data status is `Success`	The latest run completed; inspect `data.commercial_data.experian.judgments`.
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 judgment request because it could not obtain a BIN.
Invalid credentials, subcode, or provider response	The service records the failure and normalizes an Experian error message when available.

An empty judgmentDetail array means no detail records were returned. Missing or null fields are unknown, not zero or false.

FAQ

Does Data Orchestration always call Experian?

No. It reuses saved judgment data when the selected attribute’s 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 run requests both.

Does this service require an Experian BIN?

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

Is a missing liability amount the same as zero?

No. Zero is a provider result. A null or omitted amount means Experian did not supply the value.