Boliga.dk Scraper avatar

Boliga.dk Scraper

Pricing

from $0.99 / 1,000 results

Go to Apify Store
Boliga.dk Scraper

Boliga.dk Scraper

Extract real estate listings from Boliga.dk with structured property data including price, address, size, rooms, lot area, energy rating, listing status, images, coordinates, and property details. Perfect for market research, price tracking, lead generation, and analytics.

Pricing

from $0.99 / 1,000 results

Rating

5.0

(1)

Developer

Shahid Irfan

Shahid Irfan

Maintained by Community

Actor stats

0

Bookmarked

16

Total users

2

Monthly active users

21 days ago

Last modified

Features

Limited permissions

Share

What does Boliga.dk Scraper do?

Boliga.dk Scraper collects Danish property listings from Boliga.dk. Give it a Boliga result URL, an area, or a city name, and it returns structured rows with address, asking price, size, rooms, energy label, days on market, images, and a link to the listing page. The dataset is ready for price tracking, area comparisons, or feeding a property database.

Why use Boliga.dk Scraper?

  • One row per listing - Address, price, building data, and images arrive as separate fields instead of text you have to split.
  • Three ways to search - Mirror a Boliga result URL, use a region ID, or search by city name.
  • Duplicate removal - The same listing never appears twice in one run, even when it shows up on several pages.
  • Repeat runs stay fast - One request returns up to 50 listings, so a scheduled region check is a handful of requests.
  • Exports that fit your workflow - Download JSON, CSV, Excel, or XML, or send the dataset to another tool through the Apify API.

What data can you extract from Boliga.dk?

FieldDescription
streetStreet address of the property
zip_codeDanish postal code
cityCity name
priceAsking price in DKK
property_typeBoliga property type code
roomsNumber of rooms
sizeRegistered living area in square meters
lot_sizeLot size in square meters
build_yearYear the property was built
energy_classEnergy label
days_for_saleDays the listing has been on the market
squaremeter_pricePrice per square meter
monthly_net and monthly_expensesMonthly cost estimates when Boliga publishes them
latitude and longitudeCoordinates for mapping
image_url and imagesPrimary image and the full image list
listing_urlDirect link to the Boliga listing page

How to use Boliga.dk Scraper

  1. Open the Actor on Apify Store.
  2. Paste a Boliga result URL, or skip the URL and fill in an area ID or a city name.
  3. Set how many listings you want and how many result pages the Actor may read.
  4. Run the Actor.
  5. Open the dataset, or connect it to Sheets, a webhook, or your own API client.

Search modes

Use one mode per run. If you supply an area ID or a city name, the Actor ignores the start URL so the two searches never mix.

  • Start URL - Mirrors a Boliga result page, including region, property type, and filters that are part of the URL.
  • Area ID - Searches one of the eleven Boliga regions. 1 Copenhagen, 2 Greater Copenhagen, 3 North Zealand, 4 Bornholm, 5 East Zealand, 6 West and South Zealand, 7 Funen, 8 South Jutland, 9 West Jutland, 10 East Jutland, 11 North Jutland.
  • Place - Searches a city or place name such as Frederiksberg or Odense.

Input Parameters

ParameterTypeRequiredDefaultDescription
startUrlStringNoCopenhagen region result URLBoliga result URL to mirror. Ignored when areaId or place is set.
areaIdIntegerNo-Boliga region identifier from 1 to 11
placeStringNo-City or place name to search for
results_wantedIntegerNo20Maximum number of listings to save
max_pagesIntegerNo5Maximum number of result pages to read
proxyConfigurationObjectNoNo proxyOptional proxy. Boliga is read directly, so a proxy is only needed when your own network requires one.

Output Data

FieldTypeDescription
listing_idIntegerBoliga listing identifier
guidStringBoliga listing GUID when published
streetStringStreet address
clean_streetStringStreet name without house number
zip_codeIntegerDanish postal code
cityStringCity name
municipality_codeIntegerMunicipality code
area_idIntegerBoliga area identifier
property_typeIntegerProperty type code
item_typeIntegerListing item type code
priceIntegerAsking price in DKK
price_change_percent_totalNumberTotal price change percentage
squaremeter_priceNumberPrice per square meter
monthly_netIntegerMonthly net payment estimate
monthly_expensesIntegerMonthly expense estimate
down_paymentIntegerDown payment estimate
energy_classStringEnergy label
roomsNumberNumber of rooms
sizeIntegerRegistered living area in square meters
lot_sizeIntegerLot size in square meters
basement_sizeIntegerBasement size in square meters
business_areaIntegerCommercial floor area
floorIntegerFloor number when published
build_yearIntegerYear built
days_for_saleIntegerDays on market
open_houseStringNext open house time when scheduled
viewsIntegerListing view count
latitudeNumberLatitude
longitudeNumberLongitude
created_dateStringListing creation timestamp
last_seenStringLast time Boliga saw the listing
is_activeBooleanWhether the listing is still active
is_foreclosureBooleanForeclosure flag
is_premium_agentBooleanPremium agent flag
self_saleBooleanSold by owner
image_urlStringPrimary image URL
imagesArrayImage objects with id, date, and URL
listing_urlStringBoliga listing page URL
dawa_idStringDAWA address identifier
bfe_numberIntegerBFE property number
on_the_wayBooleanNew-build listing flag
project_sale_urlStringProject sales page when published
search_urlStringResult URL used for the run
source_area_slugStringRegion slug from the result URL
source_property_slugStringProperty type slug from the result URL

Usage Examples

Collect the newest listings in Copenhagen

Mirror a Copenhagen result page and save 20 listings:

{
"startUrl": "https://www.boliga.dk/resultat/landsdele/koebenhavn-by/alle-til-salg",
"results_wanted": 20,
"max_pages": 2
}

