All Property Management Company Profiles Scraper

CSV rank 3573. This Actor normalizes public property-manager directory profiles, not home-sale or rental listings. Chrome showed the public directory, but blocked both robots.txt and the Actor's public API endpoint. The visible Website Terms link leads to Buildium's Website Terms of Service, updated August 6, 2025, which prohibits scraping and copying without a written content license. Section 19 refers separately to Buildium's Terms of Use for contracted services, including offerings on allpropertymanagement.com, so their applicability to the public directory remains unresolved. No applicable written license is recorded. The Actor therefore makes zero source requests by default. Do not run a live collection unless current source-use rules have been reviewed and the required authorization is recorded.

Input

{ "state": "GA", "city": "ATLANTA", "maxItems": 3, "includeDetails": true, "timeoutSecs": 20 }

The safe default is {}. It finishes with status: "SUCCEEDED" and collectionStatus: "SKIPPED_POLICY", writes no dataset row, and sends no source requests. Only after reviewing current source terms and robots policy in Chrome and obtaining any required written authorization, use:

{ "authorizationConfirmed": true, "state": "GA", "city": "ATLANTA", "maxItems": 3, "includeDetails": true, "timeoutSecs": 20 }

That checkbox is an operator attestation and does not grant permission. The endpoint is also constrained to the official API host, redirects are refused, and response bodies are bounded to 2 MB.

The dataset accepts only source-backed manager profiles with an official API endpoint, positive manager ID, company name, and at least one substantive profile fact. A name-and-ID-only candidate is rejected. The OUTPUT summary reports aggregate failureDetails and keeps all diagnostics out of the dataset. Top-level status is SUCCEEDED or FAILED; runStatus describes the collection outcome. A clean empty search is SUCCEEDED/COMPLETED, the default policy gate is SUCCEEDED/SKIPPED_POLICY with zero requests and zero current-run rows, failures with no saved real rows are FAILED/FAILED with a nonzero native exit, and failures after saved real rows are SUCCEEDED/PARTIAL with a successful exit.

Local verification

npm install
npm test
npm run lint
npm run validate:saved
apify validate-schema

Do not use --purge or run this Actor against the existing default storage; it contains three historical manager rows and an OUTPUT summary. The direct API and robots.txt remain blocked in Chrome. The linked Buildium Website Terms prohibit automated extraction and copying absent a written license, while the referenced separate Buildium service terms and their applicability to the public directory remain unresolved. Offline tests use mocks and are not evidence of live collection permission or access.

Storage runtime and dependency remediation (2026-10-03)

This native-fetch Actor no longer installs the unused SDK/crawler/cache chain. Node 22 and pinned @apify/log provide the runtime and censoring logger. src/platform.js implements only input reads, append-only dataset writes, JSON summaries and exit handling through the documented Apify storage API and isolated local files. Cloud tokens use the authorization header on the fixed official API host; storage redirects and automatic append retries are disabled. This adapter does not implement request queues, billing events, input-secret decryption or migration; none is used by this Actor. Source gates and restrictions remain in force. Production dependency audits run against the actual lockfile and during the Docker build. An audit pass establishes the npm dependency result, not source extraction or an operating-system image audit.