Australian Property Data API - AVM, Sales, Listings

Look up any Australian residential property: match an address to a property, read its attributes with the dates they were sourced, its planning and tenure, every recorded sale with the source that reported it, its current and past listings, an automated sale or rental valuation, and the auction results and market metrics for the suburb around it.

What this actor does

• Address to property ID, with a confidence score. Match resolves free text to exactly one property and tells you how sure it is. When it will not narrow, suggest mode returns ranked candidates instead of a guess. Everything else keys off that property ID.
• Attributes with their source dates. Bedrooms, bathrooms, car spaces, land, floor and living area, property type, roof and wall type, year built, land use and the feature list - each with the date the provider last sourced it. A bedroom count sourced in 2014 is a different fact from one sourced last month, and this actor keeps the difference.
• Recorded sales with the source that reported them. Valuer General registered transfers and agent-advised sales are two different claims about the same market, with different lags and different reliability. The source is a first class column on every transaction row, never averaged across.
• Price suppression handled honestly. Some Australian jurisdictions restrict publication of a sale price, and the provider flags those. The flag rides beside the value on every row, so a suppressed price never enters a median as a zero.
• Listings, current and historic. Sale and rental listings with their status, advertised price, first seen date, auction date and time, description, images, energy efficiency rating and a direct link to the statement of information where one is attached.
• Automated valuations with their uncertainty. Sale and rental valuations across all four products - enquiry, origination, plus and pro - returning the estimate, its lower and upper range, the forecast standard deviation and the confidence level. Plus and pro accept your own bedroom, bathroom and car space figures, which is how you value a property as renovated rather than as recorded.
• Search by area or by radius. Properties, listings and transactions by suburb and postcode, or outward from a centre property or coordinate, filtered by bedrooms, bathrooms, car spaces, land area, living area, price and date. Transaction searches can narrow to the same street or even the same building, which is what unit comparables actually need.
• Market metrics and auction results. Median and mean sale and rental prices, transaction volumes, days on market, hold periods, rental yields and buyer and renter demand, by suburb, state or capital city area, at your choice of frequency and aggregation window.
• Census demographics. One row per measure for a suburb, state or greater capital city area.
• Pay per result. You are charged for rows carrying a real record. Addresses the provider cannot match and searches that return nothing are free.

Bring your own key

This actor calls the provider with your own api key and api secret. Paste both into the input, or set the secret as the DATA_API_KEY secret. Nothing runs on anyone else's credentials, and a run without them ends cleanly with an explanation rather than failing.

The two values are base64 encoded together and sent in the Authorization header. The provider states it does not accept them as form parameters, so there is exactly one correct way to send them and several that look correct. This actor gets that right.

If the API answers with an HTML "Access Denied" page

This one is worth knowing before it happens. The provider's production host sits behind an edge network that can block a caller by IP address, and when it does, every path answers with an HTML page rather than JSON - including paths that do not exist. Verified against the live host while building this actor.

That failure looks nothing like an API error and is easy to mistake for a bad credential. This actor detects it, reports it as a network level block rather than an authentication problem, and pulls out the edge reference number so you can hand it to the provider's support team, which is what their own documentation asks for. Running from a different network is the other fix.

Suppressed sale prices are not zeros

In several Australian states the sale price of a property may not be published. The provider marks those transactions with a suppression flag rather than omitting them, because the sale itself is still a real event with a real date.

A pipeline that reads the missing price as 0 drags every median it touches downwards. One that ignores the flag entirely may publish something it is not allowed to. So the flag sits beside the value on every transaction row, and on the recent sale on every property row, and the value is left exactly as the provider sent it.

Two sources for the same sale

Transactions come from either the state Valuer General - a registered transfer, authoritative but lagged by the registration process - or from the selling agency, which is faster but self-reported. They disagree, and the disagreement is informative rather than noise.

You can filter to one source, and every row records which one it came from either way, so a downstream average never silently mixes a registered price with an advertised one.

Example output

{
  "recordType": "transaction",
  "requested": "RICHMOND 3121 VIC",
  "found": true,
  "propertyId": "3987592",
  "fullAddress": "21 STANLEY ST RICHMOND VIC 3121",
  "latitude": -37.82364584,
  "longitude": 144.99504193,
  "sourceCategory": "vg",
  "transactionDate": "2024-11-28",
  "contractDate": "2024-11-06",
  "transferDate": "2025-01-15",
  "transferType": "full",
  "saleValue": 1350000,
  "saleValueSuppressed": false,
  "listingId": "146535076",
  "daysOnMarket": 24,
  "bedrooms": 3,
  "bathrooms": 1,
  "carSpaces": 4,
  "landArea": 420,
  "propertyType": "house",
  "landUse": "residential"
}

FAQ

What Australian property data does this actor return?

For a property: the standardised address and coordinates, bedrooms, bathrooms, car spaces, land, floor and living area, property type, roof and wall type, year built, land use, features, parcel plan and lot numbers, current market status, active listings, and the most recent sale. Optionally also planning and zoning, tenure history, the full listing history and the full sale history. For an area: listings, recorded sales, auction results, historic market metrics and census demographics.

How do I find a property ID from an address?

Run address match mode with the address as free text. It returns exactly one property with a match score, or reports that the text did not narrow to a single property. For partial or ambiguous addresses, address suggest mode returns ranked candidates you can pick from before spending a property lookup.

What is the difference between the enquiry, origination, plus and pro valuations?

Enquiry is the general purpose automated valuation. Origination is the lending grade product and is mandatory for new customers on some request paths. Plus combines a sale and a rental valuation in one request. Pro adds environmental hazard information on top of that. Plus and pro are sale side products, so a rental valuation requested under them falls back to enquiry rather than being refused.

Why does a valuation come with a forecast standard deviation?

Because an automated valuation without a measure of its own uncertainty is a number pretending to be a fact. The forecast standard deviation is the model's statement of how wide the estimate really is, and lenders commonly set policy thresholds on it. It is returned alongside the estimate, its lower and upper range, and the confidence level.

Can I get sold prices for Australian properties?

Yes, from two sources that are kept apart: Valuer General registered transfers and agency-advised sales. Every transaction row records the source, the sale value, the transaction, contract and transfer dates, and an explicit flag for whether the price is suppressed under state rules. Suppressed prices are flagged rather than zeroed, so your medians stay honest.

How do I get comparable sales for a unit?

Run a transaction search in point and radius mode with the subject property as the centre, and set proximity to same building. That returns sales inside the same complex rather than within a radius that would sweep in freestanding houses on the same street. Same street and same suburb are the wider settings.

What market metrics are available?

Sale side: median and mean sale price, sale transaction volume, mean hold period and median days on market. Rental side: median and mean rental price, median rental yield, rental transaction volume and median days on market. Demand: potential buyers and potential renters. Median days on market exists in both families and means something different in each, so every row records which family it was read from.

Does it cover all Australian states?

The address, property, listing and transaction data covers all eight states and territories. The provider wants state codes lowercase and refuses other casing, which returns an empty run rather than an error, so this actor presents them as a fixed list and sends the form the API wants. Coverage depth for recorded sales varies by state because it follows each state's own land registry publication rules.

Keyword map

Australian property data API, Australia real estate API, property data API Australia, AVM API Australia, automated valuation model Australia, property valuation API, sold prices Australia API, property sales history API, Valuer General data API, real estate listings API Australia, rental listings API, auction results API, suburb market data API, median house price API, rental yield data, days on market data, property attributes API, UPRN equivalent Australia, property ID lookup, address matching API Australia, census demographics API, statement of information, comparable sales API, unit comparables, forecast standard deviation AVM