# France Property Sale Prices Scraper (DVF Open Data) (`soogrow_berries/france-property-sales-dvf-scraper`) Actor

Recorded property sales in France from the government's DVF open data: date, price, address, property type, built and land area, rooms, price per m² and GPS position, by town. Newest sales first.

- **URL**: https://apify.com/soogrow_berries/france-property-sales-dvf-scraper.md
- **Developed by:** [Matt](https://apify.com/soogrow_berries) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.80 / 1,000 sale saveds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## France Property Sale Prices Scraper (DVF Open Data)

Compare recorded sale prices in chosen French towns using the government's DVF open data. Get up to Maximum results sales per run, one row per sale, with location, date, price and property details.

### What does this Actor do?

- **You give:** French towns by name or INSEE code (such as `Bordeaux` or `33063`), or postal codes (such as `75011`). Optional: years, property types and a price range.
- **You get:** sale ID, date, sale type, price in euros, main property type (house, flat, commercial premises, outbuilding, land), number of dwellings, built area, rooms, Carrez area, land area, price per m², lots, address, postal code, town, INSEE and department codes, cadastral parcels and GPS position.
- **How many:** up to Maximum results matching sales across the selected town files (20 by default), with newest sales first within each file. The historical Bordeaux 2025 file held about 6,400 sales; this is not a current coverage count. Paris, Lyon and Marseille cover all their arrondissements.
- **Speed and limits:** in local test runs on 2026-10-08 (UTC), a run of 20 sales took 5 s, and 200 sales from three town files took 5 s. Each town file holds one year of sales (Bordeaux 2025: about 6,400); files are read one at a time, up to 30 a minute.
- **Price:** $1.80 per 1,000 sales (20 sales = $0.036). No start fee. No proxy needed.
- **Not included:** buyer and seller names (DVF holds none), asking prices, listings, and sales in Alsace, Moselle and Mayotte, which DVF does not cover.

### Input

| Field | What it does | Default |
|---|---|---|
| Towns (communes) | Town names or INSEE codes; `Saint-Denis 974` picks the town in department 974 | `Bordeaux` |
| Postal codes | Each adds the towns that use it | None |
| Years | Years of sales to read | The newest year published |
| Property types | Keep only Maison, Appartement, Local, Dépendance or Terrain | All |
| Minimum price / Maximum price (EUR) | Keep only sales in this range | None |
| DVF town files | Read these town files from [data.gouv.fr](https://files.data.gouv.fr/geo-dvf/latest/csv/) instead | None |
| Maximum results | Stop after this many sales | 20 |
| Only new results | Skip sales an earlier run with the same input already saved; they are not saved or charged | Off |
| Proxy configuration | Optional; the Actor runs without one | No proxy |

Sales your filters leave out are not charged.

Example: flats sold in Lyon and Annecy in 2024 and 2025 for 150,000 to 400,000 euros.

```json
{
    "communes": ["Lyon", "Annecy"],
    "years": ["2025", "2024"],
    "propertyTypes": ["Appartement"],
    "minPriceEur": 150000,
    "maxPriceEur": 400000,
    "maxItems": 5000
}
```

### Output

One record per sale. Download it as JSON, CSV, Excel or HTML from the Output tab, or read it through the Apify API.

```json
{
    "saleId": "2025-418413",
    "date": "2025-12-31",
    "saleType": "Vente",
    "priceEur": 223000,
    "propertyType": "Appartement",
    "dwellingCount": 1,
    "builtAreaM2": 45,
    "rooms": 2,
    "carrezAreaM2": 46.47,
    "pricePerM2Eur": 4956,
    "lotCount": 2,
    "postalCode": "33100",
    "communeName": "Bordeaux",
    "inseeCode": "33063",
    "departmentCode": "33",
    "sourceUrl": "https://files.data.gouv.fr/geo-dvf/latest/csv/2025/communes/33/33063.csv",
    "scrapedAt": "2026-10-08T03:23:30.070Z"
}
```

A real record from a local test run on 2026-10-08 (UTC), shortened to 17 of its 22 fields. Not shown: `landAreaM2`, `address`, `parcelIds`, `longitude`, `latitude`.

`pricePerM2Eur` is the price divided by the built area of all premises sold, outbuildings included. A sale of several premises or parcels is one record; `dwellingCount`, `lotCount` and `parcelIds` show what it held.

The run also saves an `OUTCOME` record in its key-value store, and the same sentence as the run's status message: `COMPLETE` (no more sales in your towns and years), `MAX_RESULTS` (stopped at Maximum results), `SPENDING_LIMIT`, `PARTIAL` (some files failed to load), `NO_NEW_RESULTS` (Only new results is on and nothing is new), `NO_MATCHING_RESULTS` (your filters left nothing) or `FAILED`. Only `FAILED` ends the run as failed.

### Pricing

You pay $1.80 per 1,000 sales, only for sales saved. No start fee. Platform costs are included in the price.
Example: the default maximum of 20 saved sales costs $0.036 (20 × $0.0018). Fewer saved sales cost proportionally less.

- Sales your filters leave out are not charged.
- A sale found in two of your towns is saved and charged once per run.
- A run that cannot read anything stops with a reason and costs nothing.
- A sale seen again in a later run is saved and charged again, unless "Only new results" is on.
- Set "Maximum results" or a spending limit to cap the cost.

### Notes

- This Actor is an independent tool. It is not affiliated with, endorsed by or sponsored by the French government, the DGFiP, Etalab or data.gouv.fr.
- It reads the DVF files that Etalab publishes on data.gouv.fr under the Licence Ouverte 2.0, and looks up town names in the government's public geo API. No key is needed. When reusing results, attribute the DVF source (DGFiP / Etalab) and identify the source file and date; each row includes `sourceUrl` and `scrapedAt` to support that attribution.
- DVF's own rules (decree 2018-1350) bar re-identifying the people involved in a sale and having the data indexed by search engines. Do not re-identify people or allow search engines to index the resulting property-sale data.
- DVF is updated twice a year, about six months after the sales.
- Found a problem? Open an issue on the Issues tab and include the run link.

# Actor input Schema

## `communes` (type: `array`):

Town names or INSEE codes, such as "Bordeaux", "33063" or "Saint-Denis 974" (a department code after the name picks between towns of the same name; without it the largest is used). Paris, Lyon and Marseille cover all their arrondissements.

## `postalCodes` (type: `array`):

Optional. Postal codes, such as "33000" or "75011"; each adds the towns that use it.

## `years` (type: `array`):

Optional. Years of sales to read, such as "2025" or "2024". Default: the newest year published. DVF is published twice a year, with a delay of about six months.

## `propertyTypes` (type: `array`):

Optional. Keep only these main property types: Maison (house), Appartement (flat), Local (shop, office or industrial premises), Dépendance (garage, cellar, parking), Terrain (land only). Sales left out are not charged.

## `minPriceEur` (type: `integer`):

Optional. Keep only sales at or above this price. Sales left out are not charged.

## `maxPriceEur` (type: `integer`):

Optional. Keep only sales at or below this price. Sales left out are not charged.

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

Optional. DVF files by town and year from data.gouv.fr, such as https://files.data.gouv.fr/geo-dvf/latest/csv/2025/communes/33/33063.csv.

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

Stop after saving this many sales. You pay per result, so this also caps the cost.

## `onlyNew` (type: `boolean`):

Skip sales that an earlier run with the same towns and filters already saved. Skipped sales are not saved and not charged. The list of saved IDs is kept in a key-value store named "france-property-sales-dvf-scraper-seen" in your Apify account; delete it to start over.

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

Optional. The Actor runs without a proxy.

## Actor input object example

```json
{
  "communes": [
    "Bordeaux"
  ],
  "maxItems": 20,
  "onlyNew": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `sales` (type: `string`):

Saved sales in the default dataset.

## `runSummary` (type: `string`):

Run outcome record in the default key-value store.

# 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 = {
    "communes": [
        "Bordeaux"
    ],
    "maxItems": 20,
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("soogrow_berries/france-property-sales-dvf-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 = {
    "communes": ["Bordeaux"],
    "maxItems": 20,
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("soogrow_berries/france-property-sales-dvf-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 '{
  "communes": [
    "Bordeaux"
  ],
  "maxItems": 20,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call soogrow_berries/france-property-sales-dvf-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,soogrow_berries/france-property-sales-dvf-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/1ikat4khOUQLGgekh/builds/cNJ2FrYOrJsmsYTpP/openapi.json