# Figaro Immobilier Properties and Details Scraper (`realestateapi/figaro-immobilier-properties-and-details-scraper`) Actor

Authorization-gated Figaro Immobilier Actor. Runs make zero source requests by default, write no diagnostic dataset records, and report canonical native run status in OUTPUT_SUMMARY.

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

## Figaro Immobilier Properties and Details Scraper

This Actor is currently **authorization-gated**. Figaro Immobilier's current Conditions générales d’utilisation, Article 6, require prior written authorization for automated collection of site content for commercial purposes and restrict extraction or storage of database content. No applicable written authorization is recorded.

Each run writes only an `OUTPUT_SUMMARY` with `SUCCEEDED` / `SKIPPED_POLICY`, zero source requests, zero property rows, and a `WRITTEN_PERMISSION_REQUIRED` policy code. The dataset contains property listings only; no diagnostic or dummy records are pushed. The parser and normalization modules remain dormant and are not called by the Actor.

### Output

- Default dataset: empty while collection remains policy-gated.
- Key-value store: `OUTPUT_SUMMARY`, including canonical `status`, `runStatus`, and aggregate counts.
- A source failure with no saved property rows is `FAILED` / `FAILED`; real rows saved before a later failure keep native `SUCCEEDED` / `PARTIAL` status. A clean authorized run is `SUCCEEDED` / `COMPLETED`.

### Local development

```bash
npm test
npm run lint
```

Do not enable source collection based on an operator checkbox or self-attestation. Reassess the current terms and implement any authorized collection only after applicable written permission is documented.

### Runtime storage and dependencies

The runtime uses Node.js HTTPS fetch and Apify’s documented default Dataset/KVS REST APIs. It no longer includes the unused Apify SDK/Crawlee HTTP caching stack. JSON input and records are supported; the platform provides the run token and default storage IDs through environment variables. Credentials are sent only in the Authorization header to api.apify.com. Storage redirects are refused. Dataset writes are not retried after uncertain failures, to prevent duplicates; read and idempotent summary writes may retry once. Local verification uses APIFY_LOCAL_STORAGE_DIR and preserves existing dataset rows. Source permission and access requirements still apply.

# Actor input Schema

## Actor input object example

```json
{}
```

# 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/figaro-immobilier-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/figaro-immobilier-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/figaro-immobilier-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/figaro-immobilier-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/QjfPwnYaa7mYXBIRZ/builds/dm7f0GvLp7s3L3jOM/openapi.json