/v1/propertyAddress or cadastral resolver. Add enrich=full for deeper Estonia-specific enrichment where covered.
PropData Estonia resolves official ADS addresses, native cadastral codes and coordinates into a governed property graph spanning national land intelligence, assessed land value, explicit object relationships, available parcel geometry and — where populated — EHR building, energy and document history.
Estonia is already a deep country product, but every layer has its own rollout truth. National cadastral land is live. Geometry and EHR-derived layers remain coverage-aware while national reconciliation and backfill continue.
/v1/property?country=EE&parcel=78404:406:4330
/v1/property?country=EE&address=...
/v1/property/by-location?country=EE&lat=...&lng=...
enrich=full attaches Estonia-specific source layers where covered.
curl "https://propdata-api-worker.sales-fd3.workers.dev/v1/property?country=EE&parcel=78404:406:4330&enrich=full" \ -H "x-api-key: $PROPDATA_API_KEY"
Direct REST uses the x-api-key header. Production keys belong in server-side secrets or environment variables — never URLs, browser bundles, screenshots, analytics or repositories. PropData MCP uses OAuth and is a different authorization flow.
These are the public routes used by the Estonia experience. Internal database RPCs, ingest tables and service-role operations are intentionally excluded.
/v1/propertyAddress or cadastral resolver. Add enrich=full for deeper Estonia-specific enrichment where covered.
/v1/property/by-locationWGS84 coordinate → containing parcel/property context.
/v1/countriesCountry-aware platform capability context.
/v1/auth/usageAuthoritative account usage and limits.
/v1/healthPublic production service health.
/v1/changelogProduction API and data-platform changes.
Resolve an official ADS address and attach the property graph beneath it where available. Address responses can expose ADR_ID, ADS code-address, lifecycle/source timestamps, hierarchy, source coordinates, related property objects and parcel attachment.
GET /v1/property?country=EE&address=Viljandi%20maakond%2C%20Mulgi%20vald%2C%20Abja-Paluoja%20linn%2C%20P%C3%A4rnu%20mnt%2051a
Use the native Estonian katastritunnus directly. Canonical PropData parcel IDs are also accepted where supported by the resolver.
{
"country_code": "EE",
"match_level": "cadastral_code",
"coverage_status": "live_enriched",
"parcel": {
"global_parcel_id": "EE:MAARUUM:CADASTRE:ads_ky.10761487",
"geometry": {"type":"Polygon"}
},
"estonia": {
"land": {
"cadastral_code": "78404:406:4330",
"area_sqm": 600,
"intended_uses": [{"use":"ELAMUMAA","percent":100}],
"ownership_type": "Eraomand",
"assessed_land_value_eur": 123108,
"registered_immovable_number": "3298301"
},
"ehr_buildings": [{
"ehr_code": "101000361",
"first_usage_year": 1956,
"dimensions": {"floors_count":2,"closed_net_area_sqm":113},
"energy_certificate_history": {"count":1},
"documents": {"count":14}
}]
}
}Resolve WGS84 coordinates to containing Estonia parcel context without requiring an address-string match.
The national cadastral enrichment baseline contains 778,325 units. The Estonia response can attach area, intended uses and percentages, land-area composition, ownership type where published, registered immovable number, registration/change dates and official assessed land value in EUR.
The Estonia graph carries 2.44M+ property objects, 10.27M+ object↔address relationships and 971K+ building↔parcel relationships. PropData preserves those explicit links instead of collapsing them into a single guessed property record.
ADR_ID, code-address, hierarchy, coordinates and lifecycle context.
Source-native object identity remains visible in the normalized graph.
Address and object relationships attach to cadastral identity where resolved.
Estonia parcel geometry is being reconciled nationally. When materialized, PropData returns source-aware GeoJSON-ready geometry. A missing polygon must remain unavailable rather than being inferred from a centroid, address point or nearby parcel.
Where populated, EHR building enrichment can attach building identity/status, first-use year, floor count, closed net area, footprint, volume, primary use, construction materials and technical systems. National EHR backfill is coverage-aware and continues independently of the already-live cadastral land baseline.
Where published and linked through EHR, PropData can attach certificate number, ETA/KEK type and value, energy class, status, issue date and expiry date. Absence of a certificate in the response is not proof that a building has never had one unless the returned coverage supports that conclusion.
The EHR document layer normalizes available building permits, permit applications, occupancy/use records, construction-start notices, design conditions, registry events and restriction notices into a source-aware timeline.
/v1/countriesCountry-aware capability context across the PropData network.
/v1/auth/usageAuthoritative account usage and limits.
/v1/healthPublic service health for operational checks.
/v1/stats · /v1/changelogPlatform proof points and production changes.
| Status | Meaning | Recommended behavior |
|---|---|---|
| 400 | Validation / invalid request | Correct parameters before retrying. |
| 401 | Authentication failed | Check server-side credential and account state. |
| 403 | Entitlement restriction | Verify plan or layer entitlement; do not retry blindly. |
| 429 | Rate limit | Use authoritative usage headers and backoff. |
| 5xx | Transient service/upstream failure | Retry conservatively; preserve a valid base property result if only optional enrichment failed. |
Core Estonia property identity and cadastral layers are built from official Maa- ja Ruumiamet source systems, including ADS/cadastral infrastructure. Building, energy and document intelligence is sourced from Estonia's EHR where available. PropData operates ingestion, normalization, canonical identity, relationship graphs, coverage semantics and production delivery above those systems.
The EE Workspace is the operating surface for live request testing, country coverage, response inspection, account usage and developer handoff.