Boliga Denmark Real Estate Scraper

Boliga Denmark Real Estate Scraper collects property listings from Boliga.dk and turns them into structured data for Danish market research, investment analysis, and lead generation. Provide a zip code such as 9500, a location query such as København, or a Boliga search URL, then export price, address, rooms, energy class, and agent contact to JSON, CSV, or Excel. Use it to monitor listings, compare municipalities, and schedule recurring collection. Pricing starts at $1.00 per 1,000 listings, with optional listing details at $2.00 per 1,000.

What can you automate with Boliga Denmark Real Estate Scraper?

• Build Danish listing databases — Collect properties by zip code, free-text query, or Boliga search and listing URLs.
• Enrich with full listing data — Add agent contact, BBR building data, sales history, price analytics, and photo galleries when Extract Listing Details is on.
• Filter by property type and price — Narrow by villa, apartment, price range, rooms, size, build year, days for sale, and energy class.
• Track market movement — Sort by days for sale, price, views, or price per m² to spot stale inventory or price changes.
• Schedule recurring collection — Run daily or weekly and push new listings into Sheets, a CRM, or an alert workflow.

Who is this scraper for?

Team	Workflow
Real estate investors	Compare asking prices, price/m², and sales history across Danish municipalities.
Market researchers	Monitor inventory, days on market, and energy labels by zip code.
Lead-generation teams	Collect agent names, phone numbers, and emails when detail extraction is enabled.
Proptech products	Feed structured Boliga listings into dashboards and alerts.

What data can you collect from Boliga.dk?

Data group	Example fields	How it helps
Listing identity	listing ID, address, zip code, city, coordinates, property type	Identify each property and deduplicate with the listing ID.
Commercial	price, price/m², days for sale, sort metadata	Compare asking prices and time on market.
Property	rooms, living area, lot size, basement size, build year, energy class	Filter by size, age, and energy rating.
Media	image URLs, full photo gallery	Review listing presentation.
Agent contact	agent name, phone, email, homepage, brokerage URL	Appear when Extract Listing Details succeeds.
BBR and analytics	BBR building data, sales history, price changes, municipality stats	Appear when detail extraction is enabled.

Basic search-card fields are always collected. Agent contact, BBR data, and sales history appear only when Extract Listing Details is on.

How to use Boliga Denmark Real Estate Scraper

1. Open the Boliga Denmark Real Estate Scraper on Apify.
2. Enter Danish zip codes, location queries, or paste Boliga search or listing URLs.
3. Set property filters and toggle Extract Listing Details if you need agent contact or BBR data.
4. Run the Actor — it writes one dataset row per listing.
5. Export the dataset or connect it to your workflow.

{
    "searchQueries": ["9500"],
    "propertyTypes": ["villa", "ejerlejlighed"],
    "priceMin": 100000,
    "priceMax": 3000000,
    "sort": "daysForSale-a",
    "extractDetails": true,
    "maxItems": 20,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": ["RESIDENTIAL"]
    }
}

Example workflow

Build a weekly North Jutland villa watchlist

1. Schedule a Monday run with searchQueries = ["9500"], propertyTypes = ["villa"], and sort = "daysForSale-a".
2. Enable Extract Listing Details when you need agent phone and sales history.
3. Keep rows inside your price and room band using price and rooms.
4. Send new records to Google Sheets through a webhook after each run.
5. Deduplicate user-side against the stable listing ID.

The Actor does not merge results across runs — those steps happen in your pipeline.

Automate and integrate your results

• Schedules — Run weekly for a market snapshot or daily when monitoring new inventory in a zip code.
• Webhooks — Push completed runs into Google Sheets, Make, Zapier, Slack, or a CRM.
• Exports and API — Download JSON, CSV, Excel, or HTML from the Apify Console, or start a run from the API:

curl -X POST "https://api.apify.com/v2/acts/scraptivo~boliga-dk-scraper/runs?token=YOUR-APIFY-TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "searchQueries": ["9500"],
    "maxItems": 20,
    "extractDetails": false
  }'

Use the listing ID as the stable deduplication key across runs.

Input reference

