Skip to content

Property24 Listings as Structured Data

Property24 is the main marketplace for South African property listings, and its public pages carry the fields most analysis teams need: asking price or rent, beds, baths, square metres, suburb, agent name, days on market and the image gallery.

OUTPUT FORMATSHTMLJSONMarkdown

This page explains how a hosted scraping API turns a Property24 URL into structured output, which request options control rendering and extraction, and how to choose between CSS rules and AI-driven extraction.

What the API does with a Property24 URL

You send a Property24 URL plus your extraction logic. The service renders the page in a real browser, rotates the outbound IP, and returns the response your code can act on. JavaScript rendering, proxies and bot-detection handling sit behind that single call, so your pipeline does not need to manage a headless browser fleet or a proxy pool.

Three scraping jobs dominate Property24 work: comparing suburb pricing across Cape Town, Johannesburg, Durban, Pretoria and other South African markets; extracting rental price data for trend analysis; and collecting property agent details for lead generation or competitor benchmarking. Each of these is a different extraction shape over the same public listing pages.

Listing fields you can target

Every public Property24 listing exposes the same core set of fields. The table below maps each field to what it is useful for and notes the request option that most affects whether it is present in the response.

Request options and what they change

The advanced parameters are the difference between a raw HTML response and a clean structured payload. Use this map to decide which options your Property24 job actually needs.

  • render_js — executes the page in a browser so JavaScript-rendered listing content is present before extraction.
  • stealth_proxy — routes the request through a stealth proxy tier intended for pages that present CAPTCHAs or aggressive bot checks.
  • country_code — sets the geo-targeting country for the request.
  • ai_extract_rules — describes the fields you want in natural language and lets the service return structured data without hand-written selectors.
  • extract_rules — targets exact elements with CSS or XPath selectors when you already know the page structure.

A practical rule: start with extract_rules when the listing markup is stable and you want deterministic output; switch to ai_extract_rules when the page structure shifts or when you are prototyping the field set.

Worked example: one listing, one call

Suppose you want the asking price, bedroom count, bathroom count, floor area, suburb, agent name and days on market for a single Property24 listing. You send the listing URL with render_js enabled and an extraction rule set that names those seven fields. The response returns them as structured JSON rather than as HTML you would have to parse.

If the same job covers a whole suburb, you iterate the listing URLs for that suburb and apply the same rule set to each. The image gallery is returned alongside the numeric fields, so a single pass can populate both a pricing table and a media index.

Render failure versus extraction failure

Two different problems can produce an empty or partial result, and they need different fixes.

A render failure means the page did not load as expected: the browser was blocked, the JavaScript did not finish, or the proxy was rejected. Symptoms are an error status, a CAPTCHA page, or a response that contains no listing content at all. The fix is on the request side — enable render_js, move to stealth_proxy, or adjust country_code.

An extraction failure means the page rendered correctly but your rules did not match. Symptoms are a successful response with the listing visible in the HTML but missing from the structured output. The fix is on the rule side — correct the CSS or XPath selector, or replace the rule with an ai_extract_rules description. Checking which of the two happened before changing anything saves a debugging cycle.

Plans and credit costs

Per-request credit costs depend on the options you enable: 5 credits for JavaScript rendering, 25 for premium_proxy with JS rendering, and 75 for stealth_proxy. Plan prices, credit allowances, credit validity, tax treatment and cancellation terms are commercial details that should be confirmed against the current pricing page before you commit to a tier. The full plan matrix, including credit allowances, concurrency limits and which support features are included at each tier, is delivered in the pricing table module referenced below. Match a plan to your expected monthly request volume rather than to the headline price: estimate how many Property24 pages you will fetch per month, multiply by the credit cost of the options you need, and compare that total against each tier's allowance.

Languages and setup

SDKs are published for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works for any stack. Code samples exist in every major language, and the dashboard includes a request builder for testing without writing code. Setup is designed to take under five minutes: create an account, copy the API key, and send a GET request with the target URL.

Legality and scope

Public-facing pages can usually be scraped, but you should review the target site's terms of service before deploying and avoid post-login content. The API is built for public Property24 data; it does not require a Property24 account. How request data and returned content are retained is a policy question worth settling with the provider before you send personal information; treat any data-handling commitment as something to verify in writing rather than assume.

Property24 listing fields and their request controls
FieldWhat it tells youRequest option that affects it
Asking price or rentCurrent listing price or monthly rentrender_js if price is rendered client-side
BedsBedroom countrender_js
BathsBathroom countrender_js
Square metresFloor or stand arearender_js
SuburbLocation for comparison groupingcountry_code for geo-targeted requests
Agent nameListing agent for lead generationextract_rules or ai_extract_rules
Days on marketHow long the listing has been activerender_js
Image galleryFull set of listing photosextract_rules or ai_extract_rules

Field availability depends on what the public page renders; the request options above are the controls that most affect presence, not a guarantee that every field appears on every listing.

Frequently asked questions

Do I need a Property24 account to scrape it?

No. You sign up for an API key, send the Property24 URL, and the service handles rendering and proxies. Whether a free trial credit allowance applies, and how large it is, should be checked on the current signup page before you plan a test run.

Is scraping Property24 legal?

Public-facing pages can usually be scraped, but you should review the target site's terms of service before deploying and avoid post-login content. Legality depends on your jurisdiction and how you use the data.

What data can I extract from Property24?

Anything that renders on the public page. Use extract_rules with CSS selectors for deterministic output, or ai_extract_rules for AI-driven extraction when you want structured JSON without hand-written selectors.

How do I start scraping Property24?

Sign up, copy your API key, and send a GET request with the target URL. The service renders the page, rotates proxies, and returns the data. Check the current signup page for any trial credit allowance before you size a first test batch.

Which programming languages can I use?

Any. SDKs are published for Python, Node.js, Go, PHP, Ruby and Java, and plain cURL works too. Pick whatever your stack already uses.

How much does it cost to scrape Property24?

Per-request credit costs depend on options: 5 credits for JavaScript rendering, 25 for premium_proxy with JS rendering, and 75 for stealth_proxy. Plan prices, credit allowances, credit validity and tax treatment are commercial details to confirm against the current pricing page. A useful estimate is monthly page count multiplied by the credit cost of your chosen options, compared against each tier's allowance.