PropData EstoniaCOUNTRY WORKSPACE · EESTONIA
COUNTRY LOCK · EE
API DocsGlobal Workspace
Estonia operating console

One country. Real depth.

Resolve cadastral identity, inspect the official-source graph, test Estonia-native requests and hand a verified response contract directly to engineering.

Read docs
PRODUCTION · MAA- JA RUUMIAMET + EHR

Estonia property infrastructure beyond parcel lookup.

Addresses and cadastral codes resolve into land intelligence, assessed land value, available parcel geometry, ADS relationships and — where populated — EHR building specifications, energy certificates and permit/document history.

ADDRESS → CADASTRE → LAND → GEOMETRY → BUILDINGS → ENERGY → DOCUMENTS
Country scopeEE only
Source backboneMaa- ja Ruumiamet · EHR
API surfaceGlobal /v1
Land layerNATIONAL · LIVE
Normalized addresses1.39M+Official ADS identity
Land-enriched units778,325National cadastral land baseline
Building ↔ parcel971K+Relationship graph
Property objects2.44M+ADS object graph
Object ↔ address10.27M+Relationship records
Estonia property graphSOURCE-AWARE LAYERS
AD
Official addressesADS identity, lifecycle, hierarchy and coordinates
1.39M+
CA
Cadastral landArea, intended use, registration, assessed value
778K+
GE
Parcel geometryNational polygon reconciliation expanding
LIVE+
OB
ADS property objectsObject identity linked to address graph
2.44M+
BP
Building ↔ parcel relationshipsExplicit graph relationships
971K+
EH
EHR building intelligenceSpecs, energy and documents where populated
COVERAGE
Developer quickstartCOUNTRY-AWARE REST
# Native Estonian cadastral code
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"

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

# Coordinates → property
GET /v1/property/by-location?country=EE&lat=58.12511901&lng=25.34680635
REFERENCEOpen country docs

Land, buildings, energy, documents and source rules.

Live request lab

Test the EE contract.

Country scope is locked to EE. The lab exposes customer-safe public routes only — never internal RPCs, source tables or service-role operations.

Endpoint reference
EndpointsEE PUBLIC SURFACE
GET
Select an endpoint
No API key connected. Public health/stats/changelog routes can still run.
LIVE RESPONSE
READY0 MS0 KB
Select a route, complete its parameters, then run the request.

Secrets are never placed in the URL or printed into this panel.
Country: EE · API origin: propdata-api-worker.sales-fd3.workers.dev
Country graph coverage

Separate loaded truth from rollout state.

Estonia is already a deep country product. National cadastral land is live; geometry and EHR layers remain coverage-aware while national reconciliation/backfill continues.

NATIONAL · LIVE778,325 cadastral units

Area, intended use, registration date and assessed land value. Ownership type and registered immovable number where published.

ADS GRAPH1.39M+ addresses

Official address identity with lifecycle, hierarchy, coordinates and object relationships.

RELATIONSHIPS10.27M+

Object↔address graph records plus 971K+ building↔parcel relationships.

EXPANDING NATIONAL BASELINEParcel geometry

Whole-country geometry reconciliation is actively increasing materialized polygon coverage.

COVERAGE-AWAREEHR buildings

Building specifications and footprints return where the EHR building layer is populated.

COVERAGE-AWAREEnergy + documents

Energy certificates and normalized permit/document history attach where source coverage is populated.

Deep-response proof78404:406:4330
Documented live example: 600 m² residential land, private ownership type, €123,108 assessed land value, registered immovable number, parcel polygon, linked EHR building, energy history and a 14-event document timeline.
Contract ruleFAIL-CLOSED FACTS
A 200 is not universal coverage. Optional Estonia layers populate independently. Missing source facts remain missing; the workspace never converts an unavailable layer into a positive property claim.
Account & usage

One PropData account, Estonia-focused workflow.

The EE Workspace uses the same PropData account and REST credential while keeping examples and live requests scoped to Estonia.

Connected API credentialNOT CONNECTED
No credential connected.
Production handling: customer applications should keep PropData credentials in a trusted server, worker or edge function. This browser workspace is for explicit account-holder testing.
Authoritative usage/v1/auth/usage

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.
Developer handoff

Everything needed to ship Estonia.

Use country docs for exact semantics, this workspace for live probes, and the global workspace when engineering needs multi-country control.

EE

Estonia API Docs

Country architecture, public routes, deep enrichment, rollout states and source rules.

Open docs →
LAB

EE Request Lab

Run country-locked production requests without placing an API key in the URL.

Open lab →
GL

Global PropData Workspace

Cross-market endpoints, U.S. intelligence, account controls, MCP and the broader developer surface.

Open global workspace →
MCP

AI-native delivery

PropData MCP uses OAuth and is distinct from the static-key REST flow shown here.

View MCP setup →
API

Production edge

Direct REST uses the shared PropData edge while preserving Estonia-native identifiers and provenance.

Authentication guide →