Resolve the input against authoritative New Zealand identity instead of forcing a U.S. parcel convention.
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.
Preserve the many-to-many title graph and spatial building relationships around the verified parcel.
Attach available geometry, derived physical context and legal/statutory layers with independent coverage states.
Use the same governed PropData account and provenance rules across delivery modes.
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.Three ways into one property.
/v1/property?country=NZ&parcel=3818618Resolve an exact LINZ primary parcel identifier.
/v1/property?country=NZ&address=221%2F66%20Mabey%20Road%2C%20Avalon%2C%20Lower%20HuttResolve an authoritative New Zealand address into property identity.
/v1/property/by-location?country=NZ&lat=-41.1886269490596&lng=174.943031500008Resolve a WGS84 coordinate into the containing property context.
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.
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.
PROPDATA_API_KEY=pd_live_... PROPDATA_API_BASE=https://propdata-api-worker.sales-fd3.workers.dev
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.
/v1/propertyPrimary 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.
/v1/property/by-locationWGS84 coordinate → parcel/property context with explicit spatial match semantics.
/v1/property/by-location/coverage-checkProbe coordinate coverage before relying on a property-by-location workflow.
/v1/countriesDiscover the country-aware framework and supported market capabilities.
/v1/auth/usageAuthoritative account usage and current limits for quota-aware applications.
/v1/healthPublic production service health for operational checks.
/v1/statsPublic platform-level proof and service statistics. Do not substitute global stats for property-level coverage.
/v1/changelogProduction API and data-platform changes for integration teams.
GET /v1/property
Resolve a New Zealand property by authoritative address or LINZ primary parcel identifier. Use one clear identity method per request.
/v1/property| Parameter | Required | Purpose |
|---|---|---|
| country | yes | Use NZ. |
| address | one input | New Zealand address to resolve. Do not combine with a conflicting parcel ID. |
| parcel | one input | LINZ primary parcel ID such as 3818618. |
| enrich | optional | Use full for deeper country enrichment where available to the account. |
{
"country_code": "NZ",
"match_level": "parcel_id",
"coverage_status": "live_enriched",
"property": {
"...": "route-supported NZ fields"
}
}Full Enrich connects the graph.
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.
GET /v1/property?country=NZ&parcel=3818618&enrich=full
Parcel + cadastral context
Native parcel ID, appellation, land district, area, topology and available geometry.
Title graph
Property titles plus explicit title↔parcel associations, including multi-title and unit-title contexts.
Building relationships
National building outlines spatially linked to parcels with relationship method, overlap and provenance.
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.
Coordinates → property.
/v1/property/by-location| Parameter | Required | Purpose |
|---|---|---|
| country | yes | NZ |
| lat | yes | WGS84 latitude. |
| lng | yes | WGS84 longitude. |
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
GET /v1/property/by-location/coverage-check?country=NZ&lat=-41.1886269490596&lng=174.943031500008
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.
Authoritative addresses
LINZ address identity, locality structure, lifecycle and coordinates.
2,424,415baseline completePrimary parcels
Parcel identity, cadastral attributes and available geometry.
3,040,571baseline completeProperty titles
Title status, type, dates, estate description and source context.
2,450,998baseline completeTitle ↔ parcel
Explicit many-to-many associations between legal title identity and cadastral parcels.
2,988,279baseline completeBuilding outlines
LINZ footprints with capture and imagery provenance where published.
3,268,141baseline completeBuilding ↔ parcel
Derived spatial relationships using overlap geometry and New Zealand metric CRS handling.
3,820,845relationship graph completeParcel statutory actions
Current and historic LINZ/Landonline parcel actions normalized into legal/statutory intelligence.
342,695baseline complete · automated refreshTitle estates
National title → estate graph maintained behind entitlement controls.
2.81Mrestricted baseline completeOwnership records
Estate-linked ownership source records. Counts are not unique people or organisations.
5.73Mrestricted baseline completeTitle memorials
National memorial/legal-interest graph with source identity preserved.
32.86M+restricted baseline completeStructured memorial details
Structured legal-interest detail linked back to memorial identity.
1,784,819restricted baseline · incremental path liveTitles 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.
{
"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"
}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.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.
"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
}
}Parcel actions now have their own production layer.
342,695 normalized statutory actions
LINZ dataset 51565 is loaded nationally and refreshed through a bounded, resumable changeset workflow. Records remain attached to source parcel identity rather than being turned into vague property flags.
Current vs historic, by action type
The country graph can summarize total/current/historic actions and create/extinguished/referenced counts, returning a bounded set of source-aware items without exposing raw ingest payloads.
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."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"
}
}Country product, global control plane.
/v1/countriesCountry-aware capabilities and market context across the PropData network.
/v1/auth/usageAuthoritative account usage and limits. Build quota-aware backoff from this route and returned rate-limit headers.
/v1/healthPublic service health. Suitable for operational checks, not for property-specific coverage conclusions.
/v1/statsPublic platform statistics and proof points.
/v1/changelogProduction platform and data changes for integration teams.
Match, coverage and provenance are separate signals.
match_levelHow the input resolved: address, parcel, coordinate or another explicit identity method.
coverage_statusWhether the requested source/layer is available for the resolved context.
parcel_resolutionWhether an address or coordinate successfully attached to parcel identity.
source / provenanceWhere the fact originated and how a derived relationship was produced.
count / returned / truncatedDistinguish total matches from bounded response items.
null / unavailableMissing source truth remains missing. PropData does not convert absence into a favorable claim.
Handle failures by category.
| Status | Meaning | Recommended behavior |
|---|---|---|
| 400 | Validation / invalid request | Correct parameters before retrying. |
| 401 | Authentication failed | Check the server-side credential and account status. |
| 403 | Entitlement / access restriction | Do not retry blindly; verify plan or restricted-layer entitlement. |
| 404 | Route or supported resource not found | Distinguish route mismatch from a property no_match response. |
| 429 | Rate limit | Use backoff and authoritative usage/rate-limit signals. |
| 5xx | Transient service/upstream failure | Retry conservatively; preserve a successful base property response if only an optional enrichment failed. |
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.
PropData is an independent product of PropTechUSA.ai and is not operated by or affiliated with LINZ or the New Zealand government.