# Louisville KY Code Enforcement Lien Orders: Owners & Fines (`lienintel/louisville-ky-code-enforcement-liens`) Actor

Louisville Metro, Kentucky code enforcement final orders sent to lien holders: case number, owner name and mailing address, property, final citation amount, inspection result and notification date. Filter by owner, address, date and amount.

- **URL**: https://apify.com/lienintel/louisville-ky-code-enforcement-liens.md
- **Developed by:** [LienIntel - UCC & Secured Lending Intelligence.](https://apify.com/lienintel) (community)
- **Categories:** Business, Lead generation, Automation
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $15.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

[![Louisville KY Code Enforcement Lien Orders: Owners & Fines](https://scrapers.lat/banners/louisville-ky-code-enforcement-liens.png)](https://console.apify.com/actors/Q0cG8HmWK5mx4vxml/input)

## Louisville KY Code Enforcement Lien Orders: Owners & Fines

Louisville Metro, Kentucky code enforcement final orders sent to lien holders: case number, owner name and mailing address, property, final citation amount, inspection result and notification date. Filter by owner, address, date and amount.

Here is one real record from this actor.

```json
{
  "case_number": "ENF-LEAD-25-000210-11",
  "case_status": "Final Order",
  "final_order_state": "Final By Citation",
  "notification_date": "2026-10-07",
  "final_citation_amount_usd": 2000,
  "owner_name": "FSM, OF BROADWAY LLC",
  "owner_address": "212 N 2ND ST PMB 100",
  "owner_city": "RICHMOND",
  "owner_state": "KY",
  "owner_zip": "40475-1408",
  "street_number": 3620,
  "street_direction": "W",
  "street_name": "BROADWAY",
  "street_suffix": null,
  "inspection_result": "Corrective Order Citation",
  "inspection_date": "2026-10-07",
  "latitude": 38.24968597,
  "longitude": -85.81201251,
  "case_url": "https://aca-prod.accela.com/LJCMG/Cap/CapDetail.aspx?Module=Enforcement&TabName=Enforcement&capID1=26CAP&capID2=00000&capID3=05NUB&agencyCode=LJCMG",
  "record_id": "ENF-LEAD-25-000210-11|1",
  "state": "KY",
  "jurisdiction": "Louisville Metro",
  "source": "Louisville Metro Government",
  "source_page": "https://data.louisvilleky.gov/",
  "observed_at": "2026-11-05T21:42:23.815Z"
}
```

**[Input](https://apify.com/lienintel/louisville-ky-code-enforcement-liens/input-schema) | [Output](https://apify.com/lienintel/louisville-ky-code-enforcement-liens/output-schema) | [Pricing](https://apify.com/lienintel/louisville-ky-code-enforcement-liens/pricing)**

![Coverage](https://img.shields.io/badge/Coverage-Louisville%2C%20Kentucky-blue)
![Output](https://img.shields.io/badge/Output-JSON%20%7C%20CSV%20%7C%20Excel-orange)
![Billing](https://img.shields.io/badge/Billing-Pay%20per%20result-brightgreen)

### Table of contents

- [What you get](#what-you-get)
- [Input and filters](#input-and-filters)
- [Use cases](#use-cases)
- [Coverage and freshness](#coverage-and-freshness)
- [Pricing](#pricing)
- [Comparison with other Apify actors](#comparison-with-other-apify-actors)
- [Related LienIntel actors](#related-lienintel-actors)
- [FAQ](#faq)
- [Run it through the Apify API](#run-it-through-the-apify-api)

### What you get

- **The case.** Case number, status, final order state and a link to the official case page.
- **The owner.** Owner name and full mailing address.
- **The property.** Street address and coordinates.
- **The money.** Final citation amount, with notification and inspection dates.
- **A stable `record_id`** and the date the record was collected, with one flat record per row.

Each record can carry these 25 fields. A field the source does not publish for a record comes back as `null`.

| Field | Type | Description |
|---|---|---|
| `case_number` | string | Case number |
| `case_status` | string | Case status |
| `final_order_state` | string | Final order state |
| `notification_date` | string | Notification date |
| `final_citation_amount_usd` | integer | Final citation amount usd |
| `owner_name` | string | Owner name |
| `owner_address` | string | Owner address |
| `owner_city` | string | Owner city |
| `owner_state` | string | Owner state |
| `owner_zip` | string | Owner zip |
| `street_number` | integer | Street number |
| `street_direction` | string | Street direction |
| `street_name` | string | Street name |
| `street_suffix` | string | Street suffix |
| `inspection_result` | string | Inspection result |
| `inspection_date` | string | Inspection date |
| `latitude` | number | Latitude |
| `longitude` | number | Longitude |
| `case_url` | string | Case url |
| `record_id` | string | Record id |
| `state` | string | State |
| `jurisdiction` | string | Jurisdiction |
| `source` | string | Source |
| `source_page` | string | Source page |
| `observed_at` | string | Observed at |

### Input and filters

All inputs are optional.

| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| `maxFilings` | integer | no | `100` | Maximum records to return. Free Apify plans are capped at 10 per run. |
| `names` | array | no | (none) | Contains match, one or more names. |
| `address` | string | no | (none) | Contains match on the address. |
| `minAmount` | integer | no | (none) | Only records at or above this amount. |
| `dateFrom` | string | no | (none) | Earliest date, as YYYY-MM-DD. |
| `dateTo` | string | no | (none) | Latest date, as YYYY-MM-DD. |

A working example to paste into the Input tab:

```json
{
  "maxFilings": 10
}
```

### Use cases

- Find Louisville properties with final code enforcement orders and citation amounts, with owner mailing address.

### Coverage and freshness

Data comes from official public records as published by Louisville Metro Government. Check the original record before making a legal or financial decision.

### Pricing

This actor uses pay-per-event pricing. These are the current Apify prices, read on 2026-11-06.

| Event | Price | When it is charged |
|---|---|---|
| `result` | $0.015 | Each record delivered to your dataset |
| `apify-actor-start` | $0.003 | When a run starts, once per GB of run memory with a minimum of one |

At the default 512 MB, a run that delivers 100 records costs $1.503.

- Apify asks for a maximum spend of at least $0.018 per run on this actor.
- Accounts on the free Apify plan receive up to 10 results per run.
- If nothing matches or the source fails, you get one row with an `error` field and no `result` charge. The start event still applies to the run.
- Set a maximum cost per run and the actor stops delivering results when it reaches that limit.

### Comparison with other Apify actors

No dedicated actor for this source on the Apify Store as of November 2026. We searched the public Store on 2026-11-06 with queries including "Louisville tax", "Louisville delinquent" and "Louisville lien", and we reviewed the listings for this source and data type. Store listings change, so run the same search before you rely on this.

### Related LienIntel actors

Other public LienIntel actors for the same buyer:

- [Fayette County KY UCC Fixture & Tax Lien Search](https://apify.com/lienintel/fayette-county-ky-lien-filings): county recorded liens and UCC filings in Kentucky
- [Alaska Recorder UCC & Lien Filings: Debtors & Lenders](https://apify.com/lienintel/alaska-recorder-ucc-lien-filings): county recorded liens and UCC filings in Alaska
- [Allegan County MI UCC & Lien Records Search](https://apify.com/lienintel/allegan-county-mi-lien-filings): county recorded liens and UCC filings in Allegan County, Michigan
- [Allegheny County PA Tax Liens: Dockets, Amounts & Assignees](https://apify.com/lienintel/allegheny-county-pa-tax-liens): delinquent property tax records in Allegheny County, Pennsylvania

### FAQ

**Is the amount a final payoff?**

No. Use it as published on the order and confirm the current payoff with the city.

**What can I filter by?**

The input accepts `names`, `address`, `minAmount`, `dateFrom` and `dateTo`. The Input and filters section explains each one.

**Can I run it on a schedule?**

Yes. Create an Apify schedule for the actor, then send the dataset to your database, a spreadsheet or a webhook.

### Run it through the Apify API

Replace `<TOKEN>` with your Apify API token.

```bash
curl -X POST "https://api.apify.com/v2/acts/lienintel~louisville-ky-code-enforcement-liens/run-sync-get-dataset-items?token=<TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"maxFilings": 10}'
```

With the Apify CLI:

```bash
apify call lienintel/louisville-ky-code-enforcement-liens --input '{"maxFilings": 10}'
```

Every run writes to a dataset that you can export as JSON, CSV or Excel from the Storage tab or through the Apify API.

***

*LienIntel is an independent data provider and is not affiliated with any government office named on this page. Records are public and are provided for research and workflow automation. This is not a certified search and not a consumer report under the FCRA.*

# Actor input Schema

## `maxFilings` (type: `integer`):

Maximum records to return. Free Apify plans are capped at 10 per run.

## `names` (type: `array`):

Contains match, one or more names.

## `address` (type: `string`):

Contains match on the address.

## `minAmount` (type: `integer`):

Only records at or above this amount.

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

Earliest date, as YYYY-MM-DD.

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

Latest date, as YYYY-MM-DD.

## Actor input object example

```json
{
  "maxFilings": 10
}
```

# Actor output Schema

## `results` (type: `string`):

One flat record per row.

# 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 = {
    "maxFilings": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("lienintel/louisville-ky-code-enforcement-liens").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 = { "maxFilings": 10 }

# Run the Actor and wait for it to finish
run = client.actor("lienintel/louisville-ky-code-enforcement-liens").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 '{
  "maxFilings": 10
}' |
apify call lienintel/louisville-ky-code-enforcement-liens --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,lienintel/louisville-ky-code-enforcement-liens"
        }
    }
}
```

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/Q0cG8HmWK5mx4vxml/builds/yJefDlesux7YDsPdP/openapi.json