# Commercial Real Estate Australia Properties and Details Scraper (`realestateapi/commercialrealestate-properties-and-details-scraper`) Actor Commercial Real Estate Australia Properties and Details Scraper — Permission-gated commercial property parser with uppercase run status and property-only dataset output. - **URL**: https://apify.com/realestateapi/commercialrealestate-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 ## Commercialrealestate Properties and Details Scraper This Actor is a modular parser for detailed Australian commercial property listing pages on [Commercial Real Estate](https://www.commercialrealestate.com.au/). It is designed to normalize property information, pricing, images, location, agent details, public property highlights, area metrics, leasing/sale signals, and NABERS/sustainability fields without putting the extraction logic in `main.js`. ### Important source-use boundary The official [Domain Conditions of Use](https://www.domain.com.au/group/conditions-of-use/) expressly includes the `commercialrealestate.com.au` website and CRE application. The conditions prohibit directly or indirectly scraping or indexing the Product, deploying robots or similar data-gathering methods, and using the Product to build a property database or derivative product. Because no applicable permission is recorded, this Actor defaults to `authorizationConfirmed: false`, reports `SUCCEEDED / SKIPPED_POLICY`, and makes **zero source requests**. It emits no policy diagnostic or placeholder dataset row. Set the flag to `true` only when the caller has applicable written authorization or a licensed feed arrangement that explicitly permits the intended automated use. This input is an attestation by the caller, not a bypass of the source terms. When authorization is confirmed, the Actor still uses a conservative, sequential workflow: it checks `robots.txt`, follows only HTTPS URLs on the official host, applies a delay between requests, caps pages/listings/response bytes, sends no cookies or credentials, and stops on access failures. It never solves CAPTCHAs, bypasses WAFs, uses stealth/proxies, submits enquiry forms, or calls private APIs. The output is a data-integration aid; verify availability, price, listing status, and legal rights with the source and the relevant agent. ### Input - `authorizationConfirmed` (required for any request): written permission or a licensed feed must be in place. - `startUrls`: authorized search or detail pages; defaults to the public for-sale landing page. - `maxItems` and `maxPages`: hard output/request bounds. - `includeImages`, `includeDescription`, and `includeRawData`: control optional public media, description, JSON-LD, and labeled source attributes. - `requestDelayMs`, `timeoutMs`, and `maxResponseBytes`: conservative request controls. ### Output The dataset schema defines more than 65 possible normalized fields, including title/description, listing status/type, property ID, address/suburb/state/postcode/country, latitude/longitude, categories, price text/range/currency/period/unit, auction date/time/location, floor/land/NLA/gross/tenancy/available areas, parking/car spaces, occupancy, yield, rental income, lease term/expiry, zoning/development potential, features/highlights, images/floorplans/videos, agent names/phones/emails, agency details, inspections, last updated, NABERS overall/energy/water/indoor-environment ratings, sustainability text, nearby transport, map URL, raw JSON-LD, and source attributes. These are parser/schema capabilities, not verified live-source coverage: no listing or detail page was opened in the review and no authorized collection was run. Missing values stay `null` or `[]`; the parser does not invent commercial facts. Dataset output contains property records only; failure codes and aggregate counts remain in the run summary. Key-value records: - `SOURCE_METADATA`: target URL, official Conditions of Use URL, policy text, and permission-gate explanation. - `OUTPUT_SUMMARY`: uppercase Actor and run statuses, stored property count, authorization state, request/page counts, rejected URL count, and aggregate failure count. ### Local verification ```bash npm install npm test npm run lint apify validate-schema npm run validate-datasets ``` The default local run is expected to be policy-gated with no network requests. A live authorized run should only be performed by an authorized operator under the source agreement; this repository verification does not use login, Apify API, Apify push/call, private endpoints, or cloud Actor operations. ### 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. # Actor input Schema ## `authorizationConfirmed` (type: `boolean`): Required before any request. Confirm that the caller has written permission or a licensed feed that permits this automated use of commercialrealestate.com.au. ## `startUrls` (type: `array`): HTTPS commercialrealestate.com.au listing/search URLs. Detail pages use /property/; search pages may discover detail links when authorized. ## `maxItems` (type: `integer`): Maximum detailed listing records emitted. ## `maxPages` (type: `integer`): Maximum authorized source pages fetched, including search pages and listing detail pages. ## `includeImages` (type: `boolean`): Keep public image, floorplan, and video URLs found in the listing page. ## `includeDescription` (type: `boolean`): Keep the public listing description when available. ## `includeRawData` (type: `boolean`): Keep bounded JSON-LD objects and labeled source attributes for auditability; raw HTML is never stored. ## `requestDelayMs` (type: `integer`): Serial delay between authorized requests. ## `timeoutMs` (type: `integer`): Maximum time to wait for one authorized page. ## `maxResponseBytes` (type: `integer`): Safety cap for one HTML response. ## Actor input object example ```json { "authorizationConfirmed": false, "startUrls": [ "https://www.commercialrealestate.com.au/for-sale/" ], "maxItems": 5, "maxPages": 5, "includeImages": true, "includeDescription": true, "includeRawData": true, "requestDelayMs": 2000, "timeoutMs": 30000, "maxResponseBytes": 10000000 } ``` # Actor output Schema ## `dataset` (type: `string`): Detailed normalized commercial-property records only. Diagnostics are never emitted as dataset rows. ## `runSummary` (type: `string`): Uppercase Actor and run statuses, stored property count, and aggregate failure counts. ## `sourceMetadata` (type: `string`): Target and official source-policy metadata. # 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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = {}; // Run the Actor and wait for it to finish const run = await client.actor("realestateapi/commercialrealestate-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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = {} # Run the Actor and wait for it to finish run = client.actor("realestateapi/commercialrealestate-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/commercialrealestate-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/commercialrealestate-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 ` 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/RzP8W0YkR39Sg7ANm/builds/I2f1heq3EcpxVnnYL/openapi.json