# French Companies (SIRENE) - Official Registry (`egarian/sirene-france-companies`) Actor

Official French company registry (SIRENE) straight from the INSEE API. 15M+ companies, all legal forms. Search by SIRET, SIREN, NAF/APE code, city, postal code, department, legal form, creation date. Perfect for B2B prospecting, KYC, compliance, market analysis.

- **URL**: https://apify.com/egarian/sirene-france-companies.md
- **Developed by:** [Loïc Rossi](https://apify.com/egarian) (community)
- **Categories:** Business, Lead generation
- **Stats:** 2 total users, 1 monthly users, 81.8% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 company records

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 Companies Registry (SIRENE) — Official INSEE Data

Search **millions of French companies** from the official **SIRENE register**, served by INSEE's Sirene 3.11 API. No 2.6 GB bulk files to download — query by SIREN/SIRET, activity code (NAF), location, creation date or legal form and get clean JSON records.

### What it does

- **Legal units** (by SIREN) and **establishments** (by SIRET, with full address) — the actor picks the right endpoint automatically
- Filters: SIREN/SIRET lists, **NAF/APE activity codes** (prefix match supported), city, postal code, department, creation date range, legal form, active-only
- Output verbosity: `minimal`, `standard`, `full` (full includes the raw INSEE payload)
- Handles INSEE pagination (1,000 records/page) and API rate limits automatically

### Input example

```json
{
  "nafCodes": ["6201Z"],
  "departments": ["75"],
  "activeOnly": true,
  "maxRecords": 100,
  "outputFields": "standard"
}
```

Main input fields: `sirets`, `sirenes`, `nafCodes`, `cities`, `postalCodes`, `departments`, `dateCreatedFrom`, `dateCreatedTo`, `legalForms` (e.g. `5499` = SAS, `5498` = SARL), `activeOnly`, `maxRecords`, `outputFields`.

### Output example (establishment, standard)

```json
{
  "siren": "309634954",
  "siret": "30963495400036",
  "companyName": "EXAMPLE SAS",
  "legalForm": "5499",
  "nafCode": "62.01Z",
  "creationDate": "2019-04-12",
  "status": "active",
  "employeeTranche": "21",
  "address": { "street": "12 RUE DE LA PAIX", "postalCode": "75002", "city": "PARIS" },
  "isHeadquarter": true,
  "entityType": "establishment",
  "scrapedAt": "2026-10-13T09:00:00.000Z"
}
```

`full` mode adds the raw INSEE record under `raw`. `minimal` keeps only the key identification fields.

### Data source

- **INSEE Sirene 3.11** — official company registry of France (`api.insee.fr`), updated daily
- Legal units and establishments of active and inactive companies

### Notes

- The Actor is preconfigured with INSEE API access — **you don't need your own INSEE key**.
- Covers companies registered in France (including DOM-TOM where available in the register).
- HTTP errors fail the run loudly instead of returning empty results.

# Actor input Schema

## `sirets` (type: `array`):

Specific SIRET numbers to fetch (14 digits)

## `sirenes` (type: `array`):

Specific SIREN numbers to fetch (9 digits)

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

Activity codes (e.g., 6201Z, 6202A, 7022Z). Prefix match supported.

## `cities` (type: `array`):

City names (e.g., Paris, Lyon, Marseille)

## `postalCodes` (type: `array`):

Postal codes (e.g., 75001, 69000, 13000)

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

Department codes (e.g., 75, 69, 13, 2A, 2B)

## `dateCreatedFrom` (type: `string`):

Filter companies created after this date

## `dateCreatedTo` (type: `string`):

Filter companies created before this date

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

Legal form codes (e.g., 5499=SAS, 5498=SARL, 1000=SA, 5599=EI)

## `activeOnly` (type: `boolean`):

Only return active companies (etatAdministratif=A)

## `maxRecords` (type: `integer`):

Safety limit on output records

## `outputFields` (type: `string`):

Output verbosity

## Actor input object example

```json
{
  "sirets": [],
  "sirenes": [],
  "nafCodes": [],
  "cities": [],
  "postalCodes": [],
  "departments": [],
  "dateCreatedFrom": "",
  "dateCreatedTo": "",
  "legalForms": [],
  "activeOnly": true,
  "maxRecords": 1000,
  "outputFields": "standard"
}
```

# Actor output Schema

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

French companies from the INSEE SIRENE 3.11 API. One item per company (head office) matching the filters.

# 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("egarian/sirene-france-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("egarian/sirene-france-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 '{}' |
apify call egarian/sirene-france-companies --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,egarian/sirene-france-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/xhI35P04yX4CdSWpa/builds/Vcl4fiwBYre45mfdV/openapi.json