CSV rank: 4107. Store listing: 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.

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.