# Boligsiden Dk Properties and Details Scraper (`realestateapi/boligsiden-dk-properties-and-details-scraper`) Actor

Authorization-gated Boligsiden sitemap property records with optional permitted page metadata; failures and diagnostics are stored in OUTPUT, not the dataset.

- **URL**: https://apify.com/realestateapi/boligsiden-dk-properties-and-details-scraper.md
- **Developed by:** [Real Estate API](https://apify.com/realestateapi) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.99 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

## Boligsiden Dk Properties and Details Scraper

This local Apify Actor definition corresponds to CSV rank **443** (`lexis-solutions/boligsiden-dk-scraper`). It reads Danish property URLs from Boligsiden’s official public sitemap and can optionally request permitted property-page metadata. The default run is gated because no applicable data license or written authorization is recorded here.

Primary source: https://www.boligsiden.dk\
Default sitemap: https://www.boligsiden.dk/sitemaps/sitemap-1.xml

### Input

```json
{
  "sitemapUrls": [
    "https://www.boligsiden.dk/sitemaps/sitemap-1.xml"
  ],
  "maxSitemaps": 1,
  "maxProperties": 10,
  "includeDetails": false,
  "authorizationConfirmed": false,
  "timeoutSecs": 30
}
```

Each successful sitemap can produce `property-listing` rows containing a source-backed property URL, its sitemap, path classification, and address slug. Only those property records enter the Dataset. With `includeDetails: true`, accessible permitted page metadata may be added to the property row; blocked/error details are kept in the `OUTPUT` summary, and broker-written descriptions are omitted because the page marks them as protected from reuse.

The `OUTPUT` key-value record reports canonical `status` / `runStatus`, request counts, saved property rows, and aggregate failure details. Without an applicable written license, the Actor returns `SUCCEEDED` / `SKIPPED_POLICY` with zero requests and rows. Clean bounded or empty runs return `SUCCEEDED` / `COMPLETED`; failures without saved rows return `FAILED` / `FAILED` with native exit code 1; failures after saved rows return `SUCCEEDED` / `PARTIAL` with exit code 0.

### Responsible-use limits

The source and reuse terms remain unverified beyond the existing browser notes. Do not enable source requests unless an applicable written license or authorization covers collection and planned reuse. Requests stay on HTTPS Boligsiden hosts, redirects are blocked, and the Actor does not sign in, submit forms, solve challenges, or bypass access controls.

### Local run

The historical local storage contains five sitemap-backed property URL records. Sitemap observations and detail diagnostics were archived outside the Actor folder; see the actor-local `AGENTS.md` for hashes. No source request or Actor run was made in the status audit.

### Dependency remediation — October 3, 2026

This Actor uses native HTTP and parser code, with a small readable default-storage adapter and the pinned official Apify logger. The unused SDK/crawler/proxy/cache dependency graph was removed because its current http-cache-semantics advisory has no released fix. Cloud storage uses the documented Apify REST interface and bearer headers; local writes append indexed JSON without overwriting historical rows. Storage failures propagate and ambiguous POST writes are not retried. Native exit codes and source authorization/access gates are preserved. Node 22.19+ is required. The source remains unqualified until its existing permission/access prerequisites are met.

Relevant advisory: https://github.com/advisories/GHSA-ch52-4w7c-c8xp. Runtime regression checks: node --test test/platform.test.js.

# Actor input Schema

## `sitemapUrls` (type: `array`):

Public Boligsiden sitemap URLs. The default is the first official property sitemap.

## `maxSitemaps` (type: `integer`):

Maximum official sitemap files to request.

## `maxProperties` (type: `integer`):

Maximum source-backed property URLs to emit.

## `includeDetails` (type: `boolean`):

Request each permitted property page. HTTP 403 or challenge responses are recorded in OUTPUT only. Broker-written property description text is omitted because the page marks it as protected from reuse.

## `authorizationConfirmed` (type: `boolean`):

Confirm only if an applicable written data license or authorization covers this collection and reuse. The default skip makes no source requests.

## `timeoutSecs` (type: `integer`):

Per-sitemap or property-page timeout.

## Actor input object example

```json
{
  "sitemapUrls": [
    "https://www.boligsiden.dk/sitemaps/sitemap-1.xml"
  ],
  "maxSitemaps": 1,
  "maxProperties": 10,
  "includeDetails": false,
  "authorizationConfirmed": false,
  "timeoutSecs": 30
}
```

# Actor output Schema

## `dataset` (type: `string`):

Dataset containing public-source records.

## `keyValueStore` (type: `string`):

Key-value store containing the OUTPUT run summary.

# 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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "sitemapUrls": [
        "https://www.boligsiden.dk/sitemaps/sitemap-1.xml"
    ],
    "maxSitemaps": 1,
    "maxProperties": 10,
    "includeDetails": false,
    "authorizationConfirmed": false,
    "timeoutSecs": 30
};

// Run the Actor and wait for it to finish
const run = await client.actor("realestateapi/boligsiden-dk-properties-and-details-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 '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "sitemapUrls": ["https://www.boligsiden.dk/sitemaps/sitemap-1.xml"],
    "maxSitemaps": 1,
    "maxProperties": 10,
    "includeDetails": False,
    "authorizationConfirmed": False,
    "timeoutSecs": 30,
}

# Run the Actor and wait for it to finish
run = client.actor("realestateapi/boligsiden-dk-properties-and-details-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 '{
  "sitemapUrls": [
    "https://www.boligsiden.dk/sitemaps/sitemap-1.xml"
  ],
  "maxSitemaps": 1,
  "maxProperties": 10,
  "includeDetails": false,
  "authorizationConfirmed": false,
  "timeoutSecs": 30
}' |
apify call realestateapi/boligsiden-dk-properties-and-details-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,realestateapi/boligsiden-dk-properties-and-details-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 <APIFY_API_TOKEN>` 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/dXkwYOFVx547XwAnh/builds/ObHDpw5GkZPeOpO1V/openapi.json