kv APIkv.ee ↗
Search and retrieve property listings from kv.ee, Estonia's largest real estate portal. Filter by county, price, area, and deal type via 2 endpoints.
What is the kv API?
The kv.ee API provides access to Estonia's largest real estate portal through 2 endpoints covering listing search and listing detail retrieval. The search_listings endpoint returns paginated results with address, price, area, and price per square meter across apartments, houses, and other property types. The get_listing endpoint returns full property attributes, coordinates, images, and free-text descriptions for any individual listing.
curl -X GET 'https://api.parse.bot/scraper/a3bfb1cb-10a8-4df2-8699-8627281e6a54/search_listings?page=1&county=1&parish=1061&orderby=cdwl&area_max=100&area_min=40&deal_type=1&price_max=200000&price_min=50000&rooms_max=3&rooms_min=2' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace kv-ee-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: kv_ee_api SDK — bounded, re-runnable; every call capped."""
from parse_apis.kv_ee_api import KvEe, DealType, SortOrder, ListingNotFound
client = KvEe()
# Search for apartments for sale in Tallinn, sorted by price
for listing in client.listings.search(
deal_type=DealType.SALE,
county="1",
parish="1061",
orderby=SortOrder.CHEAPEST,
limit=3,
):
print(listing.address, listing.price, listing.rooms)
# Drill-down: take one listing and get full details
item = client.listings.search(deal_type=DealType.RENT, parish="1061", limit=1).first()
if item:
full = item.details()
print(full.title, full.price, full.description[:100])
# Direct get by ID with typed error handling
try:
detail = client.listings.get(listing_id="3599884")
print(detail.title, detail.latitude, detail.longitude)
except ListingNotFound as e:
print(f"listing gone: {e.listing_id}")
print("exercised: listings.search / listings.get / ListingSummary.details")
Search real estate listings with filters for deal type, location, rooms, price, and area. Returns paginated results (50 per page) with total count. Results are auto-iterated; no page/cursor param to pass.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination (50 results per page). |
| county | string | County ID for location filter (e.g. '1' for Harjumaa). Obtainable from site dropdowns. |
| parish | string | Parish/city ID for location filter (e.g. '1061' for Tallinn). Obtainable from site dropdowns. |
| orderby | string | Sort order for results. |
| area_max | string | Maximum area in square meters. |
| area_min | string | Minimum area in square meters. |
| deal_type | string | Transaction type filter. |
| price_max | string | Maximum price in euros. |
| price_min | string | Minimum price in euros. |
| rooms_max | string | Maximum number of rooms. |
| rooms_min | string | Minimum number of rooms. |
{
"type": "object",
"fields": {
"page": "current page number",
"total": "total number of listings matching the search criteria",
"listings": "array of listing summaries with id, url, address, rooms, area, price, price_per_m2, description, and label"
},
"sample": {
"data": {
"page": 1,
"total": 3638,
"listings": [
{
"id": "3884842",
"url": "https://www.kv.ee/harjumaa-tallinn-lasnamae-paekaare-tn-44-1-tuba-32-3884842.html",
"area": "32.7 m2",
"label": "",
"price": "1 EUR",
"rooms": "1",
"address": "Paekaare tn 44, Lasnamae, Tallinn",
"description": "Vajab renoveerimist, elektripliit, parkimine tasuta",
"price_per_m2": "0.03 EUR/m2"
}
]
},
"status": "success"
}
}About the kv API
Search Listings
The search_listings endpoint accepts filters including deal_type (sale or rent), county and parish IDs for location scoping, price_max, area_min, area_max, and an orderby sort parameter. Results are paginated at 50 listings per page; pass the page parameter to iterate. Each result in the listings array includes the listing id, url, address, rooms, area, price, price_per_m2, a short description, and a label. The total field gives the full count of matching listings, which you can use to determine how many pages to fetch.
Listing Detail
The get_listing endpoint accepts a numeric listing_id (available from search_listings results) and returns a richer data shape. The details object contains Estonian-language property attributes such as Tube (rooms), Uldpind (total area), Korrus/Korruseid (floor/floors), Ehitusaasta (year built), Seisukord (condition), Omandivorm (ownership type), and Energiamargis (energy class). The response also includes latitude and longitude coordinates, an images array of photo URLs, a full description text, and price_per_m2.
Coverage and ID Lookups
Location IDs for county and parish parameters (e.g., '1' for Harjumaa, '1061' for Tallinn) correspond to the dropdown values used on kv.ee. These are stable numeric strings. The listing_id used by get_listing is the same numeric identifier exposed in each search result's id field and in the listing url, so the two endpoints compose naturally into a search-then-fetch workflow.
The kv API is a managed, monitored endpoint for kv.ee — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when kv.ee changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official kv.ee API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Monitor asking prices and price-per-m2 trends across Estonian counties for market analysis.
- Build a property alert system that checks new listings matching specific room count, area, and price filters.
- Aggregate listing coordinates to map real estate inventory density by parish or county.
- Compare energy class (Energiamargis) distribution across listings in Tallinn versus other regions.
- Track year-built (Ehitusaasta) and condition (Seisukord) data to identify renovation-era housing stock.
- Compile listing image URLs for visual datasets or automated property photo catalogues.
- Feed structured listing data (price, area, rooms, floor) into a valuation or comparables model.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does kv.ee have an official developer API?+
What location identifiers does search_listings accept?+
county and parish as numeric string IDs. For example, '1' targets Harjumaa county and '1061' targets Tallinn. These IDs correspond to the location dropdown values on kv.ee. You can supply both together to narrow results to a specific city within a county, or use either alone.Does the API return seller or agent contact information?+
search_listings nor get_listing currently expose contact details such as agent name, phone number, or email. The API covers property attributes, pricing, coordinates, images, and description text. You can fork this API on Parse and revise it to add a contact-details endpoint if that data is needed.How does pagination work in search_listings?+
page parameter to request subsequent pages. The total field in the response gives the total matching listing count, so you can calculate the number of pages as ceil(total / 50). There is no cursor parameter — page number is the only pagination control.