From cadastral identity
to property intelligence.

Coverage is a field, not a promise.

Different Estonia layers populate independently. PropData exposes the source facts that are actually available for the resolved property and preserves explicit match/coverage semantics instead of synthesizing missing data.

Authentication

Direct PropData requests use x-api-key. Keep direct production keys server-side. Marketplace requests use RapidAPI-provided credentials and should be routed through the Estonia-scoped marketplace integration.

curl "https://propdata-api-worker.sales-fd3.workers.dev/v1/property?country=EE&parcel=78404:406:4330" \
  -H "x-api-key: $PROPDATA_API_KEY"

Address → property

Resolve an official ADS address and attach the property graph beneath it where available.

GET /v1/property?country=EE&address=Viljandi%20maakond%2C%20Mulgi%20vald%2C%20Abja-Paluoja%20linn%2C%20Pärnu%20mnt%2051a

Cadastral code → deep property

Use the native Estonian katastritunnus directly. Canonical PropData parcel IDs are also accepted.

{
  "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}
    }]
  }
}

Coordinates → property

Resolve WGS84 coordinates to the containing Estonia parcel without requiring an address-string match.

GET /v1/property/by-location?country=EE&lat=58.12511901&lng=25.34680635

Deep Estonia response contract

The enrichment model is additive. Existing property identity fields remain stable while Estonia-specific source layers attach below estonia.

Land intelligence

The national cadastral export enriches the CU graph with typed land/property attributes.

EHR building intelligence

For populated EHR-linked buildings, PropData can return current physical/technical state alongside stable EHR identity.

Energy certificates

Energy data attaches to the linked EHR building when published.

"energy_certificate_history": {
  "count": 1,
  "items": [{
    "document_number": "1711567/00915",
    "eta_kek_type": "KEK",
    "eta_kek_value": 238,
    "energy_class": "ENERGIAKL_E",
    "valid_from": "2017-06-01",
    "valid_to": "2027-05-31"
  }]
}

Permits & document history

The EHR document layer is normalized into a building timeline instead of forcing clients to parse Estonian document types themselves.

Parcel + building geometry

Parcel and building geometry are distinct layers. Parcel geometry comes from national cadastral sources; building footprints come from EHR when available. Both are normalized to GeoJSON-compatible WGS84 output.

Platform endpoints

Errors & retries

Official sources & provenance

Core Estonia source systems include Maa- ja Ruumiamet for ADS/cadastral data and the Estonia Register of Construction Works (EHR) for building, energy and document intelligence. PropData is an independent normalization/delivery platform and is not operated by the Estonian government.