Field	Type	Required	Default	What it controls
startUrls	array	No	—	Boliga search or listing URLs.
searchQueries	array	No	9500	Danish zip codes or free-text location queries.
propertyTypes	array	No	all	Villa, rækkehus, ejerlejlighed, and other Boliga types.
priceMin / priceMax	integer	No	—	Asking price range in DKK.
roomsMin / roomsMax	integer	No	—	Room count range.
sizeMin / sizeMax	integer	No	—	Living area range in m².
lotSizeMin / lotSizeMax	integer	No	—	Plot size range in m².
buildYearMin / buildYearMax	integer	No	—	Construction year range.
daysForSaleMin / daysForSaleMax	integer	No	—	Days on market range.
energyClassMin / energyClassMax	string	No	—	Energy label range.
zipCodes	string	No	—	Comma-separated zip codes applied to all queries.
municipality	integer	No	—	Danish municipality code (kommunekode).
sort	string	No	daysForSale-a	Sort order for search results.
hideBrokerListings	boolean	No	false	Exclude standard broker listings.
hideSelfSale	boolean	No	false	Exclude private self-sale listings.
hideForeclosure	boolean	No	false	Exclude foreclosure listings.
extractDetails	boolean	No	false	Fetch agent contact, BBR data, sales history, and analytics.
detailConcurrency	integer	No	10	Parallel detail requests when extraction is on (1–50).
maxItems	integer	No	0	Maximum listings (0 = unlimited).
proxyConfiguration	object	No	residential	Proxy settings. Residential proxy is recommended.

Can I paste a Boliga search URL instead of filters?

Yes. When startUrls are provided, query parameters from those URLs drive the search. Listing URLs scrape those specific properties.

Output example

{
    "id": "995530789",
    "url": "https://www.boliga.dk/adresse/thostruphovgaardsvej-4-9500-hobro-995530789",
    "address": "Thostruphovgaardsvej 4",
    "zipCode": "9500",
    "city": "Hobro",
    "price": 2495000,
    "propertyType": "Villa",
    "rooms": 5,
    "size": 180,
    "lotSize": 1200,
    "buildYear": 1978,
    "energyClass": "D",
    "daysForSale": 42,
    "pricePerSqm": 13861
}

When extractDetails is enabled, the same row can also include agent contact, BBR data, sales history, and a full image gallery.

How much does it cost to scrape Boliga.dk?

Billing is pay-per-event. A one-time Actor Start fee of $0.00005 applies per run.

Event	When it is charged	Price
Listing	Each property row from search results	$1.00 per 1,000
Listing Details	Each listing successfully enriched when extractDetails is on	$2.00 per 1,000

A listing-only run of 1,000 properties costs about $1.00 plus Actor Start. Adding details on every listing costs about $3.00 plus Actor Start. Apify plan discounts may reduce these prices. Platform compute and proxy usage are billed separately on your Apify plan.

Reliability and responsible use

• Residential proxy recommended — Default input uses Apify residential proxies for reliable Boliga runs.
• Conditional fields — Agent contact, BBR data, and sales history appear only when detail extraction succeeds.
• Public data — The Actor collects publicly visible listing information from Boliga.dk.
• User responsibility — Use collected data in line with applicable laws and Boliga terms.

Frequently asked questions

Can I scrape Boliga listings by Danish zip code?

Yes. Add zip codes to searchQueries, such as 9500, or set zipCodes to a comma-separated list like 2100,2200,9500.

Can I schedule Boliga Denmark Real Estate Scraper to run automatically?

Yes. Create an Apify schedule on a saved task. Separate tasks per municipality or zip code make monitoring easier.

What counts as one result?

Each property written to the dataset counts as one Listing event. When extractDetails is enabled, each successfully enriched listing also counts as one Listing Details event.

Why are some agent fields empty?

Agent phone, email, and BBR fields appear only when Extract Listing Details is on and Boliga publishes them for that listing.

How do I avoid duplicate records?

Within one run, listings are unique by listing ID. Across runs the Actor appends results. Deduplicate user-side against the listing ID when combining datasets.

Do I need a proxy?

Residential proxy is recommended for reliable runs on Apify Cloud. The default input enables Apify residential proxies.

Related Scraptivo automations

• Funda Netherlands Real Estate Scraper — Dutch property listings
• Idealista Scraper — Spanish and Portuguese property listings
• Realestate.com.au Scraper — Australian property listings
• Daft.ie Property Scraper — Irish property listings
• Autotrader Scraper — UK vehicle listings

Support and custom workflows

Need a different field, source, or delivery workflow? Contact Scraptivo at scraptivo@gmail.com. Include the Actor name, sample URL, required fields, and expected volume so we can assess the request.