REAL ESTATE · SOUTH AFRICA
property24.com Property (South Africa)
Property listings from Property24 (property24.com, South Africa) for sale or to rent across verified search areas.
About this data
Property listings from Property24 (property24.com, South Africa) for sale or to rent across verified search areas. One record: URL, price ZAR, suburb, city, province, bedrooms, bathrooms, property type, images, agent. On-demand scrape — fresh listings every run.
From the actor’s Apify Store listing. The per-call endpoint may return a bounded subset; its own description is below.
Buy per call over x402
One endpoint at api.ssh.autos. Each call is one JSON POST, paid in USDC with no account or API key, and answered in the same HTTP response.
POST /v1/za/property24/listings
Live Property24 listings for one South African area (Cape Town City Centre by default): price in ZAR, suburb, city, province, property type, bedrooms where shown, images and listing URL.
First results page only, up to 20 listings; the residential proxy is included in the price.
Input
Send a JSON body to POST https://api.ssh.autos/v1/za/property24/listings.
| Field | Type | Required | Notes |
|---|---|---|---|
area | string | optional | 1–160 characters; default "cape-town-city-centre" |
operation | string | optional | one of for-sale, to-rent; default "for-sale" |
maxResults | integer | optional | 1–20; default 10 |
Returned fields
The answer is JSON: records, a list of up to 20, and summary, the run status and counts. Each record has these 16 fields; a field the source does not publish comes back null.
16 fields per record
| Field | Type | Notes |
|---|---|---|
listing_key | string | Stable record key 'property24.com:{listingId}', or the canonical URL when the listing id is unknown. |
url | string | Canonical listing URL on the site (/{operation}/{suburb}/{city}/{province}/{areaId}/{listingId}), tracking query parameters removed. |
price | integer | Advertised price as an integer amount in the site currency ('R 2 495 000' → 2495000, 'R 2,495,000' → 2495000). Null when the price is hidden (POA). |
currency | string | Site currency: ZAR on property24.com (ZA), KES on property24.co.ke (KE stretch). |
suburb | string | Suburb from the listing URL path. |
city | string | City from the listing URL path. |
province | string | Province from the listing URL path. |
bedrooms | integer | Bedroom count ('Bed 2' / '2 Bedrooms'); null when not shown. |
bathrooms | integer | Bathroom count ('Bath 1' / '2 Bathrooms'); null when not shown. |
property_type | string | Property type keyword from the listing (Apartment, Townhouse, House, Vacant Land, ...); null when not shown. |
images | array of strings | Listing image URLs. |
agent | string | Agency/agent name from the card or embedded state; null when not shown. |
operation | string | Requested operation: 'for-sale' or 'to-rent'. |
area_id | string | Numeric property24 area id that was searched (the opaque location identifier). |
source | string | Source slug 'property24.com' (or 'property24.co.ke' on the Kenya stretch). |
scraped_at | string | UTC ISO-8601 collection timestamp. |
Example call
npx agentcash@latest fetch https://api.ssh.autos/v1/za/property24/listings -m POST -b '{"maxResults": 3}'
The example values come from the API spec or the actor’s own sample input. Running it is a paid call.
What is and isn’t charged
You pay the call price for
- An answer, including a definitive “not found” or an empty result.
- Confirmed no matches returns records: [] (charged: it is an answer).
Free
- Invalid input (422), busy (503), source failure (502), timeout (504) and calls whose client hung up are never charged.
- Invalid input and source failures are not charged.
Prefer a subscription? Run it on Apify
This data source is a public actor on the Apify Store: property24.com Property Scraper (South Africa). Run it with your Apify account and plan for larger, scheduled or exported runs; it may offer more input options than the per-call endpoint.
How x402 payment works
- Your client sends the request. The API answers
402 Payment Requiredwith the price and where to pay. - The client pays from its own wallet: USDC on Base or Solana over x402, or over MPP on Tempo. No account, sign-up or API key.
- The client retries with the payment attached and gets the JSON answer in the same call. You are only charged for answers.
The AgentCash CLI in the example does all three steps for you and pays from your AgentCash wallet. Any x402 or MPP client works the same way.
Machine-readable: openapi.json · llms.txt