PRODUCTION CONTRACT · NEW ZEALAND / AOTEAROA

Build on the national property graph.

Authoritative address resolution, parcels, titles, buildings and statutory intelligence are delivered through the customer-safe PropData API. Behind that surface, national title-estate, ownership and memorial/legal-interest baselines are complete as separately entitlement-gated infrastructure.

3,040,571Primary parcels
2,424,415Addresses
2,450,998Property titles
2,988,279Title ↔ parcel
3,268,141Building outlines
3,820,845Building ↔ parcel
2.81MRestricted title estates
5.73MRestricted ownership records
32.86M+Restricted title memorials
1,784,819Structured memorial details
342,695Statutory actions
Country API architecture

One global edge. One deep New Zealand contract.

PropData keeps one global API surface while preserving country-native data models underneath it. New Zealand requests carry country=NZ; the resolver then routes into New Zealand-specific property identity, title, cadastral and physical-improvement intelligence. The country site and workspace are the focused developer experience for that market—not a separate disconnected backend.

01 · RESOLVEAddress / parcel / coordinates

Resolve the input against authoritative New Zealand identity instead of forcing a U.S. parcel convention.

02 · CONNECTParcel ↔ title ↔ building

Preserve the many-to-many title graph and spatial building relationships around the verified parcel.

03 · ENRICHCountry-native context

Attach available geometry, derived physical context and legal/statutory layers with independent coverage states.

04 · DELIVERREST · MCP · bulk · custom

Use the same governed PropData account and provenance rules across delivery modes.

Blueprint: this is the country pattern moving forward—global PropData API → country adapter → country website → country docs → country workspace. The global product stays unified while each mature market gets a genuinely deep local developer experience.
First request

Three ways into one property.

GET/v1/property?country=NZ&parcel=3818618

Resolve an exact LINZ primary parcel identifier.

GET/v1/property?country=NZ&address=221%2F66%20Mabey%20Road%2C%20Avalon%2C%20Lower%20Hutt

Resolve an authoritative New Zealand address into property identity.

GET/v1/property/by-location?country=NZ&lat=-41.1886269490596&lng=174.943031500008

Resolve a WGS84 coordinate into the containing property context.

CURL · VERIFIED MABEY ROAD CANARY
curl "https://propdata-api-worker.sales-fd3.workers.dev/v1/property?country=NZ&parcel=3818618&enrich=full" \
  -H "x-api-key: $PROPDATA_API_KEY"

The production canary resolves parcel 3818618, appellation Lot 1 DP 90132, Wellington land district. Examples show verified graph concepts; the returned payload remains the authority for the exact fields available to your account and route.

Authentication

Credentials stay server-side.

Direct REST uses the x-api-key header. Production keys belong in server-side secrets or environment variables—not URLs, browser bundles, screenshots, analytics, or repositories. The NZ Workspace is an account/developer tool and only sends a key after the user explicitly connects one for the session.

ENVIRONMENT
PROPDATA_API_KEY=pd_live_...
PROPDATA_API_BASE=https://propdata-api-worker.sales-fd3.workers.dev
MCP is different. PropData MCP uses OAuth in compatible clients. Do not paste a static REST API key into an MCP authorization flow.
Customer-safe REST surface

The routes New Zealand developers actually need.

These are the public PropData routes used by the country experience. Internal database RPCs, ingest functions, checkpoints, source tables and service-role operations are intentionally not public API endpoints.

GET/v1/property

Primary property resolver for NZ address or parcel input. The NZ property contract returns country-native Full Enrich including titles, building relationships and new_zealand.legal_actions from the certified LINZ 51565 layer.

AUTHNZIDENTITY
GET/v1/property/by-location

WGS84 coordinate → parcel/property context with explicit spatial match semantics.

AUTHNZSPATIAL
GET/v1/property/by-location/coverage-check

Probe coordinate coverage before relying on a property-by-location workflow.

AUTHCOVERAGE
GET/v1/countries

Discover the country-aware framework and supported market capabilities.

GLOBALCAPABILITIES
GET/v1/auth/usage

Authoritative account usage and current limits for quota-aware applications.

AUTHACCOUNT
GET/v1/health

Public production service health for operational checks.

PUBLICOPS
GET/v1/stats

Public platform-level proof and service statistics. Do not substitute global stats for property-level coverage.

PUBLICOPS
GET/v1/changelog

Production API and data-platform changes for integration teams.

PUBLICRELEASES
Property identity

GET /v1/property

PRODUCTIONCOUNTRY-AWARE

