# Dallas CAD Properties and Details Scraper (`realestateapi/dallas-cad-properties-and-details-scraper`) Actor

Search public Dallas Central Appraisal District records by owner, address, business, account, or property URL. Extract appraisal values, exemptions, estimated taxes, building facts, ownership, and parcel details from public DCAD pages.

- **URL**: https://apify.com/realestateapi/dallas-cad-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 Cad Properties and Details Scraper

CSV rank: **4107**. Store listing: [spry_frame/dallas-cad-scraper](https://apify.com/spry_frame/dallas-cad-scraper).

This Actor uses the public Dallas Central Appraisal District search and detail pages. It can open supplied account numbers or property URLs directly, or submit bounded public searches by owner, street address, city, or business name. Detail records preserve the flat fields and group the same source-backed values under `location`, `ownerDetails`, `propertyDetails`, `appraisalDetails`, `taxDetails`, `sourceMetadata`, and `sourceFields`. The property group includes land parcel rows with source-provided units when present.

The site uses a public ASP.NET form. The Actor carries only the public form state required for a normal search, does not log in, bypass a CAPTCHA, or access private endpoints, and retains the exact DCAD detail URL for every record. DCAD’s tax estimates are informational and should not be treated as an official tax bill.

### Current review status

Chrome review of DCAD's homepage, Open Records, and Data Products pages on 2026-09-27 confirmed the published data-update date and public data-product information, but did not establish a dataset-specific reuse license or verify current property-level extraction. The three saved rows are historical local output and were preserved. They are not current property-level source evidence.

### Input

No real property is queried by default. Provide `propertyUrls`, `accountNumbers` with `accountType` (`Res`, `Com`, or `BPP`), `ownerName`, `streetName` (optionally with `streetNumber` and `city`), or `businessName`, with `maxItems` and `timeoutSecs` bounds. Owner searches follow the DCAD page's instructions: enter a last name and at least two letters of the first name. Address searches omit street type and map city labels using the values published in DCAD's search form.

### Local verification

Run summaries use `SUCCEEDED` / `COMPLETED` for clean completion, including a valid empty result; `SUCCEEDED` / `PARTIAL` when at least one property record was saved before a later request or storage failure; and `FAILED` / `FAILED` when failures leave no property records. Only validated property records are written to the dataset. Failure counts stay in the `OUTPUT` key-value summary, and only `FAILED` exits with a non-zero process code.

```bash
npm install
apify validate-schema
node --test test/*.test.js
npm run check
npm run validate
```

These are offline checks. No property/owner lookup, source request, or live Actor run was made during the browser review. Preserve existing storage; do not use purge commands. `maxItems` is 1–50 for an explicitly authorized operational run. Tax estimates are informational, not official tax bills. DCAD warns that title research should be performed with the appropriate County Clerk and that its website is not a legal document.

### Runtime dependency remediation — October 3, 2026

This bounded implementation only uses JSON input, dataset appends, JSON key-value storage and (where needed) dataset counts. Its project-local `src/platform.js` now uses the official Apify REST storage contract in Cloud and SDK-compatible local JSON files, with Apify’s censoring logger. Removing the unused full SDK/Crawlee runtime removes its transitive crawler, cache, FTP and proxy dependency graph; it does not claim that those vulnerable paths were unreachable. Source permission gates, transport restrictions, output fields and historical storage are preserved. The adapter does not implement queues, migration, automatic retries or non-JSON storage; no such methods are used by this Actor. Tokens remain environment-only bearer headers to the fixed official API host.

The Docker build uses Node 24 and deterministic `npm ci --omit=dev --ignore-scripts`. `npm run test:platform` verifies local append/preservation, Cloud storage routing and authenticated write failures. Existing parser/policy tests remain necessary. Technical dependency remediation and a no-request gate run do not qualify live source extraction.

## Source request boundaries

Property URLs must use approved HTTPS DCAD detail paths, without credentials, alternate ports, or extra query parameters. The client does not follow redirects or retry access denials or verification challenges. An access boundary stops all remaining source requests. Responses are limited to 2 MB. `OUTPUT.sourceRequestCount` counts native source requests; injected offline transports report `null`. Empty input makes zero source requests. Current remediation verification uses empty input because source-use prerequisites remain unresolved.

# Actor input Schema

## `accountNumbers` (type: `array`):

Optional public DCAD account IDs; these open detail pages directly. No account number is queried by default.

## `propertyUrls` (type: `array`):

Optional public DCAD residential, commercial, or BPP AcctDetail URLs.

## `accountType` (type: `string`):

Type used when accountNumbers is provided. Direct detail URLs may use their own residential, commercial, or BPP page type.

## `ownerName` (type: `string`):

Owner search text. DCAD asks for the full last name and at least two first-name letters.

## `streetName` (type: `string`):

Street name without street type for the public DCAD address search.

## `streetNumber` (type: `string`):

Optional house number for the public DCAD address search.

## `city` (type: `string`):

Optional city label from the current DCAD list; the Actor resolves it to the form's internal option value.

## `businessName` (type: `string`):

Optional business name for the public DCAD business search.

## `maxItems` (type: `integer`):

Maximum detail records to emit.

## `timeoutSecs` (type: `integer`):

Timeout for each public DCAD request.

## Actor input object example

```json
{
  "accountNumbers": [],
  "propertyUrls": [],
  "accountType": "Res",
  "maxItems": 10,
  "timeoutSecs": 30
}
```

# 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/dallas-cad-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/dallas-cad-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/dallas-cad-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/dallas-cad-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/TmZuzBnUuTe4OKMoo/builds/fqdNTUzvXjlXRh8sR/openapi.json