# Boliga Denmark Real Estate Scraper (`datascrapers/boliga-dk-scraper`) Actor Scrape property listings from Boliga.dk (Denmark). Search by zip code, free text, or result URLs. Optionally fetch full listing details including agent contact, BBR building data, sales history, and price analytics. - **URL**: https://apify.com/datascrapers/boliga-dk-scraper.md - **Developed by:** [Data Scrapers](https://apify.com/datascrapers) (community) - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $0.70 / 1,000 dataset items This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README **Boliga Scraper** creates a structured dataset of property listings collected from Boliga in Denmark. Each dataset item is one home and can include the street, city, zip code, price, rooms, living area, property type, energy class, and listing URL. Query the source with a zip code, a place name, or a Boliga result URL, limit the run with `maxItems`, and retrieve records through the Apify Dataset API or export them as JSON, CSV, Excel, XML, or another supported format. [![Boliga Scraper β€” input to structured data](https://raw.githubusercontent.com/faizanalii/apify-actor-assets/main/boliga-dk-scraper/boliga-dk-scraper-value-demo.gif)](https://apify.com/datascrapers/boliga-dk-scraper) ### Dataset at a glance | Property | Value | |---|---| | Source | boliga.dk | | Record unit | One property listing | | Input methods | `searchQueries`, `startUrls`, price and size filters | | Main identifiers | `id` and `url` | | Delivery | Apify Dataset and API | | Export formats | JSON, CSV, Excel, XML, and other Apify dataset exports | | Update model | Fresh records per Actor run | | Pricing | $1.00 per 1,000 listings. Optional details from $2.00 per 1,000. | ### Coverage and available records The Actor searches Boliga by zip code, place name, or a copied result or listing URL. The saved sample is a villa in Hobro, zip 9500. Supported: - Zip codes and free-text places - Property type, price, rooms, size, lot size, year built, days on market, and energy class filters - Broker, self-sale, and foreclosure exclusions - A result cap through `maxItems`. `0` means no cap Not currently collected unless `extractDetails` is true: - Agent contact, building records, sales history, and the full photo gallery - Those extra pages charge `listing-details` ### Data dictionary Fields match a saved search result. Prices are Danish kroner. | Field | Type | Nullable | Description | Example | |---|---|---:|---|---| | `id` | number | No | Boliga listing id. Best field for deduplication. | `2352957` | | `url` | string | Yes | Public address URL. | `https://www.boliga.dk/adresse/godt-gemt-2-9500-hobro-1451200001` | | `street` | string | Yes | Street and number. | `Godt Gemt 2` | | `city` | string | Yes | City name. | `Hobro` | | `zipCode` | number | Yes | Postal code. | `9500` | | `price` | number | Yes | Asking price in DKK. | `645000` | | `rooms` | number | Yes | Room count. | `3` | | `size` | number | Yes | Living area in square meters. | `127` | | `propertyTypeName` | string | Yes | Type label. | `Villa` | | `energyClass` | string | Yes | Energy label. | `D` | | `latitude` | number | Yes | Latitude. | Present on the saved row | | `longitude` | number | Yes | Longitude. | Present on the saved row | | `squaremeterPrice` | number | Yes | Price per square meter. | Present on the saved row | ### Example dataset record ```json { "id": 2352957, "url": "https://www.boliga.dk/adresse/godt-gemt-2-9500-hobro-1451200001", "street": "Godt Gemt 2", "city": "Hobro", "zipCode": 9500, "price": 645000, "rooms": 3.0, "size": 127, "propertyTypeName": "Villa", "energyClass": "D" } ``` The saved row came from a zip `9500` search with `extractDetails` off. ### Query and input reference | Input | Type | Required | Default | Accepted values | Description | |---|---|---:|---|---|---| | `startUrls` | array | No | `[{"url": "https://www.boliga.dk/resultat?searchTab=0&sort=daysForSale-a&zipCodes=9500"}]` | | Paste Boliga search result URLs (e.g. | | `searchQueries` | array | No | `["9500"]` | | Danish zip codes (e.g. | | `propertyTypes` | array | No | ``| villa, raekkehus, ejerlejlighed, fritidshus, andelsbolig, landejendom, helaarsgrund, fritidsgrund | Leave empty for all property types. | | `priceMin` | integer | No |`` | | Minimum asking price in Danish kroner. | | `priceMax` | integer | No | ``| | Maximum asking price in Danish kroner. | | `roomsMin` | integer | No |`` | | Minimum number of rooms. | | `roomsMax` | integer | No | ``| | Maximum number of rooms. | | `sizeMin` | integer | No |`` | | Minimum living area in square meters. | | `sizeMax` | integer | No | ``| | Maximum living area in square meters. | | `lotSizeMin` | integer | No |`` | | Minimum plot/lot size in square meters. | | `lotSizeMax` | integer | No | ``| | Maximum plot/lot size in square meters. | | `buildYearMin` | integer | No |`` | | Minimum construction year. | | `buildYearMax` | integer | No | ``| | Maximum construction year. | | `daysForSaleMin` | integer | No |`` | | Minimum days the listing has been on the market. | | `daysForSaleMax` | integer | No | ``| | Maximum days the listing has been on the market. | | `energyClassMin` | string | No |`` | | Minimum energy label (e.g. | | `energyClassMax` | string | No | ``| | Maximum energy label (e.g. | | `zipCodes` | string | No |`` | | Comma-separated Danish zip codes applied to all search queries (e.g. | | `municipality` | integer | No | \`\` | | Danish municipality code (kommunekode), e.g. | | `sort` | string | No | `daysForSale-a` | daysForSale-a, daysForSale-d, price-a, price-d, views-d, squaremeterPrice-a, squaremeterPrice-d, rooms-d, size-d, buildYear-d | How to sort search results. | | `hideBrokerListings` | boolean | No | `False` | | Exclude standard broker listings from results. | | `hideSelfSale` | boolean | No | `False` | | Exclude private / self-sale listings. | | `hideForeclosure` | boolean | No | `False` | | Exclude foreclosure listings. | | `extractDetails` | boolean | No | `False` | | When enabled, fetches full listing details for each result (agent contact, BBR building data, sales history, price analytics, full photo gallery). | | `detailConcurrency` | integer | No | `10` | | Maximum number of listings processed in parallel when detail extraction is enabled. | | `maxItems` | integer | No | `0` | | Maximum number of listings to scrape (0 = unlimited). | | `proxyConfiguration` | object | No | `{"useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"]}` | | Proxy settings. | A run needs `searchQueries` or `startUrls`. Minimal request: ```json { "searchQueries": ["9500"], "maxItems": 10 } ``` ### Retrieve the data through the API 1. Start `datascrapers/boliga-dk-scraper` with the JSON input. 2. Wait until the run finishes, or call the synchronous dataset endpoint. 3. Read items from the run's default dataset. 4. Paginate with dataset `offset` and `limit`. ```python from apify_client import ApifyClient client = ApifyClient("") run = client.actor("datascrapers/boliga-dk-scraper").call(run_input={ "searchQueries": ["9500"], "maxItems": 10, }) for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item["id"], item["street"], item["price"]) ``` Other languages are listed on the Actor's API tab. This is the Apify Actor API, not a Boliga API. ### Data quality and record handling - One dataset item is one listing. Each pushed listing charges one `dataset-item` event. - Deduplicate on `id`. - `extractDetails` charges one `listing-details` event per enriched listing. - Prices are kroner as returned by Boliga. The Actor does not convert them. - `rooms` can be a decimal. ### Pricing and cost examples The price file sets **$1.00 per 1,000** listings and **$2.00 per 1,000** listing details on the free plan. Bronze, Silver, and Gold rates are lower. Platinum and Diamond use the Gold rate. | Event | Free | Bronze | Silver | Gold | |---|---:|---:|---:|---:| | `dataset-item` per 1,000 | $1.00 | $0.90 | $0.80 | $0.70 | | `listing-details` per 1,000 | $2.00 | $1.70 | $1.50 | $1.30 | A free-plan run of 1,000 listings with details is $3.00 in events. Platform usage, including compute and proxy, is billed separately by Apify. ### Limitations and responsible data use - Coverage is the search the input requests, not every Danish address. - Place names must match Boliga's search. Zip codes are the more stable filter. - Asking prices change. This dataset is not a historical archive unless `extractDetails` returns the sales history for that run. - You are responsible for complying with Boliga's terms and applicable law. ### Dataset questions #### What does one dataset item represent? One Boliga property listing from a search or listing URL. #### Which field should I use as a unique identifier? Use `id`. #### Are fields nullable or conditional? Yes. Detail-only blocks are present when `extractDetails` is enabled and the listing page returns them. #### Can I retrieve the records as CSV or JSON? Yes. Export the default dataset as JSON, CSV, Excel, XML, or another Apify format. #### How do I paginate large datasets? Use `limit` and `offset` on the dataset items endpoint. `maxItems` limits how many rows the run saves. #### Does the Actor return historical data? The search row is the current listing. Sales history is conditional on `extractDetails`. #### What counts as a billable result? One `dataset-item` event per saved listing, plus one `listing-details` event when detail extraction runs for that listing. ### Related datasets from Data Scrapers - [Bezrealitky Scraper](https://apify.com/datascrapers/bezrealitky-scraper) collects Czech sale and rent offers. - [BNP Paribas Real Estate Scraper](https://apify.com/datascrapers/bnppre-scraper) collects German commercial property listings. - [Boligsiden Scraper](https://apify.com/datascrapers/boligsiden-dk-scraper) collects Danish for-sale, sold, and rental rows. - [Booli Scraper](https://apify.com/datascrapers/booli-se-scraper) collects Swedish for-sale and sold homes. - [Apartments Scraper](https://apify.com/datascrapers/apartments-scraper) collects US rental listings. - [Bayut Scraper](https://apify.com/datascrapers/bayut-scraper) collects UAE property listings. ### Data Scrapers support Questions about this dataset: stardustspotlight@gmail.com # Actor input Schema ## `startUrls` (type: `array`): Paste Boliga search result URLs (e.g. https://www.boliga.dk/resultat?searchTab=0\&zipCodes=9500) or listing URLs (e.g. https://www.boliga.dk/adresse/thostruphovgaardsvej-4-9500-hobro-995530789). Query parameters from search URLs are used as filters. Listing URLs scrape those specific properties. ## `searchQueries` (type: `array`): Danish zip codes (e.g. 9500) or free-text location queries (e.g. Hobro, KΓΈbenhavn). Zip codes use the zipCodes filter; other text uses Boliga's q search. ## `propertyTypes` (type: `array`): Leave empty for all property types. ## `priceMin` (type: `integer`): Minimum asking price in Danish kroner. ## `priceMax` (type: `integer`): Maximum asking price in Danish kroner. ## `roomsMin` (type: `integer`): Minimum number of rooms. ## `roomsMax` (type: `integer`): Maximum number of rooms. ## `sizeMin` (type: `integer`): Minimum living area in square meters. ## `sizeMax` (type: `integer`): Maximum living area in square meters. ## `lotSizeMin` (type: `integer`): Minimum plot/lot size in square meters. ## `lotSizeMax` (type: `integer`): Maximum plot/lot size in square meters. ## `buildYearMin` (type: `integer`): Minimum construction year. ## `buildYearMax` (type: `integer`): Maximum construction year. ## `daysForSaleMin` (type: `integer`): Minimum days the listing has been on the market. ## `daysForSaleMax` (type: `integer`): Maximum days the listing has been on the market. ## `energyClassMin` (type: `string`): Minimum energy label (e.g. A, B, C). ## `energyClassMax` (type: `string`): Maximum energy label (e.g. C, D). ## `zipCodes` (type: `string`): Comma-separated Danish zip codes applied to all search queries (e.g. 2100,2200,9500). ## `municipality` (type: `integer`): Danish municipality code (kommunekode), e.g. 846 for Mariagerfjord. ## `sort` (type: `string`): How to sort search results. ## `hideBrokerListings` (type: `boolean`): Exclude standard broker listings from results. ## `hideSelfSale` (type: `boolean`): Exclude private / self-sale listings. ## `hideForeclosure` (type: `boolean`): Exclude foreclosure listings. ## `extractDetails` (type: `boolean`): When enabled, fetches full listing details for each result (agent contact, BBR building data, sales history, price analytics, full photo gallery). Charges an extra listing-details event per enriched listing. ## `detailConcurrency` (type: `integer`): Maximum number of listings processed in parallel when detail extraction is enabled. ## `maxItems` (type: `integer`): Maximum number of listings to scrape (0 = unlimited). ## `proxyConfiguration` (type: `object`): Proxy settings. Residential proxy is recommended for reliable runs on Apify Cloud. ## Actor input object example ```json { "startUrls": [ { "url": "https://www.boliga.dk/resultat?searchTab=0&sort=daysForSale-a&zipCodes=9500" } ], "searchQueries": [ "9500" ], "sort": "daysForSale-a", "hideBrokerListings": false, "hideSelfSale": false, "hideForeclosure": false, "extractDetails": false, "detailConcurrency": 10, "maxItems": 20, "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ] } } ``` # Actor output Schema ## `dataset` (type: `string`): JSON array of scraped property listings ## `runStats` (type: `string`): Aggregate run statistics including record counts and timestamps # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "startUrls": [ { "url": "https://www.boliga.dk/resultat?searchTab=0&sort=daysForSale-a&zipCodes=9500" } ], "searchQueries": [ "9500" ], "maxItems": 20, "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ] } }; // Run the Actor and wait for it to finish const run = await client.actor("datascrapers/boliga-dk-scraper").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`πŸ’Ύ Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // πŸ“š Want to learn more πŸ“–? Go to β†’ https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "startUrls": [{ "url": "https://www.boliga.dk/resultat?searchTab=0&sort=daysForSale-a&zipCodes=9500" }], "searchQueries": ["9500"], "maxItems": 20, "proxyConfiguration": { "useApifyProxy": True, "apifyProxyGroups": ["RESIDENTIAL"], }, } # Run the Actor and wait for it to finish run = client.actor("datascrapers/boliga-dk-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"πŸ’Ύ Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # πŸ“š Want to learn more πŸ“–? Go to β†’ https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "startUrls": [ { "url": "https://www.boliga.dk/resultat?searchTab=0&sort=daysForSale-a&zipCodes=9500" } ], "searchQueries": [ "9500" ], "maxItems": 20, "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ] } }' | apify call datascrapers/boliga-dk-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,datascrapers/boliga-dk-scraper" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/ipFUaCLAh9Vl2RfUh/builds/uBMgTJSl0geoflR2H/openapi.json