Dallas County Foreclosure Notice Access Review
Pricing
from $3.99 / 1,000 results
Dallas County Foreclosure Notice Access Review
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.
Pricing
from $3.99 / 1,000 results
Rating
0.0
(0)
Developer
Real Estate API
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
This folder is associated with the upstream Property Lead Generator Store listing, 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.
