# Bienici Ppr Properties and Details Scraper (`realestateapi/bienici-ppr-properties-and-details-scraper`) Actor

Permission-gated Bien’ici listing Actor. Default runs report SUCCEEDED / SKIPPED_POLICY with zero requests and no dataset rows. Source failures without listings report FAILED; partial saved listings remain SUCCEEDED.

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

## Bienici Ppr Properties and Details Scraper

This Actor is the rank 550 implementation for [silentflow/bienici-scraper-ppr](https://apify.com/silentflow/bienici-scraper-ppr). It reads the public Bien’ici JSON listing endpoint and, optionally, the matching public detail endpoint.

Bien’ici’s current Terms restrict unauthorized automated collection and reuse. This Actor defaults to zero source requests and requires the operator to attest that current written permission covers the collection and intended reuse. The checkbox does not grant permission. The Actor accepts only the official HTTPS listing endpoint and does not use alternate transports, proxies, or access-control workarounds. Do not run it without the required written permission.

It returns listing identity, title, description, transaction/property type, price, surface area, city, postal code, publication dates, public photo URLs, and public agency contact fields when Bien’ici exposes them. It does not invent DPE, email, address, or contact values, and it does not bypass access controls.

Default source: `https://www.bienici.com/realEstateAds.json`.

Example input:

```json
{
  "authorizationConfirmed": true,
  "maxItems": 10,
  "transactionType": "buy",
  "propertyType": "flat",
  "city": "Paris",
  "fetchDetails": true
}
```

Use that input only when written permission is already in place. By default, the Actor makes zero source requests, finishes with `status: SUCCEEDED` and `runStatus: SKIPPED_POLICY`, and writes no dataset rows. The authorization checkbox is an operator attestation, not a permission grant.

The default dataset contains Bien’ici property listing rows only. Failed requests and run details are reported in the `OUTPUT_SUMMARY` key-value-store record; diagnostic and placeholder rows are never added to the dataset. A source failure before any listing is saved reports `status: FAILED` and `runStatus: FAILED`. If listing rows were saved before detail requests failed, the run reports `status: SUCCEEDED` and `runStatus: PARTIAL`. A valid empty response reports `status: SUCCEEDED` and `runStatus: COMPLETED`.

Each listing includes `generatedBy: "codex-apify-actor-development"`, `inventoryRank: 550`, source URLs, and `scrapedAt`. The local August 31, 2026 run summary records one historical listing, but the listing row is not present in the current local storage snapshot and was previously assessed as stale and unverified. It is not evidence of current source coverage.

### Record provenance

New records identify this implementation in `actorSlug` and omit the original third-party Store URL from producer fields. Historical records retain their original inventory labels and are preserved. Collection remains subject to the existing source permission and access restrictions.

# Actor input Schema

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

Enable only when written permission covers automated collection and intended reuse. This checkbox is an operator attestation, not a permission grant.

## `sourceUrl` (type: `string`):

Official Bien’ici endpoint. Only the HTTPS www.bienici.com/realEstateAds.json path is accepted, and no request is made without written permission.

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

Maximum listings to store.

## `transactionType` (type: `string`):

Filter by purchase or rental listings.

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

Filter by the public Bien’ici property type.

## `city` (type: `string`):

Optional case-insensitive city filter.

## `postalCode` (type: `string`):

Optional postal-code prefix filter.

## `fetchDetails` (type: `boolean`):

Fetch the official public detail JSON for each selected listing to include public agency contact fields.

## Actor input object example

```json
{
  "authorizationConfirmed": false,
  "sourceUrl": "https://www.bienici.com/realEstateAds.json",
  "maxItems": 10,
  "transactionType": "all",
  "propertyType": "all",
  "fetchDetails": true
}
```

# Actor output Schema

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

Default dataset contains property listings only.

## `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/bienici-ppr-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/bienici-ppr-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/bienici-ppr-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/bienici-ppr-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/I5iRUzhchcRv3EXTR/builds/RLle1lFX5sICXYddY/openapi.json