Israel Sold Property Prices - Fast (GovMap, Map Coordinates) avatar

Israel Sold Property Prices - Fast (GovMap, Map Coordinates)

Pricing

from $5.00 / 1,000 results

Go to Apify Store
Israel Sold Property Prices - Fast (GovMap, Map Coordinates)

Israel Sold Property Prices - Fast (GovMap, Map Coordinates)

Fast scraper for Israel's official sold-property prices (GovMap), with map coordinates: date, price, price/sqm, address, rooms, floor, area. For year built, a unit's prior sales and appreciation trend, use the enriched version: apify.com/swerve/nadlan-gov-deals

Pricing

from $5.00 / 1,000 results

Rating

0.0

(0)

Developer

Swerve

Swerve

Maintained by Community

Actor stats

0

Bookmarked

16

Total users

7

Monthly active users

6 days ago

Last modified

Share

Israel Real-Estate Transactions - Official Sold Prices

Scrape actual recorded apartment sale prices in Israel, straight from the government's official GovMap real-estate database. These are real prices that apartments sold for, not asking prices, so they are the ground truth for valuation, comparables, and market analysis.

The data is free and public. The actor uses GovMap's open real-estate API directly, with no logins, no keys, and no signups.

What you get per transaction

Sale price (NIS), price per square meter, sale date, street address, map coordinates (WGS84 lat/lng), neighborhood, number of rooms, floor, registered area, the granular property type (for example standard apartment, garden apartment, penthouse), and the official block-parcel-subparcel (gush / helka / tat-helka).

{
"dealDate": "2026-05-17",
"dealAmount": 4700000,
"pricePerSqm": 46078,
"address": "לוי אשכול 86",
"cityName": "תל אביב-יפו",
"neighborhoodName": "רמת אביב החדשה",
"rooms": 4.5,
"floor": "7",
"area": 102,
"propertyType": "דירה בבית קומות",
"isFirstHand": null,
"gush": "6886",
"helka": "12",
"tatHelka": "23",
"assetId": "123456789",
"lat": 32.113,
"lng": 34.795,
"scrapedAt": "2026-06-17T09:30:00.000Z"
}

Inputs

InputWhat it does
citiesOne or more cities, in Hebrew (for example תל אביב -יפו, ירושלים, חיפה). Each is geocoded and the deals around its center are collected.
customCitiesAny city or town not in the dropdown, typed in Hebrew. Optional.
neighborhoodsOptional. Narrow to specific neighborhoods within the chosen city, in Hebrew. Only deals whose neighborhood matches are returned.
dealDateRangeall, or the last 3 / 6 / 12 months / 60 (5 years).
roomsFilter by rooms, comma-separated, for example 3,4.
minPrice / maxPriceSale-price range in NIS.
maxItemsOptional cap on how many transactions are returned and billed.

Output fields

FieldTypeMeaning
dealDatestringSale date (YYYY-MM-DD).
dealAmountintegerActual sale price in NIS.
pricePerSqmintegerSale price divided by area, rounded (NIS per sqm).
addressstringStreet and house number (Hebrew). Null when the registry row carries no address; the parcel identifiers below still identify the property.
cityNamestringCity name (Hebrew), normalized to one canonical spelling.
neighborhoodNamestringNeighborhood name (Hebrew), as tagged by GovMap. Best-effort: well filled in large cities, often null elsewhere.
roomsnumberNumber of rooms (for example 4.5).
floorstringFloor as a numeric string (for example "7", ground = "0"). GovMap publishes Hebrew ordinal words; the actor converts the known vocabulary and passes rare unrecognized values through in Hebrew.
areanumberRegistered area in square meters.
propertyTypestringGranular property type (Hebrew), for example דירה בבית קומות, דירת גן, דירת גג. Null on a share of rows where GovMap omits it.
isFirstHandbooleanCurrently always null. A mid-2026 GovMap API change removed the new-vs-resale split (the parameter now errors), so the flag cannot be populated. Kept for schema stability.
gush / helka / tatHelkastringOfficial block / parcel / sub-parcel.
assetIdstringGovMap deal id.
lat / lngnumberBuilding centroid in WGS84 — plot deals straight onto any map.
scrapedAtstringISO timestamp of the scrape.

Example

The 12-month resale transactions of one Tel Aviv neighborhood:

{ "cities": ["תל אביב -יפו"], "neighborhoods": ["רמת אביב החדשה"], "dealDateRange": "12", "dealType": "resale" }

For a whole city, drop neighborhoods. For everything available, set dealDateRange to all.

How it works

For each requested city (and each neighborhood, when given), the actor:

  1. Resolves the city to its real municipal boundary (bundled outlines for 200+ cities, GovMap's public search as fallback).
  2. Tiles that whole boundary into a grid of sub-queries and asks GovMap for the deal clusters in every tile, so outlying areas are covered, not just the center.
  3. Pages through every recorded sale in each cluster.

It then keeps only residential apartment sales, maps each to the output row above, applies your date / rooms / price / neighborhood filters, removes duplicate deals, and writes results continuously, so even a large pull never loses progress. Requests are throttled to stay within GovMap's normal use, and when Israeli residential proxy credentials are available they are used; otherwise the public API is called directly.

Notes and limits

  • This is historical sold data. Transactions appear only after official registration, which typically lags the signing date by four to six weeks — a "last 3 months" pull is expected to be thin for the most recent weeks.
  • Coverage per city is the full municipal boundary, tiled into a grid so outlying neighborhoods are included. Large cities produce hundreds of sub-queries (Tel Aviv ≈ 800+), which takes time: run big cities with no timeout or one of 15+ minutes — a short user-set timeout is the most common cause of a timed-out run.
  • Year built and total building floors are not provided by this source; our enriched sibling actor covers them: apify.com/swerve/nadlan-gov-deals.
  • The registry itself occasionally records the same physical transaction twice with a sub-parcel off by one and the amount/date marginally different. The actor deduplicates exact repeats, but these near-twin registry rows are kept, since they can also be two genuinely distinct units.
  • There is no run timeout and no result cap, so a full pull runs to completion. Use maxItems, a date range, or a neighborhood to keep runs fast and cheap.

Use cases

  • Property valuation and automated comparables (real sold prices, not listings).
  • Real-estate market and price-trend analysis by city or neighborhood.
  • Appraisal, lending, and investment due diligence.
  • Feeding a valuation model or a real-estate product with ground-truth prices.