# French BODACC Company Notices - creations, sales, insolvency (`edgarfinance/france-bodacc-notices`) Actor

Official French BODACC notices about companies: creations, sales, changes, insolvency. Filter by SIREN, department, date. No personal data. $1.50 per 1,000.

- **URL**: https://apify.com/edgarfinance/france-bodacc-notices.md
- **Developed by:** [Edgar Finance](https://apify.com/edgarfinance) (community)
- **Features:** Limited permissions
- **Stats:** 1 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 company notice founds

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 BODACC Company Notices: creations, sales, modifications, insolvency

Get official French legal notices about companies from the **BODACC** (Bulletin officiel des annonces civiles et commerciales): new companies, sales and transfers of businesses, mergers, changes of officers or address, deregistrations, insolvency proceedings (safeguard, receivership, liquidation) and annual accounts filings. Filter by **SIREN**, **department**, **notice family** and **publication date**, and get one clean row per notice.

The data comes from the **official open data API of the DILA** (Direction de l'information légale et administrative, the French government publisher of the BODACC). No scraping, no login, no proxy, no API key.

**Privacy first: only companies, never people.** Notices about sole traders and other natural persons are dropped entirely, and no name of a person (officer, liquidator, previous owner, private individual) is ever written to your dataset. See "Privacy rule" below.

### Why this Actor

- **Official and complete source**: the same notices as bodacc.fr, from 2008 to the latest bulletin.
- **Four ways to search**: by SIREN (watch a list of companies), by department, by notice family, by publication period. Combine them freely.
- **No 10,000 results ceiling**: the public API cannot page beyond 10,000 records per query; the Actor cuts big periods into smaller ones automatically.
- **Clean, stable output**: every row has the same 39 fields in the same order (company, legal form, capital, registered office city, postcode and department, court, act category, judgment, accounts filing...). Easy to load into Excel, Google Sheets, a CRM or a database.
- **GDPR friendly by design**: built for B2B use (KYB, credit risk, market watch) without storing personal data.
- **Pay only for what you get**: you are charged per company notice returned. Notices left out by the privacy rule are free.

### Use cases

- **Credit risk and supplier monitoring**: watch a list of SIREN numbers for insolvency proceedings, deregistrations, dissolutions or changes of registered office.
- **M\&A and business transfer leads**: sales of businesses (fonds de commerce) and mergers in your region.
- **Market intelligence**: new companies by department and legal form, every week.
- **Distressed assets**: new receiverships and liquidations by department.

### Input

All filters are optional. With no filter, the Actor returns the company notices of the last 30 days for all of France (creations, sales, modifications, deregistrations, insolvency proceedings).

| Field | Type | Description |
|---|---|---|
| `sirens` | list of strings | SIREN numbers (9 digits; a SIRET is reduced to its SIREN). Up to 1,000. When set and no start date is given, the whole history since 2008 is searched. |
| `departments` | list of strings | Department codes of the commercial court registry: 01 to 95, 2A, 2B, 971 to 976. |
| `noticeFamilies` | list | `creation`, `immatriculation`, `modification`, `vente`, `radiation`, `collective`, `conciliation`, `dpc` (accounts filings), `divers`. Default: creation, vente, modification, radiation, collective. |
| `noticeTypes` | list | `initial`, `correction`, `cancellation`. Default: all. |
| `dateFrom`, `dateTo` | dates YYYY-MM-DD | Publication period. Default: last 30 days (or since 2008 with SIREN numbers). |
| `maxResults` | integer, 1 to 100,000, default 1,000 | The run stops after this many company notices. |
| `maxRequestsPerSecond` | integer, 1 to 10, default 5 | Politeness limit towards the public API. |

Example: insolvency proceedings in Paris and Hauts-de-Seine in October 2026:

```json
{
    "departments": ["75", "92"],
    "noticeFamilies": ["collective"],
    "dateFrom": "2026-10-01",
    "dateTo": "2026-10-31",
    "maxResults": 500
}
```

Example: watch two companies over their whole history:

```json
{
    "sirens": ["552032534", "542051180"],
    "noticeFamilies": ["modification", "vente", "radiation", "collective", "dpc"]
}
```

### Output

One row per notice, newest first. Example (a creation):

```json
{
    "announcementId": "A2026021455",
    "publicationDate": "2026-11-06",
    "bulletin": "A",
    "noticeType": "initial",
    "family": "creation",
    "familyLabel": "Creation (new company or establishment)",
    "siren": "132331778",
    "companyName": "QUATREMA",
    "legalForm": "Société Civile Immobilière",
    "shareCapital": 1125400.0,
    "shareCapitalCurrency": "EUR",
    "headOfficePostalCode": "06650",
    "headOfficeCity": "Le Rouret",
    "headOfficeDepartment": "06",
    "court": "Greffe du Tribunal de Commerce de Grasse",
    "activity": "L'acquisition, l'administration, la propriété et la gestion de tous immeubles...",
    "actCategory": "Immatriculation d'une personne morale (B, C, D) suite à création d'un établissement principal",
    "activityStartDate": "2026-11-02",
    "previousOwners": [],
    "textWithheld": false,
    "announcementUrl": "https://www.bodacc.fr/pages/annonces-commerciales-detail/?q.id=id:A2026021455",
    "source": "BODACC, DILA (bodacc-datadila.opendatasoft.com), Licence Ouverte / Open Licence 2.0 (Etalab)"
}
```

#### All fields

- **Notice**: `announcementId`, `publicationDate`, `bulletin` (A, B or C), `bulletinIssue`, `announcementNumber`, `noticeType` (initial, correction, cancellation), `family`, `familyLabel` (English), `familyLabelFr`, `announcementUrl`.
- **Company**: `siren`, `companyName`, `acronym`, `tradeName`, `legalForm`, `shareCapital`, `shareCapitalCurrency`.
- **Location**: `headOfficePostalCode`, `headOfficeCity`, `headOfficeDepartment` (from the postcode), `courtDepartmentCode`, `courtDepartmentName`, `regionCode`, `regionName`, `court`, `registry`.
- **Content of the notice**: `activity`, `actCategory`, `actSummary`, `activityStartDate`, `registrationDate`, `judgmentFamily`, `judgmentNature`, `judgmentDate`, `accountsClosingDate`, `accountsFilingType`, `previousOwners` (companies only), `textWithheld`.
- **Provenance**: `source`.

The dataset has three ready-made views: Overview, Insolvency proceedings, Sales and creations. A `SUMMARY` record in the key-value store gives the counters of the run (found, scanned, left out by the privacy rule, requests).

### Privacy rule

The BODACC also publishes notices about natural persons (sole traders, "entrepreneurs individuels") and names company officers. This Actor is built for business data only:

1. A notice is **returned only if every subject of the notice is a legal entity** ("personne morale" in the source) with a company name and a valid SIREN, and its legal form is not an individual business (EI, EIRL, micro-entrepreneur, "commerçant", "personne physique"...).
2. A notice is **dropped entirely** when a previous owner or operator of a sold business is a natural person, or when a judgment targets a person (personal bankruptcy, ban from managing a company).
3. In the notices that are kept, **no person is named**: officers (gérant, président...), court-appointed representatives, home addresses and the free texts that could contain them are never copied. A short summary is kept only when it contains no sign of a person (no civility, no role such as "gérant", no e-mail, no phone number); otherwise it is left out and `textWithheld` is `true`.

When in doubt (unreadable record, missing type), the notice is dropped. Dropped notices are free and counted in the run summary.

### Pricing

Pay per event: **$1.50 per 1,000 company notices** ($0.0015 per notice returned), plus the standard Apify run start fee. Notices left out by the privacy rule are free.

You can set a maximum cost per run in Apify: the Actor stops cleanly when it is reached and keeps everything already delivered.

### FAQ

**How fast is it?** Each request returns up to 100 notices. In our tests, 1,000 company notices took about 26 seconds (18 requests, under 100 MB of memory).

**Why are there fewer creations than on bodacc.fr?** Because a large share of new businesses are sole traders (natural persons), whose notices are never returned. This is on purpose.

**Is the department the one of the head office?** The `departments` filter uses the department of the commercial court registry that published the notice, which in practice is the department of the registered office. The output also gives `headOfficeDepartment`, computed from the head office postcode.

**Can I get the names of officers or liquidators?** No. They are personal data, and this Actor never exports them.

**Does it cover associations or civil notices?** It covers the commercial notices of the BODACC (dataset "annonces commerciales"). Civil notices (personal recovery, successions) are not published in the open data and are out of scope.

### Limits

- One run reads at most 100,000 notices that you keep (`maxResults`).
- A single day with more than 10,000 matching notices is cut by department; notices without a usual department code on such a day are skipped and counted in the summary (`truncated_windows`). This only happens with very broad queries on accounts filings (`dpc`).
- If the public API is down, the Actor retries several times with backoff, then stops and keeps what was already delivered.

### Data source and licence

Data: BODACC, published by the DILA on its open data portal (bodacc-datadila.opendatasoft.com) and referenced on data.gouv.fr (https://www.data.gouv.fr/datasets/bodacc). The DILA API sheet ("Fiche API BODACC", https://echanges.dila.gouv.fr/OPENDATA/BODACC/DILA_API-BODACC_Presentation_20260327.pdf) states that the API is free to use and that reuse of the data falls under the **Licence Ouverte / Open Licence version 2.0** (Etalab): https://www.etalab.gouv.fr/wp-content/uploads/2017/04/ETALAB-Licence-Ouverte-v2.0.pdf. You may reuse the data, including commercially, provided you mention the source and the date of last update. Every output row carries the source in the `source` field.

The DILA also reminds reusers that personal data in public information must be handled under the French data protection law ("Avertissement données à caractère personnel", https://echanges.dila.gouv.fr/OPENDATA/AVERTISSEMENT-Donnees_a_caractere_personnel.pdf). This Actor's privacy rule is designed with that in mind.

This Actor is an independent tool. It is not affiliated with, or endorsed by, the DILA or the French administration.

# Actor input Schema

## `sirens` (type: `array`):

Optional. French company identifiers (SIREN, 9 digits; a 14-digit SIRET is reduced to its SIREN). Only notices about these companies are returned. When this list is filled and no start date is given, the whole history since 2008 is searched. Up to 1,000 SIREN per run.

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

Optional. French department codes of the commercial court registry that published the notice (in practice the department of the company's registered office): 01 to 95, 2A, 2B, 971 to 976. Leave empty for all of France.

## `noticeFamilies` (type: `array`):

Which kinds of notices to return. creation = new company or establishment; immatriculation = registration after a transfer of registered office; modification = change of officers, address, capital, activity, dissolution; vente = sale or transfer of a business, merger; radiation = removal from the trade register; collective = insolvency proceedings (safeguard, receivership, liquidation); conciliation = conciliation proceedings; dpc = filing of annual accounts; divers = miscellaneous. Default: creation, vente, modification, radiation, collective.

## `noticeTypes` (type: `array`):

initial = first publication; correction = notice that corrects an earlier one; cancellation = notice that cancels an earlier one. Default: all three.

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

Optional. First publication date to include, written YYYY-MM-DD. Default: 30 days before dateTo, or 2008-01-01 when SIREN numbers are given (the dataset starts in 2008).

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

Optional. Last publication date to include, written YYYY-MM-DD. Default: today.

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

The run stops after this many company notices (each one is a charged result). Newest notices come first.

## `maxRequestsPerSecond` (type: `integer`):

Politeness limit towards the public API (each request returns up to 100 notices). Leave the default unless you run several copies in parallel.

## Actor input object example

```json
{
  "sirens": [
    "552032534",
    "542051180"
  ],
  "departments": [
    "75",
    "92",
    "69"
  ],
  "noticeFamilies": [
    "collective"
  ],
  "noticeTypes": [
    "initial"
  ],
  "dateFrom": "2026-10-01",
  "dateTo": "2026-10-31",
  "maxResults": 500,
  "maxRequestsPerSecond": 5
}
```

# Actor output Schema

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

Company notices as JSON objects.

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

Counters of the run: notices found, scanned and left out by the privacy rule.

# 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 = {
    "sirens": [
        "552032534"
    ],
    "maxResults": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("edgarfinance/france-bodacc-notices").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 = {
    "sirens": ["552032534"],
    "maxResults": 100,
}

# Run the Actor and wait for it to finish
run = client.actor("edgarfinance/france-bodacc-notices").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 '{
  "sirens": [
    "552032534"
  ],
  "maxResults": 100
}' |
apify call edgarfinance/france-bodacc-notices --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,edgarfinance/france-bodacc-notices"
        }
    }
}
```

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/HY0TIqZbRn9vgcb9N/builds/j4WhQoezipK4xmPN8/openapi.json
