BODACC France Company Notices Scraper

Extract official French BODACC company legal notices from the DILA/OpenDataSoft API.

Use this actor to search, monitor, and export company announcements by SIREN, company name, publication date, department, notice family, notice type, or legal-event keyword.

The actor is designed for compliance, KYB, credit-risk, legal operations, sales operations, and data teams that need repeatable BODACC data without maintaining their own API client.

What does BODACC France Company Notices Scraper do?

BODACC France Company Notices Scraper collects announcement records from the official BODACC commercial notices dataset.

It saves normalized rows to an Apify dataset.

Each row includes identifiers, source URLs, dates, notice categories, company names, SIREN/RCS numbers, geography, tribunal data, event summaries, structured nested objects, and optional raw source JSON.

You can run it once for ad-hoc research.

You can also schedule it to build a daily or weekly monitoring feed.

Who is it for?

Compliance analysts use it to watch suppliers, customers, or counterparties for legal events.

KYB teams use it to enrich onboarding checks with official French public notices.

Credit-risk teams use it to spot insolvency, liquidation, radiation, filing, and registration signals.

Legal teams use it to monitor restructuring or court-related notices.

B2B sales and RevOps teams use it to detect company changes that may trigger outreach.

Data vendors use it as an official public-data source for French company-event feeds.

Why use this actor?

It uses the official DILA/OpenDataSoft API.

No login is required.

No browser automation is required.

No proxy is required for the normal workflow.

The output is immediately available in JSON, CSV, Excel, XML, RSS, and via the Apify API.

The actor preserves the raw record by default so French source fields remain available for audit and downstream parsing.

BODACC data source

The source dataset is annonces-commerciales hosted by bodacc-datadila.opendatasoft.com.

BODACC announcements cover French commercial legal events.

The dataset includes notices for registrations, modifications, radiations, account filings, judgments, acts, transfers, and other commercial announcements.

OpenDataSoft field names are French.

This actor maps common fields into English names while keeping rawRecord available.

Data fields you get

Field	Description
bodaccId	BODACC announcement identifier
sourceUrl	Official BODACC detail URL when available
publicationDate	Publication date
publicationCode	BODACC publication code
announcementNumber	Announcement number inside the issue
noticeTypeLabel	Human-readable notice type
noticeFamilyLabel	Human-readable notice family
companyName	Company or commercial name
siren	Normalized 9-digit SIREN when present
rcsNumbers	RCS/registration values from the source
departmentCode	French department code
departmentName	Department name
city	City
postalCode	Postal code
tribunal	Registry court / tribunal
legalForm	Legal form when available
eventSummary	Best available short event summary
persons	Parsed person/company object
establishments	Parsed establishment object
judgment	Parsed judgment object
filing	Parsed filing/deposit object
rawRecord	Complete source record when enabled

How much does it cost to scrape BODACC company notices?

This actor uses pay-per-event pricing.

A small run fee is charged when the actor starts.

A per-result fee is charged for each BODACC notice saved to the dataset.

The exact live price is visible on the Apify Store pricing panel.

Because the actor uses an official HTTP API and does not need a browser or proxy, normal runs are designed to be inexpensive.

How to use it

1. Open the actor on Apify.
2. Choose a maximum number of notices.
3. Add a date range.
4. Optionally add department codes.
5. Optionally add one or more SIREN numbers.
6. Optionally add a company-name search.
7. Optionally add a full-text legal-event query.
8. Run the actor.
9. Download the dataset or connect it to your workflow.

Example input: Paris keyword search

{
  "maxItems": 100,
  "dateFrom": "2025-01-01",
  "dateTo": "2025-01-31",
  "departments": ["75"],
  "companyQuery": "boulangerie",
  "sortOrder": "newest",
  "includeRawRecord": true
}

Example input: SIREN monitoring

{
  "maxItems": 50,
  "sirens": ["752461681"],
  "dateFrom": "2024-01-01",
  "dateTo": "2025-12-31",
  "sortOrder": "newest",
  "includeRawRecord": true
}

Example input: insolvency and risk feed

{
  "maxItems": 250,
  "dateFrom": "2025-01-01",
  "dateTo": "2025-01-31",
  "departments": ["75", "92", "93"],
  "fullTextQuery": "liquidation redressement radiation",
  "sortOrder": "newest",
  "includeRawRecord": true
}

Input options

maxItems controls how many notices are saved.

dateFrom and dateTo filter by BODACC publication date.

departments filters by French department code.

sirens filters by registration number.

companyQuery searches company and person fields.

fullTextQuery performs a global OpenDataSoft search.

noticeFamilies filters BODACC family codes or labels.

noticeTypes filters notice type codes or labels.

sortOrder returns newest or oldest records first.

includeRawRecord keeps the complete source JSON.

Output example

{
  "bodaccId": "C202500182618",
  "source": "BODACC OpenDataSoft",
  "sourceUrl": "https://www.bodacc.fr/pages/annonces-commerciales-detail/?q.id=id:C202500182618",
  "publicationDate": "2025-01-26",
  "noticeTypeLabel": "Avis initial",
  "noticeFamilyLabel": "Dépôts des comptes",
  "companyName": "Le Fournil des Bocages",
  "siren": "752461681",
  "departmentCode": "60",
  "departmentName": "Oise",
  "city": "Thiescourt",
  "tribunal": "Greffe du Tribunal de Commerce de compiègne"
}

