> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.middesk.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.middesk.com/_mcp/server.

# Research legal records

> Learn how to retrieve legal records associated with businesses and individuals using the Middesk API.

Middesk supports additional risk assessment by pulling legal records for a business or person:

* Litigations (legal cases)
* Bankruptcy filings
* People criminal history

Separately or combined, these records help identify potential legal risks, assess reputation, and make informed decisions about business relationships.

> **Note**
>
> Legal record searches are available as add-ons within the Business Verification solution. Ordering legal records requires a Verify report. You can order these products simultaneously with a Verify report or add them afterward.

## Search for litigations

Middesk's Litigations product enables you to access court case records associated with businesses and individuals.

Middesk searches for various types of court cases, including:

* **Civil litigation**, contract disputes, business disputes, and other civil matters
* **Debt collection cases**, actions to recover unpaid debts
* **Commercial disputes**, business-to-business legal conflicts
* **Other case types**, additional legal proceedings as available in public records

### How to retrieve litigations

Retrieving litigations requires that you first create a business, then request an [order](/create-orders) for that business.

* For business litigations, request a `litigations` order
* For associated people litigations, request a `people_litigations` order

You can do this in the Dashboard or the API.

> **Tip**
>
> For people litigations, you can filter the types of cases returned by configuring your account settings in the Dashboard. This helps you focus on relevant case types for your use case.

### Understand litigation results

The litigations response contains detailed information about each court case found associated with the business or person.

**Litigation object structure**

Each litigation object includes the following key attributes:

| Field           | Type   | Description                                                               |
| --------------- | ------ | ------------------------------------------------------------------------- |
| `id`            | string | Unique litigation identifier assigned by Middesk                          |
| `case_name`     | string | The official name of the court case                                       |
| `case_number`   | string | The case identifier assigned by the court                                 |
| `case_status`   | string | Current status: `Open`, `Closed`, or `Unknown`                            |
| `case_type`     | string | Category of the case (for example, `Debt Collection`, `Unknown`)          |
| `filing_date`   | string | The date when the case was filed                                          |
| `judgment`      | array  | Docket entries with dates, text descriptions, and monetary amounts        |
| `jurisdictions` | string | The location where the case was filed                                     |
| `party_type`    | string | The role of the entity: `Plaintiff`, `Defendant`, `Petitioner`, and so on |

**`Example litigation response`**

```json title="Example litigation response"
{
  "object": "list",
  "data": [
    {
      "id": "litigation_00000000000000000000000000",
      "case_name": "First National Bank v. Example Business Inc",
      "case_number": "2023-CV-12345",
      "case_status": "Open",
      "case_type": "Debt Collection",
      "filing_date": "2023-06-15",
      "judgment": [
        {
          "entry_date": "2023-06-15",
          "text": "Complaint filed by plaintiff",
          "amount_cents": null
        },
        {
          "entry_date": "2023-07-20",
          "text": "Default judgment entered in favor of plaintiff for $15,000",
          "amount_cents": 1500000
        }
      ],
      "jurisdictions": "San Francisco County Superior Court, CA",
      "party_type": "Defendant"
    }
  ]
}
```

### How to order litigations

Litigation searches require a completed Verify order. You can order both together as a bundle or sequentially.

#### Order as a bundle

Order Verify and litigations together in a single request.

#### Create a business

```bash
curl -X POST https://api.middesk.com/v1/businesses \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Acme Corporation",
    "addresses": [
      {
        "address_line1": "123 Main Street",
        "city": "San Francisco",
        "state": "CA",
        "postal_code": "94105"
      }
    ],
    "orders": [
      { "product": "business_verification_verify" },
      { "product": "litigations" }
    ]
  }'
```

#### Wait for verification to complete

