Skip to content
    ↑↓ to choose · Enter to open

    · 13 min read

    Etuovi.com Real Estate Scraper: 44 Data Fields per Record (2026)

    By CrawlerBros Engineering Team

    Each record returned carries 44 output fields, including listing identifiers, EUR asking prices, living area sizes, Finnish room notations, agent details, and image links. It queries Etuovi's public search API directly across five property categories: residential homes, building plots, holiday cottages, farm or forest estates, and garages. At $5.00 per 1,000 results on Apify's free plan, you can extract live Finnish market data across 8 sort orders and dozens of custom filters. This Actor is for real estate analysts, PropTech developers, and property investors seeking structured data from Finland. It is not for anyone targeting rental markets, as Etuovi exclusively carries properties for sale.

    Try it: open Etuovi.com Real Estate Scraper on Apify, sign in on the free plan and run the prefilled example.

    Can you try Etuovi.com Real Estate Scraper before paying?

    Yes. Apify's free plan includes $5.00 of prepaid usage every month and asks for no credit card. At $0.005 per result, that covers up to 1,000 results of Etuovi.com Real Estate Scraper a month, before run-start charges and platform usage.

    Etuovi.com Real Estate Scraper was last updated on 2026-08-18. It is one of 1,725 Actors CrawlerBros publishes on Apify, which together have 686,270 lifetime public runs and an average rating of 4.63 out of 5 across 416 reviews.

    What does it cost to run Etuovi.com Real Estate Scraper?

    Each result costs $0.005 on Apify's free plan, which is $5.00 per 1,000 results. Starting a run is charged separately at $0.005 per GB of Actor memory. Apify also bills the platform usage each run consumes, at the rates of your Apify plan, on top of these charges.

    Apify plan Per result Per 1,000 results
    FREE $0.005 $5.00
    BRONZE $0.00433 $4.33
    SILVER $0.00367 $3.67
    GOLD $0.003 $3.00
    PLATINUM $0.003 $3.00
    DIAMOND $0.003 $3.00

    The main driver of your run cost is maxItems, which caps how many listing records the run writes to the dataset. To test your inputs cost-effectively, set maxItems to a small number like 10 before scaling up to larger extractions. This lets you inspect the output structure and verify your search filters without exhausting your usage allowance.

    How do you run Etuovi.com Real Estate Scraper from the API?

    The schema marks 1 of its 43 controls as required: propertyType. Every value in the payload below comes from the published schema's own prefills, which means you can paste it, swap the token, and get a real result.

    Call the synchronous endpoint to start a run and receive dataset items in one request:

    curl -X POST "https://api.apify.com/v2/acts/crawlerbros~etuovi-scraper/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"propertyType":"RESIDENTIAL","locations":["Helsinki"]}'

    The same run from Python, using the official client:

    from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")

run_input = {
  "propertyType": "RESIDENTIAL",
  "locations": [
    "Helsinki"
  ]
}

run = client.actor("crawlerbros~etuovi-scraper").call(run_input=run_input)

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

    And from Node.js:

    import { ApifyClient } from 'apify-client'

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' })

const input = {
  "propertyType": "RESIDENTIAL",
  "locations": [
    "Helsinki"
  ]
}