Search one region by area ID

Use a Boliga area identifier when you do not have a URL:

{
"areaId": 7,
"results_wanted": 50,
"max_pages": 3
}

Search a city by name

Collect properties in a single city:

{
"place": "Frederiksberg",
"results_wanted": 40,
"max_pages": 2
}

Filter a result URL

Boliga result URLs accept filters. This example reads villas in Funen sorted by price:

{
"startUrl": "https://www.boliga.dk/resultat/landsdele/fyn/villaer-til-salg?sort=price-a",
"results_wanted": 100,
"max_pages": 4
}

Follow a postal code

Postal code filters work through the result URL query string:

{
"startUrl": "https://www.boliga.dk/resultat?zipCodes=2100",
"results_wanted": 30,
"max_pages": 2
}

Sample Output

{
"listing_id": 2380950,
"guid": "B339AEF9-6723-4C04-BAE6-0EEC3BCF3C54",
"street": "Duevej 42 st 18",
"clean_street": "Duevej",
"zip_code": 2000,
"city": "Frederiksberg",
"municipality_code": 147,
"area_id": 1,
"property_type": 3,
"item_type": 0,
"price": 425000,
"price_change_percent_total": 0,
"squaremeter_price": 28333,
"monthly_net": 2034,
"monthly_expenses": 192,
"down_payment": 25000,
"energy_class": "-",
"rooms": 1,
"size": 15,
"lot_size": 0,
"basement_size": 0,
"build_year": 1960,
"days_for_sale": 0,
"views": 0,
"latitude": 55.6905,
"longitude": 12.52851,
"created_date": "2026-10-30T23:35:03.787Z",
"last_seen": "2026-10-30T23:35:03.787Z",
"is_active": true,
"is_foreclosure": false,
"is_premium_agent": false,
"self_sale": false,
"image_url": "https://i.boliga.org/dk/550x/2380/2380950.jpg",
"listing_url": "https://www.boliga.dk/bolig/2380950/duevej-42-st-18-2000-frederiksberg",
"bfe_number": 187847,
"on_the_way": false,
"search_url": "https://www.boliga.dk/resultat/landsdele/koebenhavn-by/alle-til-salg",
"source_area_slug": "koebenhavn-by"
}

Tips for Best Results

  • Start small. Run with results_wanted: 20 and max_pages: 2, check the dataset, then raise both values.
  • Match max_pages to the target. Each page holds up to 50 listings, so max_pages: 5 can return 250 rows. The run stops as soon as results_wanted is reached.
  • Keep filters in the URL. Region, property type, price, size, and sort filters belong in startUrl, where Boliga reads them.
  • Use one search mode. If you fill in areaId or place, leave startUrl empty to keep the search unambiguous.
  • Schedule instead of repeating. A daily schedule on a region gives you a price history without extra setup.

How the Actor handles Boliga changes

Boliga updates its result pages and its request format from time to time. The Actor is built to keep running through those changes:

  • If a response comes back empty, blocked, or in an unexpected format, the Actor retries with a different browser profile before it reports a problem.
  • If the primary route stops answering, the Actor checks for an alternate route and then reads the server-rendered result page, which carries the same listing data and identifiers.
  • Network errors, timeouts, and rate limits are retried a limited number of times with increasing delays. Permanent errors are not retried, so a bad input fails fast instead of looping.
  • One page failing after earlier pages succeeded does not discard the rows already saved.

Integrations

  • Google Sheets - Send listing data to a spreadsheet for analysis or sharing.
  • Webhooks - Trigger a downstream workflow when a run finishes.
  • Make or Zapier - Connect results to no-code automations and alerts.
  • API - Read datasets from your own systems through the Apify API.
  • CSV, Excel, JSON, XML - Download the dataset in any of these formats from Apify Console.

Frequently Asked Questions

Can I export the data to CSV or Excel?

Yes. Apify datasets can be downloaded as CSV, Excel, JSON, XML, and other supported formats from the dataset page.

Can I run this Actor on a schedule?

Yes. Schedule the Actor in Apify Console to run hourly, daily, weekly, or at another interval. Scheduled runs are the simplest way to track new listings and price changes.

How are duplicate listings handled?

Listings are deduplicated by the Boliga listing identifier within a run, so the same property appears once even when it is returned on more than one page.

Can I search by postal code?

Yes. Put the postal code in the result URL query string, for example https://www.boliga.dk/resultat?zipCodes=2100. Region and property type filters use the same pattern.

How many listings can one run collect?

The run stops at results_wanted, and max_pages caps how many result pages the Actor reads. A page holds up to 50 listings, so results_wanted: 200 with max_pages: 5 collects up to 250 rows and usually stops at 200.

What if some fields are missing?

Boliga leaves some fields empty for certain listings. Basement size, floor, open house time, and project sale URL are the most common gaps. Check several rows before assuming something broke.

Why did a run return no listings?

A filter that matches nothing, such as an unused postal code, returns an empty dataset without an error. Check the result URL in a browser first. If the same URL returns listings on the site and not in the Actor, open an issue with the URL you used.

Scraping public web data can be legal, but you are responsible for complying with applicable laws, Boliga's terms of service, and your own data handling obligations.

  • Propertyfinder Scraper - Property listings from PropertyFinder.ae with prices, specifications, location data, agent details, and media.
  • Housing.com Property Scraper - Real estate listings from Housing.com with prices, seller details, sizes, tags, and location data.

Support

For issues, feature requests, or custom Actor work, use the Issues tab on the Actor page or contact the developer through Apify.

This Actor is designed for legitimate data collection from publicly available sources on Boliga.dk. Users are responsible for using the data responsibly and complying with applicable laws, the Boliga.dk terms of service, and data protection regulations.