# France New Company Finder (BODACC + SIRENE, by NAF & Dept) (`lindenbyte/france-new-companies`) Actor

Daily feed of newly registered French companies (legal entities only) from official BODACC creations, enriched with SIRENE: SIREN/SIRET, NAF, legal form, head office with GPS, employee range, capital, VAT number. Filter by date, NAF, département, region, legal form.

- **URL**: https://apify.com/lindenbyte/france-new-companies.md
- **Developed by:** [Lindenbyte Studio](https://apify.com/lindenbyte) (community)
- **Categories:** Lead generation, Business
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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

## France New Company Finder (BODACC + SIRENE Leads by NAF & Département)

Get a **daily list of newly registered French companies** straight from the official **BODACC** (Bulletin officiel des annonces civiles et commerciales) creation notices, enriched with the **SIRENE** register through the official `recherche-entreprises.api.gouv.fr` API. Pick a publication date range (or "last N days" for a schedule), filter by **NAF / APE code**, **département**, **region**, **legal form** (SAS, SARL, SCI...) or activity keywords, and get one clean row per company: name, **SIREN / head-office SIRET**, legal form, NAF code **with its label**, head-office address **with GPS coordinates**, share capital, employee range, registration date, computed **VAT number** and links to the BODACC notice and the official Annuaire des Entreprises page.

About **20,000 companies** are created in France every month. Every one of them needs a bank, an accountant, insurance, a website, software and suppliers. This Actor gives you that list every morning.

### Why this one

- **Companies only, no sole traders**: personnes physiques (entrepreneurs individuels, micro-entrepreneurs) are excluded at the source and again in the Actor. No names of managers or shareholders are collected. Company-level data only.
- **BODACC + SIRENE in one row**: BODACC gives the legal announcement (capital, activity description, registry court); SIRENE adds SIRET, NAF code (rév. 2 and NAF 2025), legal form code, head-office address with latitude/longitude, employee range and company category.
- **Gets past the 10,000-result API cap**: the BODACC API stops at 10,000 results per query. The Actor counts first and splits the date range into smaller windows, so a full month of France (22,000+ notices) comes out complete.
- **Département filter that is right**: matched on the head-office postcode, not only on the registry court, so a Paris company registered at another court still counts as Paris.
- **Prospecting opt-out flag**: every row says whether the company objected to commercial use of its SIRENE data (`commercialUseOptOut`), and one switch drops those companies.
- **Rate-limit safe**: stays under the documented recherche-entreprises limit (7 requests/second) and backs off on 429s.

### Use cases

- **Accountants (experts-comptables), banks, insurers**: reach companies in their first weeks, by département and activity.
- **B2B SaaS, agencies, web designers**: new software, e-commerce, construction or restaurant companies by NAF code.
- **Real-estate and wealth advisors**: new SCIs and holding companies in your area.
- **Market research**: creation trends by sector, legal form and region.
- **CRM hygiene and KYC**: SIREN, SIRET and VAT number of new counterparties.

### Input

| Field | What it does |
|---|---|
| `publishedLastDays` | Rolling window on the BODACC publication date, e.g. 3 for a daily schedule. Overrides the dates. Default (nothing set): last 7 days |
| `publishedFrom`, `publishedTo` | Fixed publication date range (YYYY-MM-DD, inclusive) |
| `departements` | Codes or names: `75`, `69`, `2A`, `971`, `Gironde` |
| `regions` | INSEE regions, e.g. `11` Île-de-France, `84` Auvergne-Rhône-Alpes |
| `nafCodes` | `62.01Z`, `62.01`, `62` or a section letter like `J`. Any match counts |
| `legalForms` | Families: `SAS` (SAS/SASU), `SARL` (SARL/EURL), `SA`, `SNC`, `SCI`, `SC`, `AGRI`, `SEL`, `COOP`, `GIE`, `FOREIGN`, `OTHER` |
| `legalFormCodes` | Advanced: INSEE catégorie juridique codes or prefixes, e.g. `5710`, `6540`, `57` |
| `activityKeywords` | Words in the activity description, e.g. `restaurant`, `logiciel` |
| `excludeCommercialOptOut` | Drop companies that objected to commercial use of their data (free) |
| `onlyWithSireneData` | Drop companies not yet indexed in SIRENE (free) |
| `enrichWithSirene` | Default on. Off = BODACC fields only, much faster |
| `maxResults` | Stop after this many companies (default 1,000) |

### Output (one item per company)

Real example (BODACC notice published 2026-11-13, activity description shortened):

```json
{
  "siren": "131853400",
  "siretSiege": "13185340000011",
  "name": "BEE SOFT",
  "tradeName": "BeeMySchool",
  "legalFormCode": "5710",
  "legalFormLabel": "SAS, société par actions simplifiée",
  "legalFormGroup": "SAS",
  "nafCode": "62.01Z",
  "nafLabel": "Programmation informatique",
  "naf2025Code": "62.10Y",
  "nafSection": "J",
  "nafSectionLabel": "Information et communication",
  "activityDescription": "Le développement, l'édition, l'exploitation et la commercialisation de toute solution logicielle...",
  "registrationDate": "2026-10-26",
  "activityStartDate": "2026-10-12",
  "creationDate": "2026-10-12",
  "bodaccPublicationDate": "2026-11-13",
  "street": "36 RUE SCHEFFER",
  "postalCode": "75116",
  "city": "PARIS",
  "inseeCityCode": "75116",
  "departement": "75",
  "departementName": "Paris",
  "region": "11",
  "regionName": "Île-de-France",
  "latitude": 48.862036959407185,
  "longitude": 2.282186933904752,
  "address": "36 RUE SCHEFFER, 75116 PARIS",
  "capital": 8000,
  "capitalCurrency": "EUR",
  "employeeRangeCode": "NN",
  "employeeRange": "Unité non employeuse (pas de salarié au cours de l'année de référence et pas d'effectif au 31/12)",
  "establishmentCount": 1,
  "administrativeStatus": "A",
  "commercialUseOptOut": true,
  "vatNumberComputed": "FR32131853400",
  "registryCourt": "Greffe du Tribunal des Activités Economiques de Paris",
  "bodaccNoticeId": "A202602183127",
  "bodaccUrl": "https://www.bodacc.fr/pages/annonces-commerciales-detail/?q.id=id:A202602183127",
  "annuaireUrl": "https://annuaire-entreprises.data.gouv.fr/entreprise/131853400",
  "sireneFound": true,
  "scrapedAt": "2026-11-13T12:00:23.268Z"
}
```

Each row also has `acronym`, `legalFormText`, `naf2025Label`, `bodaccCategory`, `originOfBusiness`, `addressComplement`, `country`, `capitalVariable`, `employeeRangeYear`, `companyCategory`, `financesYear`, `revenue`, `netIncome`, `isEss`, `isMissionCompany`, `diffusionStatus` and `enrichmentError`. Download as CSV, Excel or JSON, or connect to Google Sheets, HubSpot, Zapier or Make.

A `SUMMARY` record in the key-value store lists the date windows used, notices scanned, rows dropped by each filter, companies not yet in SIRENE and API requests made.

### Pricing

Pay per result: you pay per company saved. Companies dropped by your filters (NAF, département, legal form, opt-out) are not charged. Set a maximum charge on the run and the Actor stops cleanly when it is reached.

### Tips

- **Daily schedule**: `publishedLastDays: 3` plus your filters, dedupe on `siren`. BODACC publishes Monday to Saturday, from a few days to a few weeks after the company registers (`registrationDate`).
- **Cold outreach in France**: switch on `excludeCommercialOptOut`. Most brand-new companies carry the opt-out flag in SIRENE, so expect fewer than one company in ten to remain (7% in a 1,000-company sample, November 2026). Check the rules that apply to your use (GDPR, French prospecting rules) yourself.
- **Speed**: with SIRENE enrichment about 5 companies/second (one lookup per company, held under the official rate limit). NAF and legal-form-code filters need that lookup for every notice scanned, so narrow by département, region or keywords first. Without enrichment, a full month of France takes a few minutes.
- **Brand-new companies**: about 10% of the newest notices are not yet in SIRENE. They are still returned with the BODACC data (`sireneFound: false`) unless a SIRENE-based filter or `onlyWithSireneData` is on.

### Limits (honest)

- Dates are BODACC **publication** dates, not registration dates (both are in the output).
- Only what BODACC and SIRENE publish: no phone numbers, emails, websites or names of people.
- A single publication day with more than 10,000 notices could only return the first 10,000 (has not happened: a busy day is about 1,000).
- `vatNumberComputed` is calculated from the SIREN with the official key formula; it does not prove the company is VAT-registered.

### Data source and licence

BODACC data: DILA, via the BODACC open-data API (Opendatasoft). SIRENE data: INSEE, via the API Recherche d'entreprises (DINUM, annuaire-entreprises.data.gouv.fr). Both are published under the **Licence Ouverte / Open Licence v2.0 (Etalab)**; source: DILA BODACC and INSEE SIRENE, data retrieved on the date in `scrapedAt`. NAF and legal-form labels: INSEE nomenclatures.

Not affiliated with or endorsed by DILA, INSEE, DINUM or the French administration.

# Actor input Schema

## `publishedLastDays` (type: `integer`):

Rolling window on the BODACC publication date (French time): 1 = today only, 3 = the last 3 days including today. Overrides the from/to dates. If everything is empty the last 7 days are used. BODACC publishes Monday to Saturday, usually a few days after the registration; for a daily schedule use 3 and dedupe on 'siren' downstream.

## `publishedFrom` (type: `string`):

First BODACC publication date, inclusive, e.g. 2026-11-01. Used only when 'last N days' is empty.

## `publishedTo` (type: `string`):

Last BODACC publication date, inclusive. Empty = today.

## `departements` (type: `array`):

Département codes or names, e.g. 75, 69, 13, 2A, 971 or 'Gironde'. A company matches when its head office (siège) is in one of them. Empty = all of France (incl. overseas).

## `regions` (type: `array`):

Adds every département of these regions (INSEE region codes). Combined with 'Départements' as an OR.

## `nafCodes` (type: `array`):

Activity codes (NAF rév. 2, also matched against NAF 2025): exact (62.01Z), prefix (62.01, 62) or section letter (J = information & communication, F = construction, I = hospitality). Needs the SIRENE enrichment; companies not yet in SIRENE are dropped (free) when this is set.

## `legalForms` (type: `array`):

Keep only these legal form families (e.g. SAS for SAS/SASU, SARL for SARL/EURL, SCI). Empty = all legal entities. Sole traders (entrepreneurs individuels) are never returned.

## `legalFormCodes` (type: `array`):

INSEE 'catégorie juridique' codes or prefixes, e.g. 5710 (SAS), 5499 (SARL), 6540 (SCI), 57 (all SAS). Needs the SIRENE enrichment.

## `activityKeywords` (type: `array`):

Words searched in the activity description of the BODACC notice (French), e.g. 'restaurant', 'logiciel', 'boulangerie'. A company matches if any keyword appears. Applied by the API, so it is fast.

## `excludeCommercialOptOut` (type: `boolean`):

Drop companies whose SIRENE record carries an objection to commercial use (opposition_diffusion_commerciale). Recommended for cold outreach in France. Note: most brand-new companies carry this flag, so expect far fewer results. Dropped rows are free.

## `onlyWithSireneData` (type: `boolean`):

Drop companies that are in BODACC but not yet indexed in SIRENE (about 10% of the newest notices; they appear within days). Dropped rows are free.

## `enrichWithSirene` (type: `boolean`):

Look each company up in the official recherche-entreprises API (SIRET, NAF, legal form code, head-office address with GPS, employee range, category). Off = BODACC fields only (much faster; NAF/legal-form-code/opt-out filters need it on).

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

Stop after this many companies have been saved.

## Actor input object example

```json
{
  "publishedLastDays": 3,
  "departements": [
    "75"
  ],
  "excludeCommercialOptOut": false,
  "onlyWithSireneData": false,
  "enrichWithSirene": true,
  "maxResults": 1000
}
```

# Actor output Schema

## `results` (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 = {
    "publishedLastDays": 3,
    "departements": [
        "75"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("lindenbyte/france-new-companies").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 = {
    "publishedLastDays": 3,
    "departements": ["75"],
}

# Run the Actor and wait for it to finish
run = client.actor("lindenbyte/france-new-companies").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 '{
  "publishedLastDays": 3,
  "departements": [
    "75"
  ]
}' |
apify call lindenbyte/france-new-companies --silent --output-dataset

```

## MCP server setup

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

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/jnmnqj3oIYoLBbr44/builds/QRViuniwFrE0r4fwA/openapi.json
