# Finn.no Scraper — Norwegian Property Listings | No Proxy (`bovi/finn-listings`) Actor

Scrape Finn.no Norwegian property listings. Returns price, total price, shared expenses, address, ownership type, viewing schedule, bedrooms and photos. No proxy needed. Pay per listing.

- **URL**: https://apify.com/bovi/finn-listings.md
- **Developed by:** [Vitalii Bondarev](https://apify.com/bovi) (community)
- **Categories:** Real estate, Lead generation, MCP servers
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.97 / 1,000 finn.no scraper — norwegian property listings | no proxies

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Finn.no Scraper — Norwegian Property Listings | $1.50/1K | No Proxy

For Norwegian real estate investors, buyer's agents, and Nordic PropTech platforms who need structured data from Finn.no — Norway's dominant property portal with 95%+ market share.

**$1.50 per 1,000 listings.**

Scrape **Finn.no** — Norway's #1 classifieds and real estate portal. Extracts structured listing data from any search URL: price, total cost, shared expenses, address, area, ownership type, property type, bedrooms, viewing times, and photos.

**No proxy required.** No authentication. Parses HTML listing cards with parsel — stable field extraction.

### What you get

| Field | Description |
|---|---|
| `listing_id` | Finn code (finnkode) |
| `title` | Listing title |
| `price` | Asking price in NOK |
| `price_raw` | Raw price text |
| `total_price` | Total price including fees (NOK) |
| `shared_expenses` | Monthly shared expenses (NOK) |
| `currency` | Always "NOK" |
| `area_m2` | Living area in m² |
| `ownership_type` | "Selveier", "Aksje", "Andel", etc. |
| `property_type` | "Leilighet", "Enebolig", "Rekkehus", etc. |
| `bedrooms` | Number of bedrooms |
| `address` | Street address |
| `city` | City name |
| `viewing` | Next viewing date/time |
| `url` | Full Finn ad URL |
| `image_url` | Main listing photo (960px) |
| `scraped_at` | Scrape timestamp (ISO 8601 UTC) |
| `parse_confidence` | Data quality score 0.0–1.0 |
| `warnings` | Quality issue codes |

### How it works

Finn.no renders listing cards server-side as `<article>` elements with full data in text content. The actor fetches search pages and parses each card using parsel CSS/text selectors. Pagination via `?page=N` parameter.

**~50 listings per page.** No detail-page fetches needed.

### Input

```json
{
  "searchUrl": "https://www.finn.no/realestate/homes/search.html?location=0.20061",
  "maxItems": 50
}
```

Works with any Finn.no real estate search URL — location, price, size filters all work.

### Output sample

```json
{
  "listing_id": "382814524",
  "title": "Lys og pen 3-roms leilighet med balkong og garasjeplass",
  "price": 5490000,
  "total_price": 5742500,
  "shared_expenses": 4200,
  "currency": "NOK",
  "area_m2": 72,
  "ownership_type": "Aksje",
  "property_type": "Leilighet",
  "bedrooms": 2,
  "address": "Pilestredet 75C",
  "city": "Oslo",
  "viewing": "Lørdag 15. juni kl. 13:00",
  "url": "https://www.finn.no/realestate/homes/ad.html?finnkode=382814524",
  "parse_confidence": 0.95,
  "warnings": []
}
```

### Pricing example

| Run size | Cost |
|---|---|
| 50 listings | ~$0.075 |
| 1,000 listings | ~$1.50 |
| 10,000 listings | ~$15.00 |
| + viewing schedule | +$0.50/1K |

### FAQ

**Do I need a Finn.no account or proxy?**
No account, no proxy. Works from Apify cloud IPs.

**What output formats are available?**
JSON, CSV, Excel, XML — all via Apify dataset download or API.

**Are GPS coordinates included?**
Coordinates are not available from Finn.no search pages (search page only). Use the listing `url` to open the detail page for exact map location.

**What if it returns empty results?**
Check that your `searchUrl` is a valid Finn.no real estate search URL (must include `/realestate/`). The actor logs the issue and exits cleanly with 0 results rather than crashing.

### Why this actor vs. competitors

| Feature | This actor | epctex/finn-scraper ($3/1K) | Typical Finn.no scraper |
|---|---|---|---|
| total\_price (incl. fees) | Yes | No | Rarely |
| shared\_expenses | Yes | No | No |
| ownership\_type (Selveier/Aksje) | Yes | No | No |
| Viewing schedule | Yes | No | No |
| parse\_confidence | Yes | No | No |
| Price per 1K listings | $1.50 | $3.00 | varies |

**Note: GPS coordinates not available in current version (search-page only). Use the listing URL for exact location.**

**Legal note:** `ownership_type` (Selveier vs Aksje/Andel) is a legally critical field in Norway — cooperative (Aksje/Andel) ownership affects financing options. This field is unique to Norwegian real estate and rarely available in competing scrapers.

### parse\_confidence

Every listing includes a `parse_confidence` score (0–1). Score < 0.8 means one or more critical fields are missing — check the `warnings` array before relying on those records.

### Use with AI agents (MCP)

Tag: `MCP_SERVERS`. Returns clean JSON — drop into any n8n / Make / LangChain workflow without post-processing.

```json
{
  "mcpServer": "https://mcp.apify.com/?tools=bovi/finn-listings"
}
```

### Competitive edge

- `parse_confidence` + `warnings` on every record
- total\_price + shared\_expenses (full cost transparency)
- ownership\_type (Selveier vs Aksje/Andel distinction)
- viewing date extracted
- No proxy COGS

### Pricing

Pay-Per-Event (PPE):

| Event | Price |
|---|---|
| `listing-item` (primary) | **$1.50 / 1,000 listings** |
| `viewing-schedule` (premium) | **$0.50 / 1,000 listings with viewing dates** |

Listings with an upcoming viewing date fire the `viewing-schedule` event in addition to the base charge. Buyer's agents and buyer-coordination platforms use this field to track open-house schedules.

### Integrations

Built for Norwegian real-estate investors and PropTech platforms monitoring Finn.no property prices and inventory — the JSON/dataset output drops into the tools you already run, no glue code:

- **n8n / Make / Zapier** — trigger a run or pipe every new dataset item into 500+ apps (Google Sheets, Airtable, Slack, HubSpot, your database) with no code: [n8n](https://docs.apify.com/platform/integrations/n8n), [Make](https://docs.apify.com/platform/integrations/make), [Zapier](https://docs.apify.com/platform/integrations/zapier).
- **Webhooks** — fire your own endpoint the moment a run finishes, to push results straight into your pipeline ([docs](https://docs.apify.com/platform/integrations/webhooks)).
- **MCP server** — expose this actor as a tool to Claude, Cursor, or any [MCP client](https://mcp.apify.com) so an AI agent can pull this data mid-conversation ([guide](https://blog.apify.com/how-to-use-mcp/)).
- **API & SDKs** — fetch the dataset as JSON, CSV, or Excel through the Apify REST API or the Python / JS SDKs.

See all [Apify integrations](https://apify.com/integrations).

# Actor input Schema

## `searchUrl` (type: `string`):

Full Finn.no real estate search URL. Example: https://www.finn.no/realestate/homes/search.html?location=0.20061 (Oslo) or any filtered URL from the Finn search page.

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

Maximum number of listings to return (0 = no limit, scrapes all pages). Default 50.

## `proxyConfiguration` (type: `object`):

Optional Apify proxy. Finn.no works without proxy from Apify cloud IPs. Only needed if you observe 403 errors.

## Actor input object example

```json
{
  "searchUrl": "https://www.finn.no/realestate/homes/search.html?location=0.20061",
  "maxItems": 50,
  "proxyConfiguration": {}
}
```

# Actor output Schema

## `results` (type: `string`):

Dataset containing Finn Listings records (title, price, total\_price, area\_m2, bedrooms, property\_type, ownership\_type, address, city, url, scraped\_at, parse\_confidence).

# 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 = {
    "searchUrl": "https://www.finn.no/realestate/homes/search.html?location=0.20061",
    "maxItems": 50,
    "proxyConfiguration": {}
};

// Run the Actor and wait for it to finish
const run = await client.actor("bovi/finn-listings").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 = {
    "searchUrl": "https://www.finn.no/realestate/homes/search.html?location=0.20061",
    "maxItems": 50,
    "proxyConfiguration": {},
}

# Run the Actor and wait for it to finish
run = client.actor("bovi/finn-listings").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 '{
  "searchUrl": "https://www.finn.no/realestate/homes/search.html?location=0.20061",
  "maxItems": 50,
  "proxyConfiguration": {}
}' |
apify call bovi/finn-listings --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,bovi/finn-listings"
        }
    }
}

```

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/3UXYVMks2zPVmodu4/builds/04BCdyaEfP9tJzCdS/openapi.json