# French Properties and Details Scraper (`realestateapi/french-properties-and-details-scraper`) Actor

Authorization-gated French-Property.com property scraper. It reports native run status accurately and writes only validated property listings to the dataset.

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

## French Properties and Details Scraper

CSV rank: **4206**. Store listing: [dadhalfdev/french-property-scraper](https://apify.com/dadhalfdev/french-property-scraper).

When applicable written authorization is in place, this Actor can extract structured French-Property.com listings. It supports sale and rental search pages, supplied search/detail URLs, price and bedroom filters, location and keyword filters, property references, and optional detail-page enrichment. Collection is disabled by default because the site's current Terms restrict copying and storage of listing content for public or commercial use.

### Input

Use `startUrls` for a saved search or an individual listing. A supplied URL is authoritative; structured filters are added only when the Actor builds its default search URL. Examples:

```json
{
  "startUrls": [
    { "url": "https://www.french-property.com/properties-for-sale?property_types_all=house" }
  ],
  "maxItems": 25,
  "maxPages": 1,
  "includeDetails": true
}
```

Without a URL, the Actor builds an official search URL under `/properties-for-sale` or `/properties-to-rent` using the selected listing type, location, keywords, price, bedroom, land-size, and property-type filters. Habitable-area and all filters are also enforced locally against normalized records.

### Output

Each dataset record is a validated property listing with the stable advertisement reference, title, sale/rent type, property type, asking price and currency, habitable and land area, bedrooms, bathrooms, location, region, department, commune, agency information, photos, description, highlights, features, coordinates, and energy data when exposed. Invalid or diagnostic records are never written to the dataset. `OUTPUT_SUMMARY` contains canonical run status and aggregate counters, without raw error details.

Native run status follows saved property rows: a clean run is `SUCCEEDED` / `COMPLETED`; a run that saves real property rows and later encounters failures is `SUCCEEDED` / `PARTIAL`; a run with failures and no saved property rows is `FAILED` / `FAILED`. A valid empty result is successful. The default authorization gate reports `SUCCEEDED` / `SKIPPED_POLICY` and makes no source requests.

The parser handles the site's server-rendered listing cards, JSON-LD `Accommodation`/`Product` data, and detail-page HTML. It does not require a browser or dump raw page markup into the dataset.

### Access behavior

The `authorizationConfirmed` input defaults to false. It is an operator attestation only and does not grant permission; enable it only when applicable written authorization is documented. Requests are limited to HTTPS French-Property.com URLs, redirects are not followed, and the Actor does not use proxies, log in, bypass challenges, or defeat access controls. A source failure with no saved property row produces a failed native run and an aggregate count in `OUTPUT_SUMMARY`, never a diagnostic dataset record.

### Local verification

```bash
npm install
npm test
npm run lint
apify validate-schema
```

Do not run against French-Property.com without documented applicable written authorization. See [BROWSER_REVIEW.md](BROWSER_REVIEW.md).

# Actor input Schema

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

Enable source requests only when documented written authorization covers automated access and the intended collection. This attestation does not grant permission.

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

Public search URLs such as /properties-for-sale?property_types_all=house or individual /sale-property/ pages.

## `location` (type: `string`):

Location text sent as the site's search parameter when no start URL is supplied, and used as a client-side filter.

## `searchKeyword` (type: `string`):

Keyword sent as the site's keyword search parameter when no start URL is supplied, and used as a client-side filter.

## `listingType` (type: `string`):

Choose sale or rent when generating a search URL. A supplied start URL remains authoritative.

## `propertyType` (type: `string`):

Optional property type such as house, apartment, business, or land.

## `reference` (type: `string`):

Optional French-Property.com advertisement reference such as IFPC46914.

## `minPrice` (type: `number`):

Only emit records with a numeric asking price at or above this value.

## `maxPrice` (type: `number`):

Only emit records with a numeric asking price at or below this value.

## `minBedrooms` (type: `number`):

Only emit records with at least this many bedrooms.

## `maxBedrooms` (type: `number`):

Only emit records with at most this many bedrooms.

## `minArea` (type: `number`):

Only emit records with at least this many square metres of habitable area.

## `maxArea` (type: `number`):

Only emit records with at most this many square metres of habitable area.

## `minLandArea` (type: `number`):

Only emit records with at least this many square metres of land.

## `maxLandArea` (type: `number`):

Only emit records with at most this many square metres of land.

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

Maximum unique property records to emit after filters.

## `maxPages` (type: `integer`):

Maximum pages per supplied search URL.

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

Fetch each selected public detail page to enrich descriptions, features, DPE, photos, and agency data.

## `delayMs` (type: `integer`):

Delay between public French-Property.com requests.

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

Maximum time allowed for each public request.

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

Optional transparent HTTP user-agent string.

## `acceptLanguage` (type: `string`):

Optional language preference for the public HTTP request.

## Actor input object example

```json
{
  "authorizationConfirmed": false,
  "startUrls": [],
  "listingType": "sale",
  "maxItems": 25,
  "maxPages": 1,
  "includeDetails": true,
  "delayMs": 250,
  "timeoutMs": 30000,
  "acceptLanguage": "en-US,en;q=0.8"
}
```

# Actor output Schema

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

No description

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

// Run the Actor and wait for it to finish
const run = await client.actor("realestateapi/french-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/french-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/french-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/french-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/b7f5ObbHQP0CUw7vi/builds/ZDn5gbCgcvYBSTVnY/openapi.json