Australian Property Zoning and Development API

Ask an Australian address what you are allowed to build on it, and what somebody already built next door.

What it collects

• Zoning for any parcel: the primary zone code and label, and every zone on a split-zoned site rather than only the first.
• Overlays as the provider publishes them, each with its category, key and value, plus the flood, bushfire, heritage, environment, infrastructure and industry flags.
• Permitted and prohibited uses under the parcel's planning instrument, as filterable lists rather than one long string.
• Parcel facts: lot identifier, property type, area in square metres, strata lot count, local government area, locality, linked GNAF addresses and the parcel centre point.
• Development potential: estimated dwelling yield with the provider's complexity, confidence and slope grades, heritage, flood and fire flags, and the nearby built precedents behind the estimate with their address, zone, site area, dwelling count and frontage.
• Granny flat eligibility: whether a secondary dwelling can be built on the property.
• Planning maps: a rendered image of the parcel with zoning, heritage, bushfire, flood or contours drawn over it, with legend labels and colours.

FAQ

What can I build on an Australian property?

Run planning essentials on the address. It returns the zone or zones covering the parcel, the overlays that restrict it, and the permitted and prohibited use lists under the relevant planning instrument, along with the lot identifier, parcel area and local government area. Run development potential on the same address for an estimated dwelling yield and the comparable approvals it rests on.

Which states does this Australian planning API cover?

The provider's planning coverage spans Australian states and territories, and parcels come back tagged with their own region, for example nsw or vic, along with the local government area. Address matching accepts NSW, VIC, QLD, SA, WA, TAS, NT and ACT.

Can I look up a property by coordinate instead of address?

Yes. Every mode accepts a latitude and longitude pair as well as an address or a property ID. Give the pair latitude first; the actor sends them as the separate named fields this API expects, so a swapped pair cannot quietly return a real parcel somewhere else. Each row records which of the three input kinds produced it.

Why does my address need matching first?

This API takes no free text on its data endpoints. An address has to become a property ID before the zoning, potential, eligibility or image endpoints will answer, so the actor matches every address for you and carries the match through. Use the match addresses mode on its own when you only want the IDs.

What is a development potential estimate?

A modelled dwelling yield for a site, published with a complexity grade, a confidence grade, a slope grade, and the nearby built precedents that support it. The grades are the provider's own words rather than numbers and are kept as written, because turning "Low" confidence into a score would invent precision the model does not claim.

Does a blank development potential mean the property is unknown?

No, and the difference matters. The provider returns an explicit empty result when it holds the property and has no development potential recorded for it, and a different answer when it has no record of the property at all. This actor reports those as two different notes, and charges for neither.

How long is the property image link valid?

The provider issues a temporary link that its documentation says lasts seven days. Every image row carries the moment the link was issued and the moment it lapses, so a stored row can be told apart from one that has quietly expired.

Do I need my own API key?

Yes. This actor is bring-your-own-key: it calls the provider with your own account credentials and never ships a key of its own. Paste the key on its own rather than a whole header line.

What does it cost?

Pay per result. Development potential and planning records are the richest rows and cost the most; an eligibility check or an address match costs a fraction of that. Platform usage is included. Addresses, property IDs and points the provider has no record for are never charged.

Example output

{
  "recordType": "planning",
  "requested": "3 Kooyongkoot Road, Hawthorn VIC 3122",
  "subjectType": "address",
  "found": true,
  "propertyId": "4BBB64B6C2C8C7D30411E9D56831204F",
  "lotIdentifier": "\\RP10699",
  "localities": ["HAWTHORN"],
  "region": "vic",
  "propertyType": "Lot",
  "propertyAreaSqm": 2339.34,
  "zoneCode": "NRZ3",
  "zoneLabel": "NRZ3 - Neighbourhood Residential Zone - Schedule 3",
  "zoneCount": 1,
  "localGovernmentArea": "Boroondara City",
  "overlayCount": 0,
  "hasFloodOverlay": false,
  "hasBushfireOverlay": false,
  "hasHeritageOverlay": false,
  "latitude": -37.83036173778157,
  "longitude": 145.0392984627507
}

Keyword map

Australian property API, zoning data API, planning overlay API, development potential API, site feasibility data, granny flat eligibility, secondary dwelling rules, NSW VIC QLD zoning lookup, local government area planning data, bushfire flood heritage overlay data, lot and plan identifier lookup, GNAF address matching, property development site finder, planning map image API.

Notes

Bring your own key. Read only: every route this actor calls reads data, so a scheduled run cannot change anything in your provider account. Rate limiting and retries are handled for you, and a missing or refused key ends the run cleanly with an explanation rather than failing it. This API reports a miss inside a successful response rather than as an error status, and the actor detects that in the body so a property it cannot find never arrives as a row of empty columns.