Primary cadastral parcel baseline complete, with authoritative address resolution layered above it.
One country. Full depth.
Resolve property identity, inspect the production graph, test country-aware requests and see the full national posture—including restricted title ownership and memorial infrastructure without confusing entitlement-gated layers with default public API access.
New Zealand property infrastructure, not another lookup tool.
Addresses resolve into parcels. Parcels connect to titles, cadastral geometry, buildings and legal/statutory context. Behind that customer-safe surface, the national title-estate, ownership and memorial layers are also loaded as restricted infrastructure. Every layer keeps its own source, coverage and entitlement state underneath one country-aware PropData contract.
# Exact LINZ primary parcel curl "https://propdata-api-worker.sales-fd3.workers.dev/v1/property?country=NZ&parcel=3818618&enrich=full" \ -H "x-api-key: $PROPDATA_API_KEY" # Authoritative address GET /v1/property?country=NZ&address=221%2F66%20Mabey%20Road%2C%20Avalon%2C%20Lower%20Hutt # Coordinates → property GET /v1/property/by-location?country=NZ&lat=-41.1886269490596&lng=174.943031500008
Test the NZ contract.
Country scope is locked to NZ. The lab exposes public customer-safe routes only—never internal RPCs, source tables or service-role operations.
Select a route, complete its parameters, then run the request. Secrets are never placed in the URL or printed into this panel.
Know what is actually loaded.
National source completeness, derived relationship coverage and public route exposure are different facts. This workspace keeps those distinctions visible.
2,988,279 title↔parcel associations preserve many-to-many legal relationships.
National LINZ building-outline source complete; 3,820,845 derived building↔parcel relationship rows.
Current and historic LINZ parcel actions loaded into a bounded, source-aware legal intelligence layer.
National restricted legal-title layers are loaded and governed separately from the customer-safe self-serve contract.
WGS84 points can resolve into containing property context with explicit coverage semantics.
One global platform, with country-specific depth and response contracts layered underneath.
/v1/property at new_zealand.legal_actions.The country product can be deep without pretending every official dataset has the same rights model. Public product claims stop at what is actually licensed and production-ready.
One PropData account, country-focused workflow.
The NZ Workspace does not create a second billing identity. It uses the same PropData account and API credential while keeping requests and examples scoped to New Zealand.
Usage and limits are read from the production account contract rather than hardcoded into the workspace.
Connect an API key, then load /v1/auth/usage.
Everything needed to ship NZ.
Use the country docs for exact semantics, this workspace for live probes, and the global workspace when engineering needs cross-country control.
New Zealand API Docs
Country architecture, public endpoint surface, Full Enrich concepts, graph layers, statutory intelligence and rights boundaries.
Open docs →NZ Request Lab
Run country-locked requests against the production edge API without exposing a key in the URL.
Open lab →Global PropData Workspace
Cross-market endpoint catalog, broader U.S. intelligence, account controls, MCP and the global developer surface.
Open global workspace →AI-native delivery
PropData MCP is OAuth-protected and distinct from the static-key REST flow shown in this workspace.
View global MCP setup →Production edge
Direct REST runs through the shared PropData edge while the country adapter preserves New Zealand-native identifiers and provenance.
Authentication guide →Bulk / enterprise
Custom response contracts, bulk delivery, commercial platform use and country-specific data licensing.
Talk to enterprise sales →