Resolve a New Zealand property by authoritative address or LINZ primary parcel identifier. Use one clear identity method per request.

GET/v1/property
ParameterRequiredPurpose
countryyesUse NZ.
addressone inputNew Zealand address to resolve. Do not combine with a conflicting parcel ID.
parcelone inputLINZ primary parcel ID such as 3818618.
enrichoptionalUse full for deeper country enrichment where available to the account.
ILLUSTRATIVE RESPONSE ENVELOPE
{
  "country_code": "NZ",
  "match_level": "parcel_id",
  "coverage_status": "live_enriched",
  "property": {
    "...": "route-supported NZ fields"
  }
}
Fail-open enrichment, fail-closed facts. A valid property result should survive an optional layer failure. Missing or unavailable downstream facts remain unavailable; PropData does not invent a substitute.
Deep country response

Full Enrich connects the graph.

PRODUCTIONLAYER-SPECIFIC

New Zealand Full Enrich is backed by the same canonical parcel and title identity used by the base resolver, then attaches country-native building relationships, derived physical context and the certified LINZ 51565 legal/statutory summary. The legal layer is returned at new_zealand.legal_actions and remains independently fail-open so a downstream legal-layer issue cannot break valid property identity.

REQUEST
GET /v1/property?country=NZ&parcel=3818618&enrich=full
IDENTITY

Parcel + cadastral context

Native parcel ID, appellation, land district, area, topology and available geometry.

LEGAL IDENTITY

Title graph

Property titles plus explicit title↔parcel associations, including multi-title and unit-title contexts.

PHYSICAL

Building relationships

National building outlines spatially linked to parcels with relationship method, overlap and provenance.

LEGAL / STATUTORY

Live legal actions

Certified LINZ 51565 current + historic parcel actions returned directly at new_zealand.legal_actions with counts, bounded items, source revision and coverage state.

Spatial identity

Coordinates → property.

GET/v1/property/by-location
ParameterRequiredPurpose
countryyesNZ
latyesWGS84 latitude.
lngyesWGS84 longitude.
MABEY ROAD COORDINATE CANARY
GET /v1/property/by-location?country=NZ&lat=-41.1886269490596&lng=174.943031500008

Coordinate resolution attaches spatial property context without pretending every point has an exact address record. Use the returned match and coverage signals independently.

Coverage probe

PRE-FLIGHT
GET /v1/property/by-location/coverage-check?country=NZ&lat=-41.1886269490596&lng=174.943031500008
Production country graph

Eleven infrastructure layers, one governed property identity.

Seven customer-safe national layers drive the normal product contract. Four deeper title/legal layers are also loaded nationally as restricted infrastructure and remain separately entitlement-controlled rather than being implied as default REST output.

01

Authoritative addresses

LINZ address identity, locality structure, lifecycle and coordinates.

2,424,415baseline complete
02

Primary parcels

Parcel identity, cadastral attributes and available geometry.

3,040,571baseline complete
03

Property titles

Title status, type, dates, estate description and source context.

2,450,998baseline complete
04

Title ↔ parcel

Explicit many-to-many associations between legal title identity and cadastral parcels.

2,988,279baseline complete
05

Building outlines

LINZ footprints with capture and imagery provenance where published.

3,268,141baseline complete
06

Building ↔ parcel

Derived spatial relationships using overlap geometry and New Zealand metric CRS handling.

3,820,845relationship graph complete
07

Parcel statutory actions

Current and historic LINZ/Landonline parcel actions normalized into legal/statutory intelligence.

342,695baseline complete · automated refresh
08 · RESTRICTED

Title estates

National title → estate graph maintained behind entitlement controls.

2.81Mrestricted baseline complete
09 · RESTRICTED

Ownership records

Estate-linked ownership source records. Counts are not unique people or organisations.

5.73Mrestricted baseline complete
10 · RESTRICTED

Title memorials

National memorial/legal-interest graph with source identity preserved.

32.86M+restricted baseline complete
11 · RESTRICTED

Structured memorial details

Structured legal-interest detail linked back to memorial identity.

1,784,819restricted baseline · incremental path live
Legal property identity

Titles stay relational.

PropData does not flatten New Zealand title identity into a single fake owner field. The graph preserves title records and title↔parcel associations separately so multi-title, unit-title and shared-spatial contexts remain structurally correct.

