# All Property Management Company Profiles Scraper (`realestateapi/all-property-management-properties-and-details-scraper`) Actor

Permission-gated collection of public property manager directory profiles; source requests default to off until terms and authorization are verified.

- **URL**: https://apify.com/realestateapi/all-property-management-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

## 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

```json
{ "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:

```json
{ "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

```powershell
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](https://docs.apify.com/api/v2/dataset-items-post) 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.

# Actor input Schema

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

Confirm only after the source terms and robots policy have been reviewed in Chrome and any required written authorization permits this collection and reuse. False by default; this control does not itself grant permission.

## `state` (type: `string`):

Two-letter US state code used by the public directory endpoint.

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

US city name used by the public directory endpoint.

## `category` (type: `string`):

Optional exact public category such as Single Family, Multi-Family, or Commercial.

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

Maximum unique public manager records to emit.

## `includeDetails` (type: `boolean`):

Fetch each selected manager's public profile endpoint for description and address enrichment.

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

Timeout for each public endpoint request.

## Actor input object example

```json
{
  "authorizationConfirmed": false,
  "state": "GA",
  "city": "ATLANTA",
  "category": "",
  "maxItems": 10,
  "includeDetails": true,
  "timeoutSecs": 20
}
```

# 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/all-property-management-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/all-property-management-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/all-property-management-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/all-property-management-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/R2Fti21yL14DZyPhY/builds/FQGJTLPWTCNU8FCfP/openapi.json