Wait for the `business.updated` webhook indicating the business status is `in_review`. Check the [litigations review task](#litigations-review-task) for search results.

#### Order sequentially

Order Verify first, then add litigations after verification completes.

#### Create a business with verify order

```bash
curl -X POST https://api.middesk.com/v1/businesses \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Acme Corporation",
    "addresses": [
      {
        "address_line1": "123 Main Street",
        "city": "San Francisco",
        "state": "CA",
        "postal_code": "94105"
      }
    ],
    "orders": [
      { "product": "business_verification_verify" }
    ]
  }'
```

#### Wait for verification to complete

Wait for the `business.updated` webhook indicating the business status is `in_review`. See [review tasks](/review-insights) for details on verification results.

#### Order litigations

```bash
curl -X POST https://api.middesk.com/v1/businesses/{business_id}/orders \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "product": "litigations"
  }'
```

#### Wait for order to complete

Wait for the `business.updated` webhook indicating the order is complete. Check the [litigations review task](#litigations-review-task) for search results.

### How to order people litigations

People litigation searches require a completed Verify order. You can order both together as a bundle or sequentially.

#### Order as a bundle

Order Verify and people litigations together in a single request.

#### Create a business

```bash
curl -X POST https://api.middesk.com/v1/businesses \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Acme Corporation",
    "addresses": [
      {
        "address_line1": "123 Main Street",
        "city": "San Francisco",
        "state": "CA",
        "postal_code": "94105"
      }
    ],
    "people": [
      {
        "name": "Jane Smith"
      }
    ],
    "orders": [
      { "product": "business_verification_verify" },
      { "product": "people_litigations" }
    ]
  }'
```

#### Wait for verification to complete

Wait for the `business.updated` webhook indicating the business status is `in_review`. Check [people review tasks](/verify-business/people/review-tasks) for search results.

#### Order sequentially

Order Verify first, then add people litigations after verification completes.

#### Create a business with verify order

```bash
curl -X POST https://api.middesk.com/v1/businesses \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Acme Corporation",
    "addresses": [
      {
        "address_line1": "123 Main Street",
        "city": "San Francisco",
        "state": "CA",
        "postal_code": "94105"
      }
    ],
    "people": [
      {
        "name": "Jane Smith"
      }
    ],
    "orders": [
      { "product": "business_verification_verify" }
    ]
  }'
```

#### Wait for verification to complete

Wait for the `business.updated` webhook indicating the business status is `in_review`. See [review tasks](/review-insights) for details on verification results.

#### Order people litigations

```bash
curl -X POST https://api.middesk.com/v1/businesses/{business_id}/orders \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "product": "people_litigations"
  }'
```

#### Wait for order to complete

Wait for the `business.updated` webhook indicating the order is complete. Check [people review tasks](/verify-business/people/review-tasks) for search results.

## Find bankruptcies

Reviewing and monitoring bankruptcies helps determine the level of financial risk you take on when onboarding and lending to businesses.

Finding bankruptcies requires that you first create a business, then request an [order](/create-orders) for that business.

* For business bankruptcies, request a `bankruptcies` order
* For associated people bankruptcies, request a `people_bankruptcies` order

You can do this in the Dashboard or the API.

If Middesk finds bankruptcies, the resulting details include:

* **Debtor**, the individual or entity that owes money to another party
* **Trustee**, the individual responsible for the bankruptcy and all case proceedings
* **Court**, the court in which the hearing takes place, including the office number, district, and case number
* **Chapter**, the chapter in the collection of types of court cases that bankruptcy falls into
* **Updates**, a sequence of events for the case that includes a description, a reference, and the event date

> **Note**
>
> A people bankruptcies order searches for bankruptcies associated with all people on the business with the required information.

### How to order bankruptcies

Bankruptcy searches require a completed Verify order. You can order both together as a bundle or sequentially.

#### Order as a bundle

Order Verify and bankruptcies together in a single request.

#### Create a business

```bash
curl -X POST https://api.middesk.com/v1/businesses \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Acme Corporation",
    "addresses": [
      {
        "address_line1": "123 Main Street",
        "city": "San Francisco",
        "state": "CA",
        "postal_code": "94105"
      }
    ],
    "orders": [
      { "product": "business_verification_verify" },
      { "product": "bankruptcies" }
    ]
  }'
```

#### Wait for verification to complete

Wait for the `business.updated` webhook indicating the business status is `in_review`. Check the [bankruptcies review task](#bankruptcies-review-task) for search results.

#### Order sequentially

Order Verify first, then add bankruptcies after verification completes.

#### Create a business with verify order

```bash
curl -X POST https://api.middesk.com/v1/businesses \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Acme Corporation",
    "addresses": [
      {
        "address_line1": "123 Main Street",
        "city": "San Francisco",
        "state": "CA",
        "postal_code": "94105"
      }
    ],
    "orders": [
      { "product": "business_verification_verify" }
    ]
  }'
```

#### Wait for verification to complete

Wait for the `business.updated` webhook indicating the business status is `in_review`. See [review tasks](/review-insights) for details on verification results.

#### Order bankruptcies

```bash
curl -X POST https://api.middesk.com/v1/businesses/{business_id}/orders \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "product": "bankruptcies"
  }'
```

#### Wait for order to complete

Wait for the `business.updated` webhook indicating the order is complete. Check the [bankruptcies review task](#bankruptcies-review-task) for search results.

### How to order people bankruptcies

People bankruptcy searches require a completed Verify order. You can order both together as a bundle or sequentially.

#### Order as a bundle

Order Verify and people bankruptcies together in a single request.

#### Create a business

```bash
curl -X POST https://api.middesk.com/v1/businesses \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Acme Corporation",
    "addresses": [
      {
        "address_line1": "123 Main Street",
        "city": "San Francisco",
        "state": "CA",
        "postal_code": "94105"
      }
    ],
    "people": [
      {
        "name": "Jane Smith"
      }
    ],
    "orders": [
      { "product": "business_verification_verify" },
      { "product": "people_bankruptcies" }
    ]
  }'
```

#### Wait for verification to complete

Wait for the `business.updated` webhook indicating the business status is `in_review`. Check [people review tasks](/verify-business/people/review-tasks) for search results.

#### Order sequentially

Order Verify first, then add people bankruptcies after verification completes.

#### Create a business with verify order

```bash
curl -X POST https://api.middesk.com/v1/businesses \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Acme Corporation",
    "addresses": [
      {
        "address_line1": "123 Main Street",
        "city": "San Francisco",
        "state": "CA",
        "postal_code": "94105"
      }
    ],
    "people": [
      {
        "name": "Jane Smith"
      }
    ],
    "orders": [
      { "product": "business_verification_verify" }
    ]
  }'
```

#### Wait for verification to complete

Wait for the `business.updated` webhook indicating the business status is `in_review`. See [review tasks](/review-insights) for details on verification results.

#### Order people bankruptcies

```bash
curl -X POST https://api.middesk.com/v1/businesses/{business_id}/orders \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "product": "people_bankruptcies"
  }'
```

#### Wait for order to complete

Wait for the `business.updated` webhook indicating the order is complete. Check [people review tasks](/verify-business/people/review-tasks) for search results.

## Search for criminal history

A third type of legal record Middesk can pull is an individual's criminal history. Request a `people_criminal_history` order on a business to trigger a search for criminal records associated with the submitted people on the business.

### How to order people criminal history

People criminal history searches require a completed Verify order. You can order both together as a bundle or sequentially.

For people criminal history searches, the following fields are required for each person:

* `first_name` - The person's first name
* `last_name` - The person's last name
* `dob` - The person's date of birth

The following fields are optional but can improve search accuracy and results:

* `ssn` - Social Security Number
* `phone_numbers` - Array of phone number objects in E.164 format. Format: `[{ "phone_number": "+1234567890" }]`
* `middle_name` - The person's middle name

> **Note**
>
> Only one phone number per person should be submitted.

#### Order as a bundle

Order Verify and people criminal history together in a single request.

#### Create a business

```bash
curl -X POST https://api.middesk.com/v1/businesses \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Acme Corporation",
    "addresses": [
      {
        "address_line1": "123 Main Street",
        "city": "San Francisco",
        "state": "CA",
        "postal_code": "94105"
      }
    ],
    "people": [
      {
        "first_name": "Jane",
        "last_name": "Smith",
        "dob": "1985-05-15",
        "ssn": "123456789",
        "phone_numbers": [
          { "phone_number": "+17075555555" }
        ]
      }
    ],
    "orders": [
      { "product": "business_verification_verify" },
      { "product": "people_criminal_history" }
    ]
  }'
```

#### Wait for verification to complete

Wait for the `business.updated` webhook indicating the business status is `in_review`. Check [people review tasks](/verify-business/people/review-tasks) for search results.

#### Order sequentially

Order Verify first, then add people criminal history after verification completes.

#### Create a business with verify order

```bash
curl -X POST https://api.middesk.com/v1/businesses \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Acme Corporation",
    "addresses": [
      {
        "address_line1": "123 Main Street",
        "city": "San Francisco",
        "state": "CA",
        "postal_code": "94105"
      }
    ],
    "people": [
      {
        "first_name": "Jane",
        "last_name": "Smith",
        "dob": "1985-05-15",
        "ssn": "123456789",
        "phone_numbers": [
          { "phone_number": "+17075555555" }
        ]
      }
    ],
    "orders": [
      { "product": "business_verification_verify" }
    ]
  }'
```

#### Wait for verification to complete

Wait for the `business.updated` webhook indicating the business status is `in_review`. See [review tasks](/review-insights) for details on verification results.

#### Order people criminal history

```bash
curl -X POST https://api.middesk.com/v1/businesses/{business_id}/orders \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "product": "people_criminal_history"
  }'
```

#### Wait for order to complete

Wait for the `business.updated` webhook indicating the order is complete. Check [people review tasks](/verify-business/people/review-tasks) for search results.

Once completed, the Person object includes a `criminal_records` array of details.

### Understand criminal records

The criminal records response contains detailed information about each criminal record found associated with the person.

**Criminal records object structure**

Each criminal record object includes the following key attributes:

| Field                                                 | Type   | Description                                                            |
| ----------------------------------------------------- | ------ | ---------------------------------------------------------------------- |
| `criminal_records[].id`                               | string | The criminal record id, assigned by Middesk                            |
| `criminal_records[].category`                         | string | The category of the criminal record (for example, Criminal or traffic) |
| `criminal_records[].person.dob`                       | date   | The DOB on the criminal record                                         |
| `criminal_records[].cases[].arrest_date`              | date   | Arrest date                                                            |
| `criminal_records[].cases[].arresting_agency`         | string | Arresting agency                                                       |
| `criminal_records[].cases[].case_number`              | string | The case number for the criminal case                                  |
| `criminal_records[].cases[].case_type`                | string | The case type                                                          |
| `criminal_records[].cases[].court_county`             | string | The court county of the case                                           |
| `criminal_records[].cases[].court_name`               | string | The court name                                                         |
| `criminal_records[].cases[].file_date`                | string | The date when the case was filed                                       |
| `criminal_records[].cases[].status`                   | string | Case status                                                            |
| `criminal_records[].cases[].charges[].category`       | string | The category of the charge                                             |
| `criminal_records[].cases[].charges[].charge_type`    | string | The type of the charge (for example, Misdemeanor, Felony)              |
| `criminal_records[].cases[].charges[].city`           | string | The city where the charge occurred                                     |
| `criminal_records[].cases[].charges[].county`         | string | The county where the charge occurred                                   |
| `criminal_records[].cases[].charges[].description`    | string | Description of the charge                                              |
| `criminal_records[].cases[].charges[].dispositions`   | array  | Dispositions associated with the charge                                |
| `criminal_records[].cases[].charges[].legal_code`     | string | Legal code of the charge                                               |
| `criminal_records[].cases[].charges[].offense_date`   | date   | The date of the offense                                                |
| `criminal_records[].cases[].charges[].sentences`      | array  | Sentences associated with the charge                                   |
| `criminal_records[].cases[].charges[].state`          | string | The state that the charge was filed in                                 |
| `criminal_records[].cases[].charges[].subcategory`    | string | Subcategory of the charge                                              |
| `criminal_records[].cases[].charges[].subsubcategory` | string | Subsubcategory of the charge                                           |

## Review tasks

Legal record searches generate review tasks that summarize findings. These tasks appear in the Business object's `review.tasks` array.

### bankruptcies review task

Identify bankruptcy filings associated with the business.

| status  | message                                | sub\_label |
| ------- | -------------------------------------- | ---------- |
| Success | The business has no bankruptcy filings | None Found |
| Failure | The business has bankruptcy filing(s)  | Found      |

### litigations review task

Identify litigation records associated with the business.

| status  | message                                 | sub\_label |
| ------- | --------------------------------------- | ---------- |
| Success | The business has no related litigations | None Found |
| Failure | The business has related litigation(s)  | Found      |

For people-related legal review tasks (`people_bankruptcies`, `people_litigations`, `people_criminal_history`), see [People verification review tasks](/verify-business/people/review-tasks).

## Next steps

#### [Screen for adverse media](/verify-business/adverse-media)

Surface negative news coverage tied to a business or its officers.

#### [Search for liens](/assess-risk/search-liens)

Retrieve UCC and tax lien filings associated with a business.

#### [Monitor business activity](/monitor-activity)

Get notified when registrations, bankruptcies, or watchlist hits change over time.

> **Get a demo**
>
> Contact your account manager or [contact sales](https://www.middesk.com/contact-sales) to inquire about access.