const run = await client.actor('crawlerbros~etuovi-scraper').call(input)
const { items } = await client.dataset(run.defaultDatasetId).listItems()
console.log(items)

    That endpoint blocks until the run completes. Fine while you are testing a handful of records, risky once a run takes minutes: a dropped connection loses the response even though the run itself finished. Switch to an asynchronous start with polling or a webhook before you schedule anything.

    Which Etuovi.com Real Estate Scraper inputs matter, and which can you skip?

    The propertyType control is required and selects whether you are searching residential homes, plots, holiday cottages, forest estates, or garages. To restrict results geographically, pass city or regional names into the locations array. Leave specialized filter arrays empty on your first run to verify baseline results before applying narrower constraints.

    • propertyType (string): Which category of listings to search. Default: "RESIDENTIAL".
    • locations (array): City, region, neighborhood, postal code, or street address to search (e.g. Helsinki, Uusimaa, 00100). Multiple values are combined with OR. Leave empty to search all of Finland. Default: [].
    • residentialPropertyTypes (array): Restrict to specific building types. Only applies when Property category is Apartments & houses. Leave empty for all building types. Default: [].
    • roomCounts (array): Restrict to listings with these room counts. Leave empty for any room count. Default: [].
    • priceMin (integer): Drop listings priced below this amount, in euros.
    • priceMax (integer): Drop listings priced above this amount, in euros.
    • sizeMin (integer): Drop listings with living area below this size, in square meters.
    • sizeMax (integer): Drop listings with living area above this size, in square meters.
    • yearMin (integer): Drop listings built before this year.
    • yearMax (integer): Drop listings built after this year.
    • freeTextSearch (string): Free-text keyword search across listing descriptions and features (e.g. sauna, pool, fireplace).
    • newBuildingSearchCriteria (string): Filter by new-construction status. Default: "ALL_PROPERTIES".

    The other 31 controls, with their defaults, are listed in the input schema on Etuovi.com Real Estate Scraper on Apify.

    Fixed-choice controls: propertyType accepts RESIDENTIAL (Apartments & houses), PLOT (Plots & building sites), LEISURE (Holiday homes & cottages), ESTATE (Farms & forest estates), OTHER (Garages & other properties); newBuildingSearchCriteria accepts ALL_PROPERTIES (All properties), ONLY_NEW_BUILDINGS (Only new buildings), NO_NEW_BUILDINGS (Exclude new buildings).

    What does Etuovi.com Real Estate Scraper return?

    The returned records are built for market trend tracking, property comparison apps, and monitoring private-seller listings. Note that search-time criteria like heating systems, overall condition, and sauna type are used by Etuovi to filter query results but are omitted from output fields.

    • id, friendlyId - Etuovi's internal and public listing identifiers
    • published - whether the listing is currently live on Etuovi.com
    • propertyType, propertyTypeCode - human-readable category and raw code
    • propertySubtype - building type (e.g. "Detached house", "Cottage", "Forest estate")
    • address, areaAndCity, city, fullLocation
    • latitude, longitude
    • price - asking price in EUR
    • size - living area / plot area in m² (matches the sizeSmallToLarge/sizeLargeToSmall sort key)
    • totalArea - total area in m², when Etuovi reports one (e.g. detached houses, where this also includes garages, basements, or outbuildings and can exceed size)
    • forestLandArea - forest area in m² (farm/forest estates)
    • rooms - Finnish room-structure notation (e.g. 4h, k, s = 4 rooms, kitchen, sauna)
    • roomCountLabel, constructionYear, newBuilding, developmentPhase - new-building construction status (Pre-marketing / Under construction / Move-in ready), when the listing is a new-build
    • floorLevel, floorCount - the listing's floor, and the total floors in the building
    • unitFloorCount - how many floors the unit itself spans (e.g. a duplex apartment inside a taller building spans 2 of its own floors), when Etuovi reports it
    • previousPrice - the listing's prior asking price, when Etuovi reports a price change
    • hasOpenBidding, isCompanyAnnouncement, hasVideo, hasPanorama
    • sellerName - private seller's name, when the listing is not from an agency
    • officeName, officeWebsite, officeLogoUrl - listing agency
    • agentName, agentImageUrl - listing agent, when available
    • publishedAt, updatedAt
    • nextShowings[] - upcoming open-house dates/times
    • mainImageUrl, images[], floorPlanImageUrl
    • sourceUrl - canonical etuovi.com/kohde/... listing page
    • recordType: "listing", scrapedAt

    These are the documented fields. Optional ones can be empty on a given record, so measure how often each field your deliverable depends on is populated across a real sample before automating the handoff.

    How do you build the workflow end to end?

    Open Etuovi.com Real Estate Scraper and work through these in order. Each step ends with something to check, so a bad configuration surfaces on a small run rather than a scheduled one.

    1. Select propertyType as RESIDENTIAL and enter your target municipality in locations, leaving all optional inputs empty on your initial run.
    2. Run the Actor once with maxItems set to 10 to inspect the returned records in your dataset.
    3. Verify that each record contains valid address, city, price, size, and sourceUrl values.
    4. Set priceMin, priceMax, sizeMin, or sizeMax to restrict your query bounds in EUR and square meters.
    5. Select specific residentialPropertyTypes, such as APARTMENT_HOUSE or DETACHED_HOUSE, to narrow the structural building scope.
    6. Apply specialized parameters like heatingSystems or saunaType if searching residential units, keeping in mind non-residential categories will reject these filters.
    7. Set travelTimeLat and travelTimeLon simultaneously alongside travelTimeMinutes if filtering by travel radius.
    8. Increase maxItems up to 5000 for your main extraction run after validating the sample outputs.

    How do you apply it? Three worked playbooks

    These are Etuovi.com Real Estate Scraper's own documented use cases, each worked through as an operating pattern rather than a description.

    Use case 1: Real estate market analysis

    Outcome: Track asking prices, price-per-m², and inventory by city or region

    Configure: Set propertyType to RESIDENTIAL, locations to ["Helsinki"], sortBy to priceLowToHigh, and maxItems to 1000.

    Working method: Execute an initial query across the target location to establish baseline figures. Calculate average price per square meter using price and size fields. Schedule recurring weekly runs with identical inputs to log listing movements and price fluctuations over time.

    Deliverable: A structured dataset of active property listings containing price, size, totalArea, constructionYear, and geographic coordinates.

    Stop condition: The query returns zero results for a valid municipality or price values arrive as null.

    Use case 2: PropTech products

    Outcome: Feed live Finnish listings into a search or comparison app

    Configure: Set propertyType to RESIDENTIAL, publishingTimeSearchCriteria to WITHIN_ONE_DAY, sortBy to newest, and maxItems to 500.

    Working method: Run the Actor every 24 hours to capture new sale listings from Etuovi's search endpoint. Parse id, friendlyId, address, price, size, and images into your database schema. Use sourceUrl as the canonical key to resolve existing entries.

    Deliverable: A daily JSON dataset containing new Finnish real estate listings structured for backend application ingestion.

    Stop condition: Emitted listing records systematically omit key identifier fields like id, sourceUrl, or mainImageUrl.

    Use case 3: Lead generation

    Outcome: Find newly listed or private-seller properties in a target area

    Configure: Set propertyType to RESIDENTIAL, sellerType to USER, publishingTimeSearchCriteria to WITHIN_SEVEN_DAYS, and maxItems to 200.

    Working method: Target properties offered directly by individual owners rather than real estate brokerages. Extract sellerName along with address and location attributes. Sort entries by publishedAt to prioritize recent direct-owner opportunities.

    Deliverable: A list of private-seller real estate opportunities including address details, sellerName, asking price, and listing dates.

    Stop condition: Returned items show populated officeName attributes despite setting sellerType to USER.

    What breaks, and how do you design around it?

    If your search query covers broad regions and returns thousands of items, divide the location scope across separate regional runs to keep batch sizes manageable. For tracking long-term market trends beyond the two-week publication filter limit, set up recurring scheduled runs to store snapshot datasets over time.

    When should you not use Etuovi.com Real Estate Scraper?

    Do not use this Actor if you need rental properties. Etuovi lists properties for sale only, and rental portal coverage requires alternative sourcing. If you need real estate data for other regions, look at specific regional alternatives such as Zameen Real Estate Scraper for Pakistan or Lamudi Real Estate Scraper for the Philippines. Furthermore, do not use this tool if you require private contact details like phone numbers or direct email addresses, which are not returned in the dataset.

    What should you check before trusting the output?

    • Confirm that city is populated for all records, referencing fullLocation when evaluating unparsed location strings.
    • Verify that size is a positive integer representing living area, comparing it against totalArea when totalArea is reported.
    • Check that price contains an integer EUR asking price for active listing entries.
    • Ensure sourceUrl contains a valid canonical link pointing to the etuovi.com portal.
    • Confirm that nextShowings contains an array of open-house schedule objects when hasUpcomingShowing is enabled.
    • Verify that sellerType filtering for USER results in records where officeName is omitted.

    None of this proves a record is correct. It gives a scheduled Etuovi.com Real Estate Scraper run defined points where it should stop instead of quietly passing bad data downstream.

    Frequently asked questions

    What is the cost to run this Actor?

    Pricing is $0.005 per result, which equals $5.00 per 1,000 results on Apify's free plan. Paid plans offer lower per-result rates. Platform compute usage consumed during execution is billed separately by Apify.

    Does this Actor cover rental listings on Vuokraovi?

    No. This Actor exclusively extracts sale listings from Etuovi.com. Rental properties listed on Vuokraovi.com live on a separate portal and are not retrieved by this scraper.

    What does the room notation in output records mean?

    The rooms field uses standard Finnish real estate shorthand. For instance, 4h, k, s indicates 4 rooms plus a kitchen (k) and sauna (s).

    Why are heating system and sauna type missing from dataset fields?

    Parameters like heatingSystems and saunaType act as search filters on Etuovi's endpoint. Because the API does not echo those choices back in search payloads, those attributes do not appear as output fields.

    Where to go next

    When you are ready to run it, open Etuovi.com Real Estate Scraper on Apify; the free plan covers up to 1,000 results a month.

    Start with the Etuovi.com Real Estate Scraper Actor page for the current input schema, pricing tier, and run history.

    Other Actors we maintain for related data:

    Related guides:

    Resources

    • Actor documentation, input schema, and pricing: verified against the published Actor on 2026-09-28.

    • Actor last updated by its maintainers on 2026-08-18.

    • Run outcome figures cover the 30 day public window ending 2026-09-28.

    • Etuovi.com Real Estate Scraper on Apify

    Featured actors

    Etuovi.com Real Estate Scraper

    Scrape property listings from Etuovi.com, Finland's largest real estate portal. Search apartments, houses, plots, holiday homes, and farms/forest estates by city or region, with filters for price, size, rooms, construction year, and more.

    Run on Apify ↗