Poland Developer Apartment Prices (dane.gov.pl) avatar

Poland Developer Apartment Prices (dane.gov.pl)

Pricing

Pay per event

Go to Apify Store
Poland Developer Apartment Prices (dane.gov.pl)

Poland Developer Apartment Prices (dane.gov.pl)

Asking prices of every new-build apartment and house on sale in Poland, from the price lists developers must publish daily on dane.gov.pl. Price per m², area, location, developer, and price changes since your last run.

Pricing

Pay per event

Rating

0.0

(0)

Developer

Artur Flamandzki

Artur Flamandzki

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

16 hours ago

Last modified

Categories

Security

Limited permissions

Share

Poland Developer Apartment Prices (dane.gov.pl price lists)

Get the asking price of every new-build apartment and house on sale in Poland, unit by unit, from the price lists developers must publish every day under the 2025 price-transparency law. The actor reads the official open-data files from dane.gov.pl, maps the many file variants to one clean record, and tells you which prices changed since your last run.

Every unit becomes one record: developer (name, KRS, NIP, REGON), investment, voivodeship, city and street, unit number, total price, price per m², area, floor, rooms, VAT, the dates the prices apply from, and the licence and source file of the data.

What you can use it for

  • Price monitoring: run it daily and get only new units and price changes (cuts and rises, in PLN and %).
  • Market research and valuation: price per m² by city, district, developer and investment.
  • Real-estate portals and comparison sites: a complete, daily list of primary-market offers.
  • Banks, appraisers and investors: asking-price trends straight from the developers' own filings.
  • AI agents and analytics pipelines: structured, deduplicated data via the Apify API or MCP.

How it works

  1. The actor lists the price-list files developers sent to dane.gov.pl in the last N days and keeps the newest file of each developer dataset (optionally only for the developers you name).
  2. Each file (CSV in its many variants) is read and every row becomes one unit record; parking places, storage rooms and commercial units are classified, so you can keep only apartments and houses (the default) or ask for them.
  3. Your filters are applied (voivodeships, cities, property type).
  4. Each unit is compared with the price this actor last returned to you: previous_price_total, price_change, price_change_pct, price_changed, is_new. With Only new units and price changes on, a scheduled run returns only what changed: a ready-made price alert. The memory is kept per combination of filters and for 90 days after a unit was last seen.

Input

FieldWhat it does
Price lists published in the last N days1 = yesterday and today (best for a daily schedule); up to 60
DevelopersKeep only price lists whose title names these developers (e.g. Murapol); also makes runs cheaper
Voivodeshipse.g. mazowieckie, małopolskie (Polish letters optional)
Citiese.g. Warszawa, Kraków (matches city, municipality or county of the investment)
Property typeApartments and houses (default), apartments, houses, parking, storage, commercial, everything
Only new units and price changesIdeal for daily schedules
Max units / Max price-list filesStop after this many

Output example

{
"unit_key": "20 hex digits, stable per unit",
"developer_name": "Example Development sp. z o.o.",
"developer_krs": "0000123456",
"developer_nip": "1234567890",
"developer_regon": "123456789",
"developer_website": "https://example-development.pl",
"investment_name": "Apartamenty Harmonijne",
"investment_url": null,
"voivodeship": "mazowieckie",
"county": "wołomiński",
"municipality": "Radzymin",
"city": "Radzymin",
"street": "ul. Słoneczna",
"building_number": "12",
"postal_code": "05-250",
"property_type": "apartment",
"property_type_raw": "Mieszkanie",
"unit_number": "53H/2",
"source_unit_id": "2976",
"area_m2": 58.3,
"rooms": 4,
"floor": 1,
"price_total": 558436.0,
"price_per_m2": 9578.66,
"price_total_with_extras": null,
"currency": "PLN",
"vat_rate": 8.0,
"price_total_valid_from": "2025-09-11",
"price_per_m2_valid_from": "2025-09-11",
"prospectus_url": null,
"previous_price_total": 572000.0,
"price_change": -13564.0,
"price_change_pct": -2.37,
"price_changed": true,
"is_new": false,
"first_seen_at": "2026-10-20",
"published_date": "2026-11-03",
"dataset_url": "https://dane.gov.pl/pl/dataset/9580",
"file_url": "https://api.dane.gov.pl/media/resources/20261103/....csv",
"license": "CC0 1.0"
}

Pricing

Pay per event, no subscription. The prices are on the Pricing tab; you are charged for two events:

EventWhen
Price-list file (price-list-file)once per developer price-list file read in the run
Unit (unit)once per unit saved to the dataset; price changes cost nothing extra
  • Units make up most of the cost of a full snapshot (about 6,500 units a day for all Poland); with Only new units and price changes a daily run pays mainly the per-file fee plus the changed units.
  • Developers is applied before download, so it lowers both fees; voivodeship, city and property-type filters lower only the unit fees.
  • The form starts with Max units = 100 for a cheap first run; raise it for a full snapshot.
  • Set a maximum cost per run in Apify and the actor stops cleanly when it is reached, after delivering the units of the last file it charged for.

Data, licence and privacy

The source is the official Polish open-data portal dane.gov.pl. Almost all developer datasets are published under CC0 1.0 (no restrictions); a few use CC BY 4.0, which requires naming the source: every record carries its license, dataset_url and file_url. The actor never outputs the developers' phone numbers, e-mail addresses or fax numbers. Some developers are sole traders (registered in CEiDG, not KRS): for them the developer name, NIP and REGON identify a person, as published in the official register; use such records in line with the GDPR. Prices are asking prices as published by the developers; the actor does not correct them, it only drops values that cannot be real (e.g. a price of 5 PLN).

Known limits

  • Voivodeship and city filters work on the units inside the files, so every file read is charged; naming the developers is what makes a run cheaper.
  • Price changes are detected on the total price; a unit published only with a price per m² shows no change.
  • Files sent as XLSX or JSON (a few percent) are skipped and counted in the run's status message.
  • Developers that publish no file in the chosen period are not included; use a longer period for a full snapshot.