# Dallas County Foreclosure Notice Access Review (`realestateapi/property-lead-generator-properties-and-details-scraper`) Actor

Authorization and implementation-status gate only. This local Actor does not request source pages, parse foreclosure notices, identify owners, generate skip-tracing links, or emit generic metadata rows.

- **URL**: https://apify.com/realestateapi/property-lead-generator-properties-and-details-scraper.md
- **Developed by:** [Real Estate API](https://apify.com/realestateapi) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.99 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

## Dallas County Foreclosure Notice Access Review

This folder is associated with the upstream [Property Lead Generator Store listing](https://apify.com/direct_duty/property-lead-generator), which advertises foreclosure leads, owner names, and skip-tracing links. The local implementation does not extract foreclosure events, identify owners, or generate leads.

### Source and limits

The Dallas County Clerk foreclosure-notices index is an index of Notices of Substitute Trustee Sale, not a consolidated property list. Earlier public page text said notices are available for public viewing and individual copies may be purchased per page. The review did not establish permission for automated bulk collection or reuse. On September 30, 2026, Chrome navigation to the official index timed out. No notice PDF or individual public-search record was opened, and no property or owner values were retained.

### Current behavior

- With authorization unconfirmed, the Actor makes zero source requests and writes a policy status to OUTPUT_SUMMARY as SUCCEEDED / SKIPPED_POLICY.
- Setting authorizationConfirmed to true does not enable collection. The local Actor has no source-backed property-event parser, so that run reports FAILED / FAILED with PROPERTY_EVENT_PARSER_UNAVAILABLE, zero requests, and zero dataset rows.
- The Dataset rejects all rows. Generic page metadata, input echoes, synthetic records, and diagnostics are not property-event results.
- Proxy, alternate-client, and notice-detail collection options are not exposed.

This Actor cannot currently produce property records. Do not describe it as a working foreclosure-lead or skip-tracing scraper.

### Validation

Offline tests cover the authorization gate, zero-request behavior, status mapping, and schema contracts. Run npm test, npm run lint, and apify validate-schema from this folder. These checks do not establish live source access, record-level parsing, or permission.

The input authorization field is an operator attestation only. It does not grant or verify permission.

### Runtime dependency remediation

Batch input and JSON storage use the documented Apify REST API and isolated local JSON storage, with environment-only credentials, bounded requests, no platform redirects, and no automatic dataset-POST retry. The Actor does not import the full Apify/Crawlee SDK. Source collection rules and authorization gates are unchanged. This adapter does not provide request queues, proxies, browser automation, encrypted input fields, or long-running system-event migration. Those capabilities are not used by this implementation.

# Actor input Schema

## `authorizationConfirmed` (type: `boolean`):

Attest only if current written permission covers the intended automated collection and reuse. This checkbox does not grant or verify permission. Even when true, this Actor makes zero source requests until a source-backed notice parser is implemented.

## Actor input object example

```json
{
  "authorizationConfirmed": false
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `runSummary` (type: `string`):

No description

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("realestateapi/property-lead-generator-properties-and-details-scraper").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("realestateapi/property-lead-generator-properties-and-details-scraper").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 '{}' |
apify call realestateapi/property-lead-generator-properties-and-details-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,realestateapi/property-lead-generator-properties-and-details-scraper"
        }
    }
}
```

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/nnSeWd1zgcLfbY9TS/builds/gBxVTbSGhO50Ft3m1/openapi.json