RealCommercial.com.au Scraper

Slug: fatihtahta/realcommercial-au-scraper

Overview

RealCommercial.com.au Scraper collects structured commercial property listing data, including listing titles, prices, property types, locations, areas, agents, agencies, media, property attributes, and listing metadata when available. RealCommercial.com.au is one of Australia's major commercial property marketplaces, making its public listing data useful for market research, acquisition analysis, leasing intelligence, and competitive tracking. The actor turns marketplace search results into repeatable JSON records that can be consumed by analytics tools, operational reports, enrichment workflows, and downstream systems. It supports configurable searches across deal type, location, keyword, commercial property category, pricing, area, parking, energy rating, tenure, and output size. The actor is designed for dependable recurring data acquisition with consistent structured output, while reflecting the public data available at the time each run executes.

Why Use This Actor

• Market research and analytics teams: build structured extraction workflows for pricing, supply, location coverage, property mix, and availability analysis across Australian commercial markets.
• Product and content teams: normalize public listing attributes, photos, descriptions, and agency details for internal tools, content operations, and market-facing product experiences.
• Developers and data engineering teams: feed repeatable collection jobs into downstream systems, warehouses, APIs, search indexes, and enrichment pipelines.
• Lead generation and enrichment teams: identify relevant listings, agencies, agents, and commercial opportunities for prospecting, CRM enrichment, and operational qualification.
• Monitoring and competitive intelligence teams: schedule recurring runs to track new listings, listing changes, active inventory, recently sold or leased properties, and category movement.

Common Use Cases

• Market intelligence: monitor commercial property supply, price positioning, availability, locations, property types, and area ranges.
• Lead generation: build targeted prospect lists from public property listings, agency records, and agent contact context where available.
• Competitive monitoring: track changes in listings, agencies, represented properties, pricing language, and commercial property categories over time.
• Catalog and directory building: populate internal databases with structured public commercial property records.
• Data enrichment: add current public listing attributes, property media, location details, and agency metadata to CRM, BI, or analytics datasets.
• Recurring reporting: schedule periodic runs for dashboards, alerts, regional snapshots, and trend analysis.

Quick Start

1. Choose the deal_type you want to collect: buy, lease, sold, or leased.
2. Add one or more location values, such as suburbs, cities, regions, or state-level search areas supported by RealCommercial.com.au.
3. Apply optional filters such as keyword, property_type, price range, area range, parking, NABERS rating, or tenure type.
4. Set a small limit for the first validation run, such as 25 or 50 records per location.
5. Run the actor in Apify Console and inspect the first dataset records to confirm the output shape matches your workflow.
6. Increase coverage, refine filters, enable enrich_data, or schedule the actor once the output is verified.

Input Parameters

The actor accepts search criteria for deal type, result order, location, listing filters, enrichment, and maximum results per location.

Parameter	Type	Description	Default
deal_type	string	Listing channel to collect. Allowed values: buy, lease, sold, leased.	buy
sort_by	string	Result order for matching listings. Allowed values: featured, price-descending, price-ascending, listing-date-newest-first, listing-date-oldest-first.	featured
location	array of strings	Australian suburbs, cities, regions, or state-level search areas to collect. Add one location per array item.	–
keyword	string	Word or phrase used to narrow listing text, such as a business use, property feature, tenant type, or location qualifier.	–
property_type	array of strings	Commercial property categories to include. Allowed values: industrial warehouse, retail, offices, land development, showrooms bulky goods, hotel leisure, medical consulting, commercial farming, other.	–
min_price	integer	Minimum listing price in Australian dollars. Leave empty for no lower price requirement.	–
max_price	integer	Maximum listing price in Australian dollars. Leave empty for no upper price requirement.	–
min_floor_area	integer	Minimum internal floor area in square meters.	–
max_floor_area	integer	Maximum internal floor area in square meters.	–
min_land_area	integer	Minimum land area in square meters.	–
max_land_area	integer	Maximum land area in square meters.	–
min_parking	string	Minimum number of parking spaces. Allowed values: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 25, 50, 100, 250, 500, 1000.	–
nabers_energy_rating	string	Minimum NABERS energy rating threshold on a 1 to 6 scale. Allowed values: 1, 2, 3, 4, 5, 6.	–
tenue_type	string	Tenure filter for occupancy or investment profile. Allowed values: vacant_possession, tenanted_investment.	–
enrich_data	boolean	When enabled, collects richer listing details such as descriptions, attributes, maps, photos, and agency contact information when available.	false
limit	integer	Maximum number of listings to save for each location input. Minimum: 1.	–

