Property24 Data Starts With the Data Category You Actually Need
Property24 is operated in South Africa by HomeFind24 (Pty) Ltd, which Property24’s current Data Processing Agreement also identifies as Property24. (Property24 Data Processing Agreement)
For a property-data team, the useful first question is not: “Can we scrape Property24?” It is: “Do we need marketplace listings, rental data, registered sale information, transfer history, property reports, or a combination of those?”
Those are materially different requirements.
A useful project should define:
- South African provinces, cities, municipalities, and suburbs in scope
- for-sale versus rental listings
- active listing data versus sold/transfer data
- required property attributes
- floor-size versus erf-size requirements
- whether agency information is necessary and permitted
- whether recurring listing observations are required
- whether licensed Property24 Property Data products are relevant
- intended use and redistribution requirements
- source authorization/licence
- delivery destination
NenoData’s current Real Estate Data Scraping service NenoData’s current Real Estate Data Scraping service uses this same source-first approach: it scopes sources, markets, fields, schedules, and destinations before implementation and confirms source/field feasibility rather than assuming coverage.
What Property24 Listing Data May Be Relevant?
The actual field set depends on the approved source, page type, property category, and project scope.
| Data category | Potential fields | Qualification |
|---|---|---|
| Listing identity | listing/source ID, source URL, listing type, status | Source dependent |
| Transaction/marketing type | for sale, to rent, sold-page context where applicable | Keep explicit |
| Pricing | asking sale price, asking rent, ZAR, price per m² where displayed | Marketplace price concepts |
| Property | property type, bedrooms, bathrooms, parking | Availability varies |
| Size | floor size, erf/land size, unit | Preserve measurement type |
| Location | suburb, city/municipality, province | Granularity varies |
| Availability | source-visible availability/status | Source dependent |
| Agency context | agency/company information where permitted | Personal/contact data requires separate review |
| Observation metadata | observed_at, first_seen, last_seen | Only where recurring access is approved |
| Source metadata | source URL, source category, source record type | Useful for provenance |
This is an illustrative schema, not a guarantee that every Property24 page exposes every field.
Asking Price and Registered Sold Price Are Different Data Concepts
This distinction is one of the most important for South African property analytics. Property24 Property Trends page explicitly compares:
- the average asking price of Property24 listings
- the average selling price of sales registered in the Deeds Office
Those values must never be collapsed into one generic price.
| Concept | Meaning |
|---|---|
| asking_sale_price_zar | Current source-visible listing asking price |
| asking_rent_zar | Current rental asking price |
| registered_sale_price_zar | Registered transfer/sale value from an appropriate source |
| price_source | Listing portal, Deeds Office-derived source, licensed report, etc. |
| observed_at | Timestamp for marketplace observation |
| transfer_date | Transaction-event date where available |
This distinction matters for:
NenoData’s Real Estate Transaction Data service should continue to treat recorded transactions as a separate workflow with its own source, lineage, schema, and validation rather than as a relabelled marketplace listing.
Marketplace Listings and Property24 Property Data Are Different Products
Property24 has a public property marketplace. It also currently sells a separate Property Data product. Property24’s current Property Data page advertises access to:
- a database of more than 9 million properties
- registered-property searching
- property reports
- transfer reports
- sectional scheme reports
- area reports
Marketplace asking prices, registered transfers, and valuation/report outputs are different data concepts.
Property
location · type · floor size · erf size
Marketplace Listing
asking price · status · agency
Asking Price Obs.
observed_at · asking_price_zar
Registered Transfer
Deeds Office source · transfer date
Registered Sold Price
registered_sale_price_zar
Property Report
licensed product · separate access
Valuation / AVM
valuation_amount_zar
Do not claim NenoData has access to Property Data simply because Property24 offers it.
Property, Listing, and Transfer Should Be Separate Entities
A robust South African property-data model should distinguish:
Property
The underlying real-world asset.
- internal/property identifier
- location
- property type
- floor size
- erf size
Listing
A marketplace marketing record.
- listing ID
- source URL
- listing status
- asking price
- agency context where permitted
- first observed
- last observed
Listing Observation
A time-specific view of marketplace information.
- observed asking price
- availability
- status
- observed_at
Transfer
A registered property event.
- transfer date
- registered sale/consideration amount
- source authority
- source reference
Report / Valuation
A separate analytical or report output.
- valuation amount
- valuation/report type
- source/product
- report date where applicable
This prevents a common analytical error: one Property24 listing does not automatically equal one registered sale event.
Floor Size and Erf Size Should Never Be Combined Into One Generic Area Field
South African property records often require two different size concepts: floor size (building/internal floor area) and erf size (land/plot area). Those values answer different questions.
South African property analysis should preserve the measurement type as well as the numeric value.
Floor Size
Building / internal floor area
floor_size_value
floor_size_unit = m²
Erf Size
Land / plot area
erf_size_value
erf_size_unit = m²
Preserve separately — never sum into a single area field
Use fields such as:
floor_size_valuefloor_size_uniterf_size_valueerf_size_unitarea_originalFor example:
floor_size = 180 m²
erf_size = 750 m²
area = 930 m²
those measurements describe different physical concepts.
Where the source does not clearly identify measurement type: preserve the source value/label, leave the normalized basis unresolved, and route it to exception review if necessary. Do not infer floor versus erf semantics from numeric magnitude alone.
ZAR Price Fields Should Preserve Their Commercial Meaning
Potential fields include:
asking_sale_price_zarasking_rent_zarregistered_sale_price_zarvaluation_amount_zarprice_per_sqm_zarprice_originalprice_sourceDo not silently replace one with another.
- A marketplace asking price is a listing observation.
- A registered sale price is a transfer/transaction signal.
- A valuation is another data class.
Each value should retain: semantic type, currency, source, relevant date/context.
NenoData’s Data Cleaning & Standardization service supports agreed ZAR normalization, price-type mapping, and schema validation rules.
Automated Valuation Is a Separate Data Concept
Property24’s current Property Report product may include an automated valuation where available, alongside property information, transfer history, buyer/seller information, bond information, and nearby sales. (Property24 Property Report)
A valuation must remain distinct from:
Potential fields:
asking_price_zarregistered_sale_price_zarvaluation_amount_zarvaluation_sourceDo not claim: access to Property24’s proprietary AVM; reproduction of its methodology; reverse engineering of its valuation system; equivalent NenoData valuation accuracy unless separately licensed, implemented, and verified.
Province, City, and Suburb Should Be Modelled as a Hierarchy
South African property analysis often depends on geographic granularity.
country = South Africaprovincecity_or_municipalitysuburbsource_location_labelsource location identifier where availableDo not force every source location into an exact street address.
Exact address or coordinate availability must be confirmed during scoping.
Other Property24 country editions must not inherit South African geography or rights assumptions automatically.
Property24’s Access Restrictions Are Explicit
This is a central publication gate and must remain prominent.
Property24’s current Terms state that users may not use robots, spiders, automatic devices, manual processes to monitor or copy any part of the website. The Terms also restrict copying, reproduction, alteration/modification, creation of derivative works, public display of website content without Property24’s prior written permission.
This is a source/access and content-use restriction, not merely an anti-bot engineering challenge.
Property24's current Terms prohibit robot/spider and manual/automatic monitoring or copying without permission.
Need Property24-related data
Listing data or registered-property data?
Confirm licence / permission / approved source
Approved-path examples
Preserve:
requirements → permission/licence review → approved data path → schema → validation → delivery
Does Property24 Offer Official Data Access?
Yes—but the type of access matters. Property24 Property Data page describes:
- a database of more than 9 million properties
- registered-property search
- transfer information
- Property Reports
- Transfer Reports
- Sectional Scheme Reports
- Area Reports
Property24 Property Report may include, where available:
This establishes that Property24 offers official property-data/report products. It does not establish:
- unrestricted marketplace-listing crawling
- a public unrestricted developer API
- bulk rights to every Property24 listing
- unrestricted redistribution
- NenoData subscription/entitlement
Supported conclusion:
Property24 offers official property-data and report products, but a public unrestricted developer API for bulk marketplace-listing extraction was not verified.
Does Property24 Have a Public Listing API?
This research did not verify an unrestricted official public API for arbitrary bulk reading of Property24 marketplace listings.
Third-party APIs or scraper products may expose Property24-related records, but those services do not establish official Property24 API status, Property24 permission, or NenoData authorization.
Authorized Property24 Data Paths NenoData Can Evaluate
A Property24-related requirement may be evaluated through appropriately licensed or customer-controlled paths.
Property24-approved or licensed access
Where the customer has written permission, licence, subscription, or another documented contractual right, evaluate permitted record types, fields, collection/access method, storage, retention, redistribution, schema mapping, and downstream use.
Property24 Property Data / reports
Where a customer has appropriate Property Data/report rights, NenoData can evaluate structuring authorized outputs within the applicable product/licensing terms. Do not imply access before those rights are confirmed.
Customer-owned agency inventory
Estate agencies, brokers, developers, and property managers may already control listing/property records. NenoData can normalize those customer-controlled inputs without claiming broader Property24 marketplace rights.
Authorized brokerage feeds
A customer-authorized listing or property feed can be mapped into a South African property schema.
Customer-provided files
Potential inputs include CSV, Excel, JSON, CRM exports, database extracts, and listing-management exports.
Licensed transaction/property sources
Where registered sales or transfer data is the requirement, use an appropriate licensed, public, permissioned, or customer-authorized property-record source. Do not repurpose marketplace asking prices as transaction records.
Multi-source property intelligence
Where multiple approved sources are required, map them into a common model with schema normalization, source attribution, record matching, deduplication, validation, and exception handling.
NenoData’s Multi-Source Data Aggregation service supports combining approved South African property sources with source attribution, common schemas, and cross-source matching.
Personal Information and POPIA Require Separate Review
Property24’s current Data Processing Agreement explicitly operates within South Africa’s Protection of Personal Information Act 4 of 2013 (POPIA) framework. (Property24 Data Processing Agreement)
It describes processing broadly enough to include activities such as: gathering, disclosing, combining personal information.
Therefore do not make the following a headline proposition:
If personal information is genuinely required, separately review:
Do not make an independent legal determination on POPIA compliance within this page.
One-Time Dataset or Recurring Listing Observations
Where the approved source arrangement permits repeated collection and retention, a workflow may be designed as a snapshot or recurring observation process.
One-time requirements
- South African housing-market research
- rental-market analysis
- property/inventory comparison
- customer-data migration
- investment research
Recurring observations
observed_atfirst_seenlast_seenasking sale priceasking rentlisting statusavailability
This supports marketplace change analysis while keeping listing history separate from registered transfer history.
Do not promise: an existing Property24 historical archive, daily Property24 collection, hourly collection, real-time collection, a fixed Property24 SLA.
Asking-Price Change and Transfer History Are Separate Timelines
Keep two timelines separate.
Marketplace observation timeline
- first seen
- asking price
- asking-rent change
- asking-price change
- availability
- listing status
- last seen
Registered transfer timeline
- transfer date
- registered sale/consideration amount
- source authority
- registered property reference
Do not collapse these into one ambiguous property_history.
If a combined history view is needed, every event must retain: event type, source, relevant date, value semantics, and provenance.
Delivery Does Not Override Source Rights
NenoData’s Custom Data Pipelines service may support:
- CSV
- Excel
- JSON
- API-ready payloads
- database loads
- warehouse loads
- webhooks
- scheduled delivery
- recurring feeds where scoped
These technical capabilities do not create Property24 access or redistribution rights.
Final delivery must fit:
- 1.approved data source
- 2.licence/permission
- 3.permitted fields
- 4.storage terms
- 5.retention terms
- 6.redistribution rights
- 7.privacy requirements
- 8.agreed destination
“API-ready” means NenoData can structure records for downstream programmatic consumption. It does not mean NenoData has Property24 API credentials.
How an Authorized Property24 Data Workflow Would Work
- 1
Define the data requirement
Specify South African geography, for-sale/rental listings, marketplace versus registered property/transfer data, required attributes, asking-price versus sold-price requirements, floor/erf-size requirements, privacy-sensitive fields, one-time versus recurring requirements, and downstream destination.
- 2
Confirm the access and licence basis
Identify whether the workflow uses written Property24 permission, licensed Property24 product, customer-owned inventory, authorized brokerage feed, customer-provided files, separately licensed transaction/property data, or another approved South African source.
- 3
Define the entity model
Agree whether separate entities are required for property, listing, listing observation, registered transfer, and valuation/report.
- 4
Define price semantics
Separate asking sale price, asking rent, registered sold price, valuation, and price per m².
- 5
Define size semantics
Keep floor size and erf size in separate fields with their own units and source representations.
- 6
Define geography
Map available source fields into province, city/municipality, suburb, and optional address/location fields.
- 7
Ingest through the approved path
Use only a licensed, permissioned, customer-owned, customer-authorized, or otherwise approved source.
- 8
Normalize and validate
Apply agreed rules for ZAR formatting, price semantics, field mapping, property-type normalization, floor/erf handling, location hierarchy, duplicate rules, entity matching where scoped, source attribution, and exception handling.
- 9
Deliver within approved rights
Prepare permitted output for CSV, Excel, JSON, API-ready schema, database, warehouse, webhook, or scheduled delivery.
Potential Business Requirements
These are examples of buyer requirements, not proof that Property24 authorizes unrestricted source reuse.
South African housing-market research
Structure approved listing or transaction records by province, city, suburb, property type, and relevant price concept.
Asking-price benchmarking
Compare marketplace asking prices while preserving their distinction from registered sale prices.
Rental-market analytics
Normalize approved asking rents, property attributes, locations, and observation timestamps.
Inventory monitoring
Track permitted listing additions, removals, asking-price changes, and availability changes.
Comparable-sale research
Use appropriately licensed or approved registered transaction/property data. Do not substitute marketplace asking prices for completed sales.
Property enrichment
Combine approved property, listing, transfer, and customer-owned information into a source-aware property model.
Investment research
Prepare licensed or otherwise approved South African property records for internal analysis.
Internal BI
Map several authorized property sources into one validated schema.
Why NenoData Is Relevant to a Property24 Requirement
Real Estate Data Scraping
- source and market scoping
- property/listing schemas
- field mapping
- normalization
- validation
- observations
- structured delivery
Real Estate Transaction Data
- approved property-record sources
- transaction-event models
- lineage
- structured transaction fields
- asking/listing versus recorded-transaction distinctions
Data Cleaning & Standardization
- schema mapping
- transformations
- validation
- deduplication
- exception handling
Multi-Source Aggregation
- agreed external sources
- customer-authorized inputs
- common schemas
- matching
- deduplication
- validation
- source attribution
NenoData's AI Entity Resolution and Matching service can support scoped linkage where property/listing/transfer records need matching.
NenoData's Custom Data Pipelines service supports validated delivery into: files, API-ready records, databases, warehouses, webhooks, scheduled workflows.
For Property24, preserve:
requirements → licensing/authorization review → approved source → South African property/listing/transfer schema → ZAR/floor/erf normalization → validation → permitted delivery
—not unrestricted Property24 scraping.
NenoData Is Not Affiliated With Property24
NenoData does not claim affiliation with Property24, partnership with HomeFind24 (Pty) Ltd, Property24 API credentials, Property Data subscription rights, access to proprietary Property24 reports, access to Property24 AVM methodology, an existing Property24 dataset, or authorized-scraper status. Only state such a relationship if separately documented.
Frequently Asked Questions
A Property24 scraper generally refers to software or a workflow intended to convert Property24 information into structured property records. For NenoData, the term must not imply unrestricted automated collection. Property24’s current Terms expressly prohibit robot/spider or manual/automatic monitoring and copying of the website without permission.
A Property24 scraper generally refers to software or a workflow intended to convert Property24 information into structured property records. For NenoData, the term must not imply unrestricted automated collection. Property24’s current Terms expressly prohibit robot/spider or manual/automatic monitoring and copying of the website without permission.
Potential fields include listing ID, source URL, for-sale/rental type, asking price, rent, ZAR, bedrooms, bathrooms, parking, floor size, erf size, property type, suburb, city, province, listing status, and timestamps. Actual fields depend on the approved source and page type.
Potential fields include listing ID, source URL, for-sale/rental type, asking price, rent, ZAR, bedrooms, bathrooms, parking, floor size, erf size, property type, suburb, city, province, listing status, and timestamps. Actual fields depend on the approved source and page type.
Yes. Asking sale price and asking rent should use distinct fields and retain their source context.
Yes. Asking sale price and asking rent should use distinct fields and retain their source context.
An asking price is the price advertised in a marketplace listing. A registered sold price can refer to a sale registered through an appropriate property/transfer source. Property24’s current trends explicitly distinguish Property24 listing asking prices from Deeds Office-registered selling prices.
An asking price is the price advertised in a marketplace listing. A registered sold price can refer to a sale registered through an appropriate property/transfer source. Property24’s current trends explicitly distinguish Property24 listing asking prices from Deeds Office-registered selling prices.
In South African property data, erf size generally refers to the land or plot area associated with a property. It should remain separate from the property’s floor/building size.
In South African property data, erf size generally refers to the land or plot area associated with a property. It should remain separate from the property’s floor/building size.
Yes, where supplied by the approved input. Keep each measurement in a separate field with its own unit.
Yes, where supplied by the approved input. Keep each measurement in a separate field with its own unit.
Yes. Property24 currently sells Property Data products covering registered properties and transfer information, with several report types. That does not mean NenoData automatically has access to those products.
Yes. Property24 currently sells Property Data products covering registered properties and transfer information, with several report types. That does not mean NenoData automatically has access to those products.
A public unrestricted developer API for bulk marketplace-listing extraction was not verified during this research. Property24’s official data/report products should not be described as equivalent to an unrestricted listings API.
A public unrestricted developer API for bulk marketplace-listing extraction was not verified during this research. Property24’s official data/report products should not be described as equivalent to an unrestricted listings API.
Property24’s current Terms prohibit robots, spiders, automatic devices, and manual processes used to monitor or copy any part of the website, and restrict certain copying/display uses without prior written permission. A direct Property24 workflow therefore requires an appropriate permitted access basis.
Property24’s current Terms prohibit robots, spiders, automatic devices, and manual processes used to monitor or copy any part of the website, and restrict certain copying/display uses without prior written permission. A direct Property24 workflow therefore requires an appropriate permitted access basis.
Potentially, where the project uses an appropriate licensed, public, permissioned, or customer-authorized transaction/property-record source. Do not infer NenoData access to Property24 Property Data or reports unless the relevant subscription/licence is confirmed.
Potentially, where the project uses an appropriate licensed, public, permissioned, or customer-authorized transaction/property-record source. Do not infer NenoData access to Property24 Property Data or reports unless the relevant subscription/licence is confirmed.
Where approved source rights permit it, NenoData’s broader services support CSV, Excel, JSON, API-ready records, databases, warehouses, webhooks, and scheduled delivery.
Where approved source rights permit it, NenoData’s broader services support CSV, Excel, JSON, API-ready records, databases, warehouses, webhooks, and scheduled delivery.
Only where the approved source arrangement permits repeated access and retention. Potential fields include first seen, last seen, asking price, rent, availability, status, and observation timestamp. No Property24-specific fixed cadence is promised.
Only where the approved source arrangement permits repeated access and retention. Potential fields include first seen, last seen, asking price, rent, availability, status, and observation timestamp. No Property24-specific fixed cadence is promised.
Do not assume unrestricted reuse. Property24’s data-processing framework expressly addresses personal-information processing under POPIA, so personal/contact fields require separate source-rights, privacy, necessity, and intended-use review.
Do not assume unrestricted reuse. Property24’s data-processing framework expressly addresses personal-information processing under POPIA, so personal/contact fields require separate source-rights, privacy, necessity, and intended-use review.
Potential alternatives include appropriately licensed Property24 data products, customer-owned agency inventory, authorized brokerage feeds, customer-supplied files, licensed South African transaction/property datasets, and other approved property sources.
Potential alternatives include appropriately licensed Property24 data products, customer-owned agency inventory, authorized brokerage feeds, customer-supplied files, licensed South African transaction/property datasets, and other approved property sources.
No affiliation, partnership, endorsement, API relationship, Property Data subscription, or authorized-scraper status is claimed.
No affiliation, partnership, endorsement, API relationship, Property Data subscription, or authorized-scraper status is claimed.