# County Clerk Records - Lis Pendens, Liens & Deeds (TX, OH, MI) (`regdata/us-county-recorded-documents`) Actor

Daily index of documents recorded with US county clerks: lis pendens, liens, deeds, deeds of trust, releases, affidavits of heirship and sheriff's deeds. Pre-foreclosure and probate leads, lien monitoring and title research. No API key needed.

- **URL**: https://apify.com/regdata/us-county-recorded-documents.md
- **Developed by:** [getregdata](https://apify.com/regdata) (community)
- **Stats:** 1 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 document records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## County Clerk Records - Lis Pendens, Liens & Deeds

Get the documents recorded with US county clerks, day by day: **lis pendens, notices of trustee's sale, mechanic's, tax and hospital liens, deeds, deeds of trust and mortgages, releases, affidavits of heirship, transfer-on-death affidavits, sheriff's and trustee's deeds**. One clean row per document with the county, recorded date, document type, grantors, grantees, legal description and a link to the record on the county's site.

The data comes from the county clerk's official public records search. No API key, no login, no county account needed.

### What you can do with it

- **Pre-foreclosure leads** - every lis pendens, notice of trustee's sale and appointment of substitute trustee recorded yesterday, with the owner names and the legal description.
- **Probate and inherited-property leads** - affidavits of heirship, transfer-on-death affidavits, small-estate affidavits and probate filings.
- **Distressed sales** - sheriff's deeds, trustee's and substitute trustee's deeds, tax deeds and deeds in lieu.
- **Lien monitoring** - mechanic's and materialman's liens, federal and state tax liens, hospital liens, judgments and HOA liens, and their releases.
- **Title research** - every deed, deed of trust, assignment and release recorded against a name in a date window.

Schedule it daily with **Only documents not delivered before** switched on and you get a feed of new filings without duplicates.

### Counties covered

- **Texas** (43): Anderson (`anderson.tx`), Bee (`bee.tx`), Bell (`bell.tx`), Bexar (`bexar.tx`), Brazos (`brazos.tx`), Brewster (`brewster.tx`), Burleson (`burleson.tx`), Cameron (`cameron.tx`), Chambers (`chambers.tx`), Cochran (`cochran.tx`), Coleman (`coleman.tx`), Collin (`collin.tx`), Dallas (`dallas.tx`), Denton (`denton.tx`), Freestone (`freestone.tx`), Gillespie (`gillespie.tx`), Goliad (`goliad.tx`), Grayson (`grayson.tx`), Grimes (`grimes.tx`), Hidalgo (`hidalgo.tx`), Hockley (`hockley.tx`), Jefferson (`jefferson.tx`), Jim Wells (`jimwells.tx`), Kendall (`kendall.tx`), Leon (`leon.tx`), Live Oak (`liveoak.tx`), Llano (`llano.tx`), Matagorda (`matagorda.tx`), Midland (`midland.tx`), Milam (`milam.tx`), Montgomery (`montgomery.tx`), Nacogdoches (`nacogdoches.tx`), Nueces (`nueces.tx`), Reeves (`reeves.tx`), Refugio (`refugio.tx`), Rusk (`rusk.tx`), San Patricio (`sanpatricio.tx`), Smith (`smith.tx`), Starr (`starr.tx`), Tarrant (`tarrant.tx`), Walker (`walker.tx`), Wilson (`wilson.tx`), Zapata (`zapata.tx`)
- **Ohio** (11): Butler (`butler.oh`), Carroll (`carroll.oh`), Clark (`clark.oh`), Cuyahoga (`cuyahoga.oh`), Franklin (`franklin.oh`), Greene (`greene.oh`), Hardin (`hardin.oh`), Harrison (`harrison.oh`), Jefferson (`jefferson.oh`), Ottawa (`ottawa.oh`), Sandusky (`sandusky.oh`)
- **Michigan** (9): Calhoun (`calhoun.mi`), Hillsdale (`hillsdale.mi`), Isabella (`isabella.mi`), Lenawee (`lenawee.mi`), Mecosta (`mecosta.mi`), Oceana (`oceana.mi`), Presque Isle (`presqueisle.mi`), Roscommon (`roscommon.mi`), Tuscola (`tuscola.mi`)
- **Pennsylvania** (4): Berks (`berks.pa`), Delaware (`delaware.pa`), Indiana (`indiana.pa`), Lawrence (`lawrence.pa`)
- **Colorado** (3): Arapahoe (`arapahoe.co`), Boulder (`boulder.co`), Routt (`routt.co`)
- **New Mexico** (3): Dona Ana (`donaana.nm`), Eddy (`eddy.nm`), Union (`union.nm`)
- **Connecticut** (2): Greenwich (`greenwich.ct`), Sterling (`sterling.ct`)
- **South Carolina** (2): Beaufort (`beaufort.sc`), Oconee (`oconee.sc`)
- **Arkansas**: Garland (`garland.ar`) - **Maine**: Kennebec (`kennebec.me`) - **Rhode Island**: East Providence (`eastprovidence.ri`) - **Utah**: San Juan (`sanjuan.ut`) - **Vermont**: Chester (`chester.vt`) - **US Virgin Islands** (`usvi`)

The value in brackets is what you put in `counties` when you call the actor through the API.

### Input

| Field | What it does |
|---|---|
| `counties` | Required. One or more counties from the list above. |
| `dateFrom`, `dateTo` | Recorded date window, `YYYY-MM-DD`. Default: yesterday to yesterday. At most 31 days per run. |
| `documentCategories` | Optional. `preForeclosure`, `liens`, `releases`, `deedsTransfers`, `distressedTransfers`, `probateHeirship`, `mortgages`. Empty = every document. |
| `partyName` | Optional. Only documents with this grantor or grantee name, e.g. `SMITH JOHN` (counties index people as LAST FIRST). |
| `maxResults` | Most documents per run, across all counties. Default 1,000; 0 = no limit. |
| `onlyNewSinceLastRun` | Feed mode: skip documents this feed delivered before (remembered for 60 days). |
| `stateStoreName` | Name of the store that remembers delivered documents. Use one name per feed. |

**Daily pre-foreclosure and probate feed for Dallas and Tarrant:**

```json
{
  "counties": ["dallas.tx", "tarrant.tx"],
  "documentCategories": ["preForeclosure", "distressedTransfers", "probateHeirship"],
  "maxResults": 0,
  "onlyNewSinceLastRun": true,
  "stateStoreName": "dfw-distress-feed"
}
```

**All liens recorded in Cuyahoga and Franklin in the first week of October:**

```json
{
  "counties": ["cuyahoga.oh", "franklin.oh"],
  "dateFrom": "2026-10-01",
  "dateTo": "2026-10-07",
  "documentCategories": ["liens"]
}
```

**Everything recorded against one name in Bexar this month:**

```json
{ "counties": ["bexar.tx"], "dateFrom": "2026-10-01", "dateTo": "2026-10-16", "partyName": "DOE JOHN" }
```

### Output

One row per recorded document. Example (names are invented):

```json
{
  "county": "Dallas County, TX",
  "state": "TX",
  "instrumentNumber": "202600220512",
  "documentType": "LIS PENDENS (NOTICE OF)",
  "documentTypeCode": "LP",
  "category": "preForeclosure",
  "recordedDate": "2026-10-14",
  "instrumentDate": "2026-10-14",
  "grantors": ["DOE JOHN Q", "DOE JANE A"],
  "grantees": ["EXAMPLE MORTGAGE CO"],
  "legalDescription": "Subdivision- Town: DALLAS Name: CEDAR CREST VILLAGE NO 5 Lot: 26 Block: H",
  "subdivision": "CEDAR CREST VILLAGE NO 5",
  "lot": "26",
  "block": "H",
  "propertyAddress": null,
  "parcelNumber": null,
  "consideration": null,
  "bookVolumePage": null,
  "pageCount": 3,
  "sourceUrl": "https://dallas.tx.publicsearch.us/doc/331600000",
  "retrievedAt": "2026-10-17T07:00:00.000Z"
}
```

- `category` is our grouping of the county's own document type (counties word the same document differently, e.g. "SHERIFF'S DEED" in Texas and "SD - SHERIFFS DEED" in Ohio). Documents outside the seven groups are `other`.
- `propertyAddress`, `parcelNumber` and `consideration` are filled only where the county indexes them (for example Cuyahoga and Bexar often do, Dallas usually does not).
- `sourceUrl` opens the document's page on the county's own site.

### Pricing

You pay per document delivered. Filters run before delivery, so with `documentCategories` you only pay for the documents you keep.

### FAQ

**Do I get the document images or PDFs?**
No. This actor delivers the county's public index only: names, dates, document type, instrument number and legal description. Copies of documents are sold by the county clerk; use `sourceUrl` to view or order them on the county's site.

**How fresh is the data?**
A document appears once the county has indexed it, and every county works at its own pace: each one shows its own "indexed through" (certification) date on its site, and the newest recorded days can still be incomplete. A daily feed with a window of the last 7 days and **Only documents not delivered before** catches late-indexed documents exactly once.

**A county "did not answer" - what now?**
Sometimes a county site is down for maintenance. The run delivers the other counties, marks itself Partial and names the county in the status message. Run it again later for that county.

**Why is a recorded day empty?**
Weekends and county holidays have no recordings, and the most recent days may not be indexed yet.

**Are the names personal data?**
These are public records, published by the county. If you use them for marketing (mail, calls, texts), you are responsible for complying with the laws that apply to you, such as the FCRA, TCPA, CAN-SPAM, do-not-call rules and state privacy laws. Do not use this data for credit, employment, insurance or tenant screening decisions.

**My county is not listed.**
Tell us in the Issues tab which county you need.

# Actor input Schema

## `counties` (type: `array`):

The counties to read, from the county clerk's official public records search. Counties are read one after another.

## `dateFrom` (type: `string`):

First recorded date, YYYY-MM-DD. Default: yesterday. At most 31 days per run.

## `dateTo` (type: `string`):

Last recorded date, YYYY-MM-DD, inclusive. Default: yesterday. Counties publish each day once their indexing is done, so the most recent day can still be incomplete.

## `documentCategories` (type: `array`):

Keep only these kinds of documents. Leave empty for every document recorded in the window. Each document gets one category, matched on the county's document type wording.

## `partyName` (type: `string`):

Only documents where this name appears as a grantor or grantee, e.g. "SMITH JOHN" or a company name. Counties index people as LAST FIRST. Leave empty for every document in the window.

## `maxResults` (type: `integer`):

Most documents delivered in this run, across all counties. 0 = no limit.

## `onlyNewSinceLastRun` (type: `boolean`):

For a scheduled daily feed: skips documents this feed already delivered (remembered for 60 days), so a window that overlaps the previous run still delivers each document once.

## `stateStoreName` (type: `string`):

Key-value store in your Apify account that remembers delivered documents. Use a different name for each independent feed.

## Actor input object example

```json
{
  "counties": [
    "dallas.tx",
    "cuyahoga.oh"
  ],
  "maxResults": 1000,
  "onlyNewSinceLastRun": false,
  "stateStoreName": "county-records-feed-state"
}
```

# Actor output Schema

## `documents` (type: `string`):

Recorded document index rows in the default dataset.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "counties": [
        "dallas.tx",
        "cuyahoga.oh"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("regdata/us-county-recorded-documents").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "counties": [
        "dallas.tx",
        "cuyahoga.oh",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("regdata/us-county-recorded-documents").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "counties": [
    "dallas.tx",
    "cuyahoga.oh"
  ]
}' |
apify call regdata/us-county-recorded-documents --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,regdata/us-county-recorded-documents"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/beFihJ4v1ueUOPsLS/builds/gvauBDxgTxCsH2Jbf/openapi.json