Choosing Inputs

Use deal_type first because it defines the primary listing channel: properties for purchase, lease, sold results, or leased results. Use location to control market coverage; broader locations improve discovery, while suburb-level inputs create more targeted datasets. Add property_type, keyword, price, floor area, land area, parking, NABERS rating, and tenure filters when you need more specific qualification criteria. Narrow filters usually produce cleaner, more targeted records, while broader filters are better for market discovery and inventory monitoring. Use sort_by to align collection order with your workflow, such as newest listings for monitoring or price ordering for valuation review. Start with a small limit for validation, then increase it after confirming that the dataset shape and coverage are appropriate.

Example Inputs

Location and Category Discovery

{
  "deal_type": "buy",
  "sort_by": "featured",
  "location": ["Brisbane QLD"],
  "property_type": ["industrial warehouse", "offices"],
  "enrich_data": false,
  "limit": 50
}

Recently Listed Leasing Monitor

{
  "deal_type": "lease",
  "sort_by": "listing-date-newest-first",
  "location": ["Melbourne VIC", "Richmond VIC"],
  "keyword": "showroom",
  "property_type": ["showrooms bulky goods"],
  "limit": 75
}

Targeted Investment Search

{
  "deal_type": "sold",
  "sort_by": "price-descending",
  "location": ["Sydney NSW"],
  "min_price": 1000000,
  "max_price": 10000000,
  "tenue_type": "tenanted_investment",
  "enrich_data": true,
  "limit": 100
}

Output

Output Destination

The actor writes RealCommercial.com.au results to the default Apify dataset. Each normal row is a property_listing record with a normalized real estate structure instead of a shallow flat object.

Record Envelope and Stable Identifiers

Use record_id as the primary idempotency key. It is the RealCommercial listing id when available. For globally scoped storage, combine record_id with source_context.source_domain or source_context.seed_value.

source_context.fingerprint remains available as a run-level collection fingerprint. It is useful for comparing records gathered from different searches or repeated scheduled runs.

Example: Property Listing Record