Tips for better results

Use a date range for scheduled monitoring.

Use SIREN numbers when you need exact company matches.

Use department codes to keep searches focused.

Use fullTextQuery for legal-event keywords such as liquidation, redressement, or radiation.

Keep includeRawRecord enabled when you need legal auditability.

Lower maxItems for test runs.

Increase maxItems for production exports.

Common workflows

Daily supplier-risk monitoring.

Weekly insolvency alert feed.

Portfolio company legal-event enrichment.

French company onboarding checks.

CRM enrichment for newly registered or modified companies.

Legal research by department and tribunal.

Data warehouse ingestion of official BODACC records.

Integrations

Export the dataset to Google Sheets for analyst review.

Send results to Make or Zapier for alerting.

Load JSON into a warehouse using the Apify API.

Connect the actor to webhooks for scheduled monitoring.

Combine BODACC data with other automation-lab French company actors for richer KYB workflows.

API usage with Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/bodacc-france-company-notices-scraper').call({
  maxItems: 100,
  dateFrom: '2025-01-01',
  dateTo: '2025-01-31',
  departments: ['75'],
  companyQuery: 'boulangerie'
});
console.log(run.defaultDatasetId);

API usage with Python

from apify_client import ApifyClient
import os

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('automation-lab/bodacc-france-company-notices-scraper').call(run_input={
    'maxItems': 100,
    'dateFrom': '2025-01-01',
    'dateTo': '2025-01-31',
    'departments': ['75'],
    'companyQuery': 'boulangerie'
})
print(run['defaultDatasetId'])

API usage with cURL

curl -X POST "https://api.apify.com/v2/acts/automation-lab~bodacc-france-company-notices-scraper/runs?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"maxItems":100,"dateFrom":"2025-01-01","dateTo":"2025-01-31","departments":["75"],"companyQuery":"boulangerie"}'

MCP: use BODACC data from AI tools

You can call this actor through the Apify MCP server from Claude Code, Claude Desktop, Cursor, or VS Code.

Use the MCP URL with this actor tool enabled:

https://mcp.apify.com/?tools=automation-lab/bodacc-france-company-notices-scraper

Claude Code setup with HTTP transport:

$claude mcp add apify-bodacc --transport http "https://mcp.apify.com/?tools=automation-lab/bodacc-france-company-notices-scraper"

Claude Desktop JSON setup:

{
  "mcpServers": {
    "apify-bodacc": {
      "url": "https://mcp.apify.com/?tools=automation-lab/bodacc-france-company-notices-scraper"
    }
  }
}

Cursor JSON setup:

{
  "mcpServers": {
    "apify-bodacc": {
      "url": "https://mcp.apify.com/?tools=automation-lab/bodacc-france-company-notices-scraper"
    }
  }
}

VS Code JSON setup:

{
  "servers": {
    "apify-bodacc": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=automation-lab/bodacc-france-company-notices-scraper"
    }
  }
}

Example prompt for Claude Code MCP usage:

"Use the BODACC France Company Notices Scraper tool for Paris notices in January 2025 matching boulangerie and summarize insolvency or radiation signals."

Example prompt for Claude Desktop, Cursor, or VS Code MCP usage:

"Run the Apify BODACC tool for these SIRENs and return a table with publication date, family, tribunal, and source URL."

Example workflow prompt:

"Create a weekly BODACC monitoring feed for departments 75 and 92 and highlight redressement, liquidation, or radiation notices."

Scheduling

Create an Apify task with your preferred filters.

Schedule it daily, weekly, or monthly.

Use the Apify dataset API to fetch only the latest run results.

For delta workflows, set a date range matching the schedule window.

Legality

This actor uses official public-data endpoints.

You are responsible for using the data in compliance with applicable law, privacy rules, and your internal policies.

The actor does not bypass authentication or private systems.

FAQ

Is this official BODACC data?

Yes. The actor reads the official DILA/OpenDataSoft BODACC commercial announcements dataset.

Do I need a BODACC login or API key?

No. The implemented source is public and does not require a user account.

Can I monitor a list of SIRENs?

Yes. Add your SIREN or RCS values to the sirens input and schedule the actor.

Why do some nested fields vary by row?

BODACC notice families have different French source structures, so the actor keeps parsed nested objects and optional rawRecord data.

Troubleshooting

If you get zero results, widen the date range or remove restrictive filters.

If SIREN matching returns unexpected records, check whether the source record contains multiple formatted RCS values.

If a keyword query is too broad, add departments or dates.

If nested French fields are important, keep includeRawRecord enabled.

Related scrapers

Use other automation-lab French company or registry actors for profile-level data.

Use this actor when you need event-level BODACC legal announcements.

Use procurement-specific actors for BOAMP or tender workflows.

Limitations

OpenDataSoft pagination has practical offset limits.

For very large exports, narrow the run by date, department, family, or company.

Some event-specific details are nested and vary by notice family.

The actor preserves raw data so you can inspect fields not yet normalized.

Support

Open an Apify issue if a run fails or if a BODACC field should be normalized into a top-level column.

Include your input, run ID, and a short description of the expected result.

Version notes

Initial version focuses on official commercial notices from the BODACC OpenDataSoft API.

Future versions can add more opinionated event classification if users request it.