# French Property Transactions (DVF) - Official Open Data (`egarian/dvf-france-property-transactions`) Actor

Access official French property transaction data (DVF) from data.gouv.fr. Search real sales prices, filter by location, date, property type, price range. No scraping - uses official government open data.

- **URL**: https://apify.com/egarian/dvf-france-property-transactions.md
- **Developed by:** [Loïc Rossi](https://apify.com/egarian) (community)
- **Categories:** Real estate, Business
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 property transactions

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

## French Property Transactions (DVF) — Official Open Data

Every **real estate sale recorded in France** since 2014, from the official DVF open data (Demandes de Valeurs Foncières, `data.gouv.fr`). Actual notarized transaction prices — the reference dataset for French property market analysis.

### What it does

- Downloads the official DVF files per **department** and **year**, then filters and normalizes them
- Filters: date range, **property type** (house, apartment, dependency, commercial, land), **price range**, **surface range**
- Computes **price per m²**, keeps mutation type, rooms, land surface
- Optional GPS coordinates (`includeCoordinates`) for mapping
- One clean record per transaction — ready for analytics, valuation or market-monitoring use cases

### Input example

```json
{
  "departments": ["75", "69"],
  "years": ["2023", "2024"],
  "propertyTypes": ["apartment"],
  "priceMin": 100000,
  "priceMax": 2000000,
  "surfaceMin": 20,
  "includeCoordinates": true,
  "maxRecords": 5000
}
```

Main input fields: `departments` (empty = all 101), `years` (from 2014), `dateFrom`, `dateTo`, `propertyTypes`, `priceMin`/`priceMax`, `surfaceMin`/`surfaceMax`, `includeCoordinates`, `updateExisting`, `maxRecords`.

### Output example

```json
{
  "source": "DVF",
  "sourceId": "2024-75102-000123",
  "date": "2024-06-14",
  "year": 2024,
  "price": 850000,
  "pricePerM2": 9444,
  "propertyType": "apartment",
  "surface": 90,
  "rooms": 4,
  "landSurface": null,
  "location": { "postalCode": "75102", "commune": "Paris", "department": "75" },
  "mutationType": "Vente",
  "coordinates": { "longitude": 2.3488, "latitude": 48.8534 }
}
```

### Data source

- **DVF — Demandes de Valeurs Foncières** — official French government open data on real estate transactions (published by DGFiP / Etalab)

### Notes

- **No API key required** — fully open data.
- Large departments/years can be heavy: use `maxRecords`, specific departments, and the cache-aware `updateExisting` option; cached downloads are reused across runs in the same Actor storage.

# Actor input Schema

## `departments` (type: `array`):

French department codes to fetch. Empty = all 101 departments. Examples: \['75'] for Paris, \['69'] for Rhône, \['13'] for Bouches-du-Rhône

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

Years of transaction data to download. DVF data available from 2014 onwards.

## `maxRecords` (type: `integer`):

Safety limit on total output records. Increase for full exports.

## `dateFrom` (type: `string`):

Filter transactions from this date onwards

## `dateTo` (type: `string`):

Filter transactions up to this date

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

Filter by property type

## `priceMin` (type: `integer`):

Minimum transaction price in euros

## `priceMax` (type: `integer`):

Maximum transaction price in euros

## `surfaceMin` (type: `number`):

Minimum built surface in square meters

## `surfaceMax` (type: `number`):

Maximum built surface in square meters

## `includeCoordinates` (type: `boolean`):

Include longitude/latitude for mapping

## `updateExisting` (type: `boolean`):

Ignore cache and re-download all files

## Actor input object example

```json
{
  "departments": [
    "75"
  ],
  "years": [
    "2024"
  ],
  "maxRecords": 100000,
  "dateFrom": "",
  "dateTo": "",
  "propertyTypes": [],
  "priceMin": 0,
  "priceMax": 10000000,
  "surfaceMin": 0,
  "surfaceMax": 10000,
  "includeCoordinates": true,
  "updateExisting": false
}
```

# Actor output Schema

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

Real French property sales from the official DVF (Demandes de Valeurs Foncières) open data. One item per transaction.

# 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("egarian/dvf-france-property-transactions").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("egarian/dvf-france-property-transactions").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 egarian/dvf-france-property-transactions --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,egarian/dvf-france-property-transactions"
        }
    }
}
```

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/5dQUEVdAt9I4yLCma/builds/pwRKeoteb4p6xxiQU/openapi.json