# FINN Property Sales Properties and Details Scraper (`realestateapi/finn-property-sales-properties-and-details-scraper`) Actor

FINN property-sales Actor. Default runs report SUCCEEDED / SKIPPED_POLICY with zero source requests and no dataset rows. Only validated property listings enter the dataset.

- **URL**: https://apify.com/realestateapi/finn-property-sales-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

## FINN Property Sales Properties and Details Scraper

This Actor targets FINN.no property-sale listings. It defaults to a zero-request policy skip with an empty dataset. FINN's current user terms, rechecked on 2026-09-30, require prior written permission to copy or reproduce site material and disallow automated or systematic copying without explicit consent; commercial use also requires a separate business agreement. No such permission is recorded for this review.

The `authorizationConfirmed` input is an operator attestation only. It does not grant permission. Leave it false unless the applicable written permission and any required business agreement are actually in place. If enabled, the Actor checks the source robots policy before requesting search or listing pages. The robots URL was blocked by Chrome on 2026-09-23 and was not retried during the latest review.

The default run writes `SUCCEEDED` / `SKIPPED_POLICY` to `OUTPUT_SUMMARY` with zero requests, zero records, and `AUTHORIZATION_REQUIRED`. It writes no diagnostic or placeholder dataset row. Historical diagnostics are kept in the local archive and excluded from active dataset storage.

### Inputs and output

- `startUrls`: official FINN real-estate search or listing URLs.
- `authorizationConfirmed`: operator attestation that applicable written permission is in place; defaults to `false`.
- `maxItems`, `includeDetails`, and `maxDetailItems`: output and detail-page bounds for an actually authorized run.
- Request timeout and delay settings apply only after authorization and the robots preflight.

Authorized property records include published listing identifiers, title, type, prices, address, area, room count, images, seller label, and source URLs. The dataset accepts only validated property rows with property-specific data. A clean run is `SUCCEEDED` / `COMPLETED`, a failure with no saved property rows is `FAILED` / `FAILED`, and real property rows saved before a later failure keep the native run `SUCCEEDED` / `PARTIAL`. Failure details remain aggregate counts in the run summary.

### Offline verification

```bash
npm test
npm run validate:schema
npm run validate
```

Do not run the Actor against FINN without applicable written permission. Preserve the historical storage during offline checks.

# Actor input Schema

## `startUrls` (type: `array`):

Official FINN real-estate search pages or listing detail URLs. Requests are blocked unless authorizationConfirmed is true and the source policy preflight permits them.

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

Set true only if applicable written permission from FINN is actually in place. This checkbox is an operator attestation, not permission by itself. False performs no FINN request.

## `maxItems` (type: `integer`):

Maximum unique property listings emitted.

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

When authorized, fetch public detail pages for discovered listings up to maxDetailItems.

## `maxDetailItems` (type: `integer`):

Bound on authorized listing detail requests.

## `timeoutMs` (type: `integer`):

Timeout for each authorized public request.

## `requestDelayMs` (type: `integer`):

Polite delay before each authorized request.

## `userAgent` (type: `string`):

Transparent user-agent used only after authorization and policy preflight.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://www.finn.no/realestate/homes/search.html/"
    }
  ],
  "authorizationConfirmed": false,
  "maxItems": 25,
  "includeDetails": true,
  "maxDetailItems": 10,
  "timeoutMs": 30000,
  "requestDelayMs": 1000,
  "userAgent": "FINNPropertySalesActor/1.0 (authorized local run)"
}
```

# Actor output Schema

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

No description

## `summary` (type: `string`):

No description

# 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 = {
    "startUrls": [
        {
            "url": "https://www.finn.no/realestate/homes/search.html/"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("realestateapi/finn-property-sales-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 = { "startUrls": [{ "url": "https://www.finn.no/realestate/homes/search.html/" }] }

# Run the Actor and wait for it to finish
run = client.actor("realestateapi/finn-property-sales-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 '{
  "startUrls": [
    {
      "url": "https://www.finn.no/realestate/homes/search.html/"
    }
  ]
}' |
apify call realestateapi/finn-property-sales-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/finn-property-sales-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/JnEXTOqrJQURgxFfI/builds/ptSf5ONcPROS069Qh/openapi.json