{
  "record_type": "property_listing",
  "record_id": "500123456",
  "source_context": {
    "source_name": "RealCommercial.com.au",
    "source_domain": "realcommercial.com.au",
    "source_url": "https://api.realcommercial.com.au/listing-ui/searches",
    "listing_url": "https://www.realcommercial.com.au/for-sale/property-12-18-example-road-port-melbourne-vic-3207-500123456",
    "seed_id": "example-seed-001",
    "seed_type": "location",
    "seed_value": "Port Melbourne VIC 3207",
    "page_index": 1,
    "detail_source_url": "https://api.realcommercial.com.au/listing-ui/listings/500123456?channel=for-sale",
    "is_enriched": true,
    "external_ids": {
      "listing_id": "500123456"
    },
    "domain": "api.realcommercial.com.au",
    "fingerprint": "example-fingerprint-500123456",
    "scraped_at": "2026-05-08T20:34:42.683856+00:00"
  },
  "entity": {
    "title": "Modern Industrial Facility with Office and Secure Yard",
    "url": "https://www.realcommercial.com.au/for-sale/property-12-18-example-road-port-melbourne-vic-3207-500123456",
    "description": "Modern industrial facility with clear-span warehouse space, refurbished office accommodation, secure yard, multiple roller doors, and convenient access to major arterial routes.",
    "description_html": "Modern industrial facility with clear-span warehouse space, refurbished office accommodation, secure yard, multiple roller doors, and convenient access to major arterial routes.<br/><br/>Available for sale with vacant possession.",
    "external_ids": {
      "listing_id": "500123456"
    }
  },
  "listing": {
    "listing_id": "500123456",
    "listing_status": "active",
    "available_channels": [
      "for-sale",
      "for-lease"
    ],
    "last_updated_at": "2026-05-01T04:15:00Z"
  },
  "pricing": {
    "price_text": "CONTACT AGENT",
    "raw": {
      "for_sale": {
        "display_price": "CONTACT AGENT",
        "is_price_hidden": true
      },
      "for_lease": {
        "display_price": "CONTACT AGENT",
        "is_price_hidden": true
      }
    }
  },
  "location": {
    "street_address": "12-18 Example Road",
    "suburb_address": "Port Melbourne, VIC 3207",
    "suburb": "Port Melbourne",
    "state": "VIC",
    "postcode": "3207",
    "marketing": {
      "region": "vic_melbourne___region,vic_inner_melbourne___region",
      "suburb": "port_melbourne"
    },
    "coordinates": {
      "latitude": -37.832104,
      "longitude": 144.921418,
      "precision": "street"
    },
    "map_thumbnail_url": "https://www.realcommercial.com.au/example-assets/map-thumbnail-500123456.png",
    "map_zoom_level": 16
  },
  "property": {
    "area": "2450 m2",
    "property_types": [
      "Industrial/Warehouse",
      "Offices"
    ],
    "floor_area": "2450 m2",
    "land_area": "6200 m2"
  },
  "media": {
    "photos": [
      {
        "url": "https://www.realcommercial.com.au/example-assets/listings/500123456/image0.jpg",
        "url_template": "https://www.realcommercial.com.au/example-assets/listings/500123456/{size}/image0.jpg",
        "alt": "12-18 Example Road Port Melbourne VIC 3207 - Image 1"
      }
    ],
    "video": {
      "youtube_id": "AbC123XyZ90"
    },
    "has_tour": false
  },
  "relationships": {
    "agents": [
      {
        "name": "Jordan Smith",
        "image_url": "https://www.realcommercial.com.au/example-assets/agents/jordan-smith.jpg"
      }
    ],
    "agencies": [
      {
        "id": "EXMELB",
        "name": "Example Commercial - Melbourne",
        "salespeople": [
          {
            "id": "900001",
            "name": "Jordan Smith",
            "phone": {
              "display": "03 9000 1000",
              "dial": "+61390001000"
            }
          }
        ],
        "phone": {
          "display": "03 9000 1100",
          "dial": "+61390001100"
        }
      }
    ],
    "similar_listings": [
      {
        "id": "500123457",
        "url": "https://www.realcommercial.com.au/for-sale/property-20-sample-street-southbank-vic-3006-500123457",
        "title": "City Fringe Warehouse and Office",
        "price": "For Sale by EOI"
      }
    ]
  },
  "metrics": {
    "days_active": 42
  },
  "attributes": {
    "highlights": [
      "Clear-span warehouse",
      "Secure yard"
    ],
    "branding": {
      "color": "#1f5f8b",
      "logo": {
        "alt": "Example Commercial - Melbourne",
        "url": "https://www.realcommercial.com.au/example-assets/agencies/example-commercial-logo.jpg"
      }
    },
    "product": "premium",
    "tenure_type": "vacant",
    "multiple_properties": false,
    "high_quality_listing": false,
    "raw_attributes": [
      {
        "id": "floor-area",
        "label": "Floor area",
        "value": "2450 m2"
      }
    ]
  }
}

Field Reference

Property Listing Record

record_type (string, required): Stable row discriminator. Normal listing rows use property_listing.

record_id (string, required): Stable RealCommercial listing identifier.

source_context (object, required): Source and crawl context, including source name, source domain, source URL, listing URL, seed metadata, page index, enrichment status, external ids, fingerprint, and scrape timestamp.

entity (object, required): Primary listing identity, including title, public URL, plain-text description, HTML description, and source ids when available.

listing (object, optional): Listing lifecycle and channel details, including listing id, listing status, available channels, and last updated time.

pricing (object, optional): Display price text plus raw sale, lease, sold, or leased price objects when detail data is available.

location (object, optional): Address, suburb, state, postcode, marketing geography, coordinates, map thumbnail, and map zoom metadata.

property (object, optional): Property categories and physical attributes such as display area, floor area, land area, and parking spaces.

media (object, optional): Photos, video metadata, tour flags, tour objects, and listing website links when available.

relationships (object, optional): Embedded agents, agencies, agency salespeople, contact fields, and similar listing summaries.

metrics (object, optional): Source-provided listing metrics such as days active.

attributes (object, optional): Source-specific details that do not fit a stronger normalized group, including highlights, branding, product tier, tenure type, quality flags, channel authority, and raw property attributes.

Data Quality, Guarantees, and Handling

• Structured records: results are normalized into predictable JSON objects for downstream use.
• Best-effort extraction: fields may vary by region, session, availability, source presentation, or marketplace experiments.
• Optional fields: null-check optional fields in downstream code, especially contact, media, pricing, map, and enrichment fields.
• Deduplication: use id as the strongest stable key; use url or id plus source_context.seed_value when your workflow needs source-scope separation.
• Freshness: results reflect the publicly available data at run time.
• Repeated runs: use the recommended idempotency key when syncing data into warehouses, CRMs, search indexes, or monitoring systems.

Tips for Best Results

• Start with a small limit to validate the output shape before scaling up.
• Use one geography, property category, or deal type per run when you need cleaner segmentation.
• Leave optional filters empty when the goal is broad discovery.
• Add filters gradually to understand how each field changes coverage.
• Use sort_by with listing-date-newest-first for monitoring workflows focused on new inventory.
• Enable enrich_data when you need descriptions, media, attributes, and richer agency context.
• Use stable identifiers for deduplication when storing results over time.

How to Run on Apify

1. Open the Actor in Apify Console.
2. Configure the available input fields for the target scope.
3. Set the maximum number of outputs to collect with limit.
4. Click Start and wait for the run to finish.
5. Open the dataset and review the first records.
6. Download results in JSON, CSV, Excel, or other supported formats.

Scheduling & Automation

Scheduling

Automated Data Collection

Schedule runs to keep commercial property datasets fresh for reporting, monitoring, and enrichment workflows. Recurring runs are especially useful when tracking new listings, pricing changes, geographic availability, or recently sold and leased records.

• Navigate to Schedules in Apify Console
• Create a new schedule, such as daily, weekly, or custom cron
• Configure input parameters
• Enable notifications for run completion
• Add webhooks for automated processing

Integration Options

• BI dashboards: monitor pricing, availability, property type movement, and geographic coverage over time.
• Data warehouses: store historical listing snapshots for reporting, modeling, and longitudinal analysis.
• CRM enrichment: sync public listing, agency, and agent attributes into account or lead records.
• Google Sheets or Airtable: review smaller market samples, qualification lists, and operational exports.
• Webhooks: trigger validation, notification, or ingestion workflows after each completed run.
• Alerts and reporting: notify teams when new listings match target locations, price ranges, categories, or tenure profiles.

Export Formats and Downstream Use

Apify datasets can be exported or consumed by downstream systems for reporting, review, and automated ingestion.

• JSON: for APIs, applications, and data pipelines.
• CSV or Excel: for spreadsheet workflows and manual review.
• API access: for automated ingestion into internal systems.
• BI and warehouses: for reporting, dashboards, and historical analysis.

Performance

Estimated run times:

• Small runs (< 1,000 outputs): ~3–5 minutes
• Medium runs (1,000–5,000 outputs): ~5–15 minutes
• Large runs (5,000+ outputs): ~15–30 minutes

Execution time varies based on filters, result volume, and how much information is returned per record. Highly filtered runs can finish faster, while broad discovery or detail-rich records may take longer.

Limitations

• Availability depends on what RealCommercial.com.au publicly exposes at run time.
• Some optional fields may be missing on sparse records or listings with limited public detail.
• Very broad searches may take longer or require higher limit values to capture the desired coverage.
• Target-side changes can affect field availability, naming, or presentation.
• Regional, account, or availability differences may change visible results.
• Pricing text can vary because some listings display guidance, ranges, or contact-only pricing rather than numeric values.

Troubleshooting

• No results returned: check filters, location spelling, property category selection, and whether the target has matching public records.
• Fewer results than expected: broaden filters, raise limit, or verify that the selected location and deal type contain enough matching records.
• Some fields are empty: optional fields depend on what each record publicly provides.
• Run takes longer than expected: reduce scope, lower limit for validation, or split broad collection into smaller segments.
• Output changed: compare the current output with the field reference and report a small sample if support is needed.

FAQ

What data does this actor collect?

It collects public RealCommercial.com.au commercial property listing data, including titles, prices, property types, areas, locations, contacts, agencies, media, descriptions, attributes, source context, and pricing details when available.

Can I filter by location, category, date, price, or other criteria?

You can filter by deal type, location, keyword, property type, price range, floor area, land area, parking, NABERS energy rating, tenure type, and result order. The schema does not include a direct date-window input, but sort_by supports newest-first and oldest-first listing order.

Why did I receive fewer results than my limit?

The limit is a maximum, not a guarantee. A run may return fewer records when the selected location, deal type, or filters have fewer matching public listings.

Can I schedule recurring runs?

Yes. Use Apify Schedules to run the actor daily, weekly, or on a custom cron schedule.

How do I avoid duplicates across runs?

Use record_id as the primary idempotency key. If you need to preserve separate records by input scope, use a composite key such as record_id plus source_context.seed_value.

Can I export the data to CSV, Excel, or JSON?

Yes. Apify datasets support exports in JSON, CSV, Excel, and other formats supported by the Apify platform.

Does this actor collect private data?

The actor is intended to collect publicly available listing information from RealCommercial.com.au. Users are responsible for ensuring their use of the data complies with applicable laws, regulations, and platform terms.

When should I enable enrichment?

Enable enrich_data when your workflow needs richer listing details such as descriptions, media, property attributes, map context, and agency contact information. Keep it disabled for faster validation runs or lighter datasets.

What should I include when reporting an issue?

Include the input used with sensitive values redacted, the run ID, expected versus actual behavior, and a small output sample when it helps explain the issue.

Compliance & Ethics

Responsible Data Collection

This actor collects publicly available commercial property listing information from https://www.realcommercial.com.au for legitimate business purposes, including:

• Commercial real estate research and market analysis
• Listing monitoring, valuation review, and operational reporting
• CRM enrichment, lead qualification, and market intelligence workflows

Users are responsible for ensuring that their use of collected data complies with applicable laws, regulations, and the target site's terms. This section is informational and not legal advice.

Best Practices

• Use collected data in accordance with applicable laws, regulations, and the target site's terms
• Respect individual privacy and personal information
• Use data responsibly and avoid disruptive or excessive collection
• Do not use this actor for spamming, harassment, or other harmful purposes
• Follow relevant data protection requirements where applicable, such as GDPR and CCPA

Support

For help, use the actor page or Issues section. Include the input used with sensitive values redacted, the run ID, expected versus actual behavior, and a small output sample when available.