One Australia scope. The full property system behind it.

The endpoint resolves the property. The Australia graph explains what it means.

PropData Australia is not a national parcel table with state labels painted on top. G-NAF provides the national address spine; cadastral identity is state or territory native; geometry and legal identifiers follow those source systems; and every promoted layer keeps its own coverage and provenance. The application sees one Australia scope while the data contract remains honest about where the underlying truth came from.

Think in property domains, not endpoint count.

A compact route surface can still unlock a deep country product. The Australia contract is the operating layer around the property: national address identity, jurisdiction routing, native cadastre, source geometry, coordinate containment, coverage and provenance. Exact response fields remain governed by the promoted route, jurisdiction and account entitlement.

Three common ways into the Australia graph.

curl --get \
  "https://propdata-api-worker.sales-fd3.workers.dev/v1/property" \
  --data-urlencode "country=AU" \
  --data-urlencode "address=YOUR_AUSTRALIAN_ADDRESS" \
  -H "x-api-key: $PROPDATA_API_KEY"

const url = new URL(
  "https://propdata-api-worker.sales-fd3.workers.dev/v1/property"
);
url.searchParams.set("country", "AU");
url.searchParams.set("address", inputAddress);

const response = await fetch(url, {
  headers: { "x-api-key": process.env.PROPDATA_API_KEY }
});

if (!response.ok) {
  throw new Error(`PropData ${response.status}`);
}

const result = await response.json();

REST keys stay on the server. MCP uses OAuth.

Direct REST requests use the x-api-key header. Store production keys in trusted server, worker or edge secrets. Do not put a PropData key in URLs, browser bundles, screenshots, repositories, analytics or logs.

PROPDATA_API_KEY=pd_live_...
PROPDATA_API_BASE=https://propdata-api-worker.sales-fd3.workers.dev

The routes are the doorway into the Australia contract.

Australia uses the shared PropData production API surface. The existence of a global route does not imply the corresponding enrichment is enabled in every Australian jurisdiction. Use the promoted route contract and returned coverage semantics as the authority.

National address identity first. Jurisdiction-native cadastral identity second.

G-NAF provides the national address spine. Once the property can be routed into a certified jurisdiction layer, PropData preserves the source-native cadastral model rather than forcing it into a U.S.-style parcel schema.

Geometry is a promoted source layer, not a universal assumption.

Australian property geometry follows jurisdiction source systems. Where promoted, the geometry route and coordinate resolver let applications connect point-based workflows to certified parcel, lot or block context. Where geometry is not promoted, PropData does not manufacture a boundary from another layer.

Build around explicit identity, coverage and provenance.

Australian integrations should not assume every jurisdiction emits the same source fields. Treat the returned envelope as authoritative and model optional jurisdiction-specific enrichment separately from successful base identity.

{
  "country": "AU",
  "jurisdiction": "VIC",
  "match_level": "source_native",
  "coverage_status": "live",
  "property": {
    "...": "promoted jurisdiction fields"
  },
  "provenance": {
    "source_name": "jurisdiction source",
    "source_dataset_id": "source dataset",
    "source_revision": "revision"
  }
}

Four live cadastral jurisdictions on top of complete national address identity.

Normalization should not erase meaning.

The point of a country abstraction is not to destroy the underlying source model. PropData provides stable access while still preserving the identifiers, geographic/legal structures and revision context needed by serious downstream systems.

Match, coverage and provenance are separate signals.

Coverage states

Authoritative sources in. Governed property infrastructure out.

PropData operates the ingestion, normalization, jurisdiction routing, canonical identity, geometry processing, coverage semantics, source revision handling, quality gates and production delivery above the Australian source systems. The country contract is designed to expose what has actually been certified — not what we hope to add later.

The Australia graph is not limited to one-request-at-a-time REST.

The same governed country model can be packaged around the workflow the customer actually needs. Authentication and entitlement remain channel-specific.