# DPE F/G Leads - New Passoires Thermiques Since Last Run (`that_red_bird/france-dpe-fg-new-leads`) Actor

RGE renovation firms: get only the NEW F and G energy diagnoses (DPE) since your last run, by departement, with surface, year, heating and energy cost. Adds legal entities registered at the address (SIRENE), never private individuals. France only.

- **URL**: https://apify.com/that_red_bird/france-dpe-fg-new-leads.md
- **Developed by:** [mohamed alaya](https://apify.com/that_red_bird) (community)
- **Categories:** Lead generation, Business, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / 1,000 dpe leads

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

## DPE F/G Leads - New Passoires Thermiques Since Last Run (France)

Returns only the **new F and G energy diagnoses (DPE)** published since your last run, by departement, from the official ADEME open data. For RGE renovation firms, insulation and heating installers, and property hunters. **France only.**

Each row is an address-level diagnosis (label, surface, year, main energy, yearly energy cost). Optionally it adds the **legal entities registered at that address** from SIRENE (companies, SCI, syndicats de copropriete).

### Quick start - three copy-paste inputs

Demo (empty input works, Paris, last 7 days of data):

```json
{}
```

Lyon and Marseille, G labels in whole buildings only:

```json
{
  "departments": ["69", "13"],
  "labels": ["G"],
  "buildingTypes": ["immeuble"],
  "maxResults": 300,
  "stateStoreName": "my-renovation-firm-dpe"
}
```

First run going back 30 days, no company lookup (cheaper and faster):

```json
{ "departments": ["33", "31"], "sinceDays": 30, "joinCompanies": false, "maxResults": 500 }
```

Schedule it daily or weekly with the same `stateStoreName`: each run continues exactly where the last one stopped.

### Input guide

| Field | Meaning |
|---|---|
| `departments` | Departement codes (75, 69, 2A ...). |
| `labels` | E, F and/or G. Default F and G. |
| `buildingTypes` | appartement, maison, immeuble. Empty = all. |
| `sinceDays` | First-run window, counted back from the newest diagnosis in the data (ADEME publishes with a few days of lag). |
| `maxResults` | Oldest first, up to this many per run; the next run resumes after the last one. Also your spending cap. |
| `joinCompanies` | Add legal entities registered at the address. |
| `stateStoreName` | Memory store. Progress is kept per combination of departments, labels and building types. |

### Output

| Field | Meaning |
|---|---|
| `dpeNumber`, `label`, `gesLabel` | ADEME DPE number, energy class and GHG class |
| `address`, `postcode`, `city`, `department` | Geocoded (BAN) address |
| `buildingType`, `dwellings`, `surfaceM2`, `constructionYear` | Building facts |
| `mainEnergy`, `annualEnergyCostEur`, `primaryEnergyKwhM2` | Energy facts from the diagnosis |
| `receivedOn`, `issuedOn` | Dates in the ADEME database |
| `companiesAtAddress` | `[ {siren, name, legalFormCode, activityCode, isSyndicatCopropriete, relation} ]` |

Sample row (shortened):

```json
{"type":"dpe-lead","dpeNumber":"2675E2467603X","label":"F","address":"306 Rue de Vaugirard 75015 Paris","buildingType":"immeuble","dwellings":12,"receivedOn":"2026-09-28","companiesAtAddress":[{"siren":"039011044","name":"SYND.COPR. DU 306 RUE DE VAUGIRARD","legalFormCode":"9110","isSyndicatCopropriete":true,"relation":"registered-at-address"}]}
```

### Use it with

- DPE rows with a `isSyndicatCopropriete` company are building-level decision makers for collective renovation: send them to your CRM.
- Pass company names to the **Google Maps Emails** or **company enrichment** Actors to find a public contact.

### GDPR and data limits

- The ADEME DPE data contains **no owner or occupant names**. An address can still point to a household, so use it under your own legitimate-interest assessment and respect opposition requests (Bloctel / right to object) and the CNIL rules on prospecting.
- The company lookup lists **legal entities only**. Sole traders (entrepreneurs individuels), private individuals and non-diffusible SIRENE entries are never listed. If no legal entity is registered at the address you get an empty list, never a personal name.
- A company registered at an address is **not proof that it owns the building** (it may be a tenant, a domiciliation or a syndic). The Actor says `registered-at-address` for that reason. The DVF land-sale join is not included.

### FAQ

**How fresh is it?** ADEME updates daily with a lag of a few days.

**Why is a run empty?** No new diagnoses for your filters since the last run. You still get a summary row.

### Price

**$0.002 per diagnosis delivered.** 100 diagnoses cost $0.20.

# Actor input Schema

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

French departement codes, for example 75, 69, 13, 33, 2A. Each run reads only diagnoses received after the previous run for this exact combination of filters.

## `labels` (type: `array`):

Which DPE energy classes to return. F and G are the passoires thermiques (banned from rental in stages by law). Add E to widen.

## `buildingTypes` (type: `array`):

Keep only these types: appartement, maison, immeuble. Leave empty for all types. Immeuble (whole building) diagnoses are the most useful for renovation firms.

## `sinceDays` (type: `integer`):

On the very first run there is no memory, so this many days back from today are read. Later runs continue from where the previous run stopped.

## `maxResults` (type: `integer`):

Oldest-first up to this number; the next run continues after the last one delivered, so nothing is skipped. You are charged per diagnosis delivered, so this is also your spending cap.

## `joinCompanies` (type: `boolean`):

Look up each address in SIRENE (recherche-entreprises.api.gouv.fr) and list legal entities registered at it. This is the registered address, not proof of ownership. Sole traders and private individuals are never listed.

## `stateStoreName` (type: `string`):

Named key-value store that remembers how far each filter combination has been read. Use the same name on every scheduled run and a different name per client. Empty = every run starts from the first-run window.

## Actor input object example

```json
{
  "departments": [
    "75"
  ],
  "labels": [
    "F",
    "G"
  ],
  "buildingTypes": [],
  "sinceDays": 7,
  "maxResults": 100,
  "joinCompanies": true,
  "stateStoreName": "france-dpe-fg-state"
}
```

# Actor output Schema

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

No description

## `downloadCsv` (type: `string`):

No description

## `summary` (type: `string`):

No description

## `count` (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("that_red_bird/france-dpe-fg-new-leads").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("that_red_bird/france-dpe-fg-new-leads").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 that_red_bird/france-dpe-fg-new-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,that_red_bird/france-dpe-fg-new-leads"
        }
    }
}
```

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/py1QPeXTMZhDMqMa4/builds/1aHTzVgUPxzcMBzjt/openapi.json