VERIFIED TITLE-SHAPE EXAMPLE
{
  "title_no": "1006231",
  "status": "LIVE",
  "title_type": "Unit Title",
  "land_district": "Wellington",
  "issue_date": "2021-11-01T16:20:02Z",
  "guarantee_status": "Guarantee",
  "estate_description": "Stratum in Freehold, 1/1, Unit 44 Deposited Plan 90777",
  "number_owners": 1,
  "spatial_extents_shared": true,
  "source": "Toitū Te Whenua LINZ"
}
Named ownership remains a separate entitlement problem. PropData maintains the national title-estate and ownership baselines internally, but title metadata and number_owners still do not authorize inference of named owner identity. LINZ Personal Data Licence-gated ownership and memorial datasets remain separately controlled and are not default self-serve output.
Physical property graph

Buildings are linked, not merely nearby.

The national building-outline source baseline contains 3,268,141 records. PropData then builds a separate relationship graph with 3,820,845 building↔parcel links. The relationship model preserves method, confidence basis, overlap area, overlap ratio, metric CRS and geometry-repair provenance where applicable.

FULL-ENRICH CONCEPT
"new_zealand": {
  "building_relationships": {
    "coverage_status": "complete",
    "count": 2,
    "returned": 2,
    "truncated": false,
    "items": [ ... ]
  },
  "derived": {
    "building_count": 2,
    "primary_building_count": 1,
    "building_overlap_area_ratio": 0.1842
  }
}
A complete national building source does not mean every parcel contains a building. A zero relationship count is different from unavailable linkage coverage; read the returned coverage state.
Legal / statutory intelligence

Parcel actions now have their own production layer.

LIVE IN THE PROPERTY API: statutory actions are now part of the New Zealand property response at new_zealand.legal_actions. Production canary parcel 3784245 returns 12 certified actions: 2 current, 10 historic, 1 create and 11 referenced. No separate legal-actions endpoint is required.
VERIFIED PUBLIC RESPONSE · PARCEL 3784245
"new_zealand": {
  "legal_actions": {
    "coverage_status": "complete",
    "count": 12,
    "current_count": 2,
    "historic_count": 10,
    "action_counts": {
      "create": 1,
      "extinguished": 0,
      "referenced": 11
    },
    "returned": 12,
    "truncated": false,
    "source_dataset_id": "51565"
  }
}
Global platform routes

Country product, global control plane.

GET/v1/countries

Country-aware capabilities and market context across the PropData network.

GET/v1/auth/usage

Authoritative account usage and limits. Build quota-aware backoff from this route and returned rate-limit headers.

GET/v1/health

Public service health. Suitable for operational checks, not for property-specific coverage conclusions.

GET/v1/stats

Public platform statistics and proof points.

GET/v1/changelog

Production platform and data changes for integration teams.

Do not guess

Match, coverage and provenance are separate signals.

match_level

How the input resolved: address, parcel, coordinate or another explicit identity method.

coverage_status

Whether the requested source/layer is available for the resolved context.

parcel_resolution

Whether an address or coordinate successfully attached to parcel identity.

source / provenance

Where the fact originated and how a derived relationship was produced.

count / returned / truncated

Distinguish total matches from bounded response items.

null / unavailable

Missing source truth remains missing. PropData does not convert absence into a favorable claim.

Core contract rule: base identity success and enrichment availability are not the same thing. Treat optional country layers independently so a missing enrichment never corrupts a valid property match.
Operational behavior

Handle failures by category.

StatusMeaningRecommended behavior
400Validation / invalid requestCorrect parameters before retrying.
401Authentication failedCheck the server-side credential and account status.
403Entitlement / access restrictionDo not retry blindly; verify plan or restricted-layer entitlement.
404Route or supported resource not foundDistinguish route mismatch from a property no_match response.
429Rate limitUse backoff and authoritative usage/rate-limit signals.
5xxTransient service/upstream failureRetry conservatively; preserve a successful base property response if only an optional enrichment failed.
Source and rights transparency

Authoritative sources in. Governed delivery out.

Core New Zealand property layers are sourced from Toitū Te Whenua Land Information New Zealand (LINZ). PropData operates the ingestion, normalization, canonical identity, spatial processing, relationship graph, refresh automation, coverage semantics and production delivery above those source systems.

LINZ SOURCE-AWAREPROPDATA NORMALIZEDPERSONAL DATA ENTITLEMENTS SEPARATE
Restricted title graph / personal data: national title-estate, ownership, memorial and structured memorial-detail baselines are complete. Those restricted LINZ datasets remain separately entitlement-gated and are not represented as generally available unless the applicable LINZ licence and downstream controls are in place.

PropData is an independent product of PropTechUSA.ai and is not operated by or affiliated with LINZ or the New Zealand government.