# FINN Real Estate Properties and Details Scraper (`realestateapi/finn-realestate-properties-and-details-scraper`) Actor

FINN real-estate Actor. Automated source requests are disabled by default because the Terms require written permission for copying and automated or systematic collection.

- **URL**: https://apify.com/realestateapi/finn-realestate-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 Real Estate Properties and Details Scraper

This Actor was designed to extract public property cards from FINN.no real-estate search pages and enrich selected listings with public detail-page fields.

Automated requests are disabled by default. FINN's user terms, section 6, require prior written permission for copying and prohibit automated services or systematic/regular copying without explicit written consent. Section 7 requires a separate business agreement for commercial use. Set `authorizationConfirmed` to true only when your written authorization covers the planned automated access and content use. With the default false value, the Actor makes zero source requests and reports `SUCCEEDED/SKIPPED_POLICY` in its OUTPUT summary without adding a diagnostic to the dataset.

When authorized access is confirmed, the Actor accepts only HTTPS FINN real-estate URLs on `finn.no` or `www.finn.no`. It makes direct requests only, refuses redirects, and stops on access blocks or security challenges without using an alternate transport. Only validated property listings are written to the dataset; failures are kept in OUTPUT. A failed run with no saved property listings reports `FAILED/FAILED` and exits nonzero. If valid property listings were saved before a later failure, it reports `SUCCEEDED/PARTIAL` and exits successfully.

Inputs are `urls`, `authorizationConfirmed`, `maxListings`, `includeDetails`, and `timeoutSecs`. Existing storage remains historical and should not be treated as a fresh source verification.

The local dataset contains one historical record from August 31, 2026. The current schema declares 36 possible top-level fields; the saved row has 19 nonempty fields and passes the local schema and summary checks. It falls in the medium (15–27 fields) band used by the local dataset review. It does not demonstrate current extraction. No fields were guessed or added because current FINN terms require prior written consent for copying and automated or systematic collection, and commercial use requires a Partner Agreement.

#### Dependency security

The locked dependency graph overrides basic-ftp with the patched 6.2.1 release. The SDK’s unpatched HTTP cache policy is replaced with the readable local vendor/noncaching-http-policy adapter, which refuses cache reads and writes and forces fresh network responses. This is an explicit removal of caching, not a claimed upstream security patch. Source transports, permission gates and request limits are unchanged. npm run test:dependencies checks cross-user cache isolation, imported stale policy rejection, FTP integration methods and adversarial listing parsing. Cloud builds run npm audit --omit=dev --audit-level=low against the installed production graph.

# Actor input Schema

## `urls` (type: `array`):

Public FINN.no real-estate search pages with server-rendered listing cards.

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

Enable only when applicable written permission is actually in place. This checkbox is an operator attestation, not permission by itself. Disabled by default; false makes zero source requests.

## `maxListings` (type: `integer`):

Maximum public property records to emit across all requested pages.

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

Fetch each public listing page for description, energy, agent, and additional property details.

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

Per-request timeout in seconds for search and detail pages.

## Actor input object example

```json
{
  "urls": [
    "https://www.finn.no/realestate/homes/search.html"
  ],
  "authorizationConfirmed": false,
  "maxListings": 25,
  "includeDetails": true,
  "timeoutSecs": 30
}
```

# Actor output Schema

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

Only source-backed FINN property listings. Run status and failures are stored in OUTPUT; diagnostics are never written to the dataset.

## `output` (type: `string`):

Fixed OUTPUT key containing run counts and bounded failures.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("realestateapi/finn-realestate-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("realestateapi/finn-realestate-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 '{}' |
apify call realestateapi/finn-realestate-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-realestate-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/cCDHILfuFP6nNAd1Y/builds/KVpXKoRjIjQmPh1tt/openapi.json