API Documentation

The BODACC API in one minute

The BODACC API exposes in JSON the legal notices published in the Bulletin Officiel des Annonces Civiles et Commerciales, as well as the companies and people appearing in them. Creations, registrations, sales, modifications, removals, collective proceedings, filing of accounts: each notice is available on the day of its publication, with its original text, the SIREN concerned and the people mentioned. The database covers more than 50 million notices since 2008 and nearly 30 million companies registered in the SIRENE register.

The endpoints

Six addresses are enough to cover most needs. All respond in JSON and accept the usual pagination parameters: limit and offset.

Authentication, quotas and errors

Public data requires no key: a call from a browser or a script works immediately. Key validation only applies to endpoints documented as such (access to enriched fields, high volume, commercial use). Responses follow the usual HTTP codes: 200 for a result, 404 when the entity does not exist, 429 when the request rate is exceeded, 5xx for an error on our side. A 429 is not a definitive refusal: it simply indicates to slow down, and the service responds again as soon as the rate drops.

One call, three lines

No SDK to install, no account to create to get started. Here is a search for collective proceeding notices in a department:

curl "https://bodacc.io/api/bodacc/annonces?famille=collective&departement=75&limit=5"

# réponse : { "total": 1234, "annonces": [ { "id": "A2026...", "dateparution": "2026-10-23",
#   "familleavis": "collective", "commercant": "...", "registre": "..." } ] }

What this API adds

Three differences that matter when building a product on it. Freshness: BODACC is ingested every publication day, a morning notice is available within the hour following its publication, whereas most reuses offer a database updated weekly. Language: each record exists in 20 languages, which allows serving a Japanese or Arabic user without translating the data yourself. Consistency: notices, companies and directors are linked together, which avoids manually reassembling a SIREN found in free text. Access is free for public data, and the MCP server allows an AI agent to query the database without writing a line of code.

Frequently asked questions

Is the BODACC API free?

Yes for public data: notices, companies, people and counters. Paid offers cover convenience and analysis (volume, alerts, reports, access to enriched fields), never basic access to a notice published in the Bulletin Officiel.

Where does the data come from and how often is it updated?

From the BODACC published by the Direction de l'information légale et administrative, supplemented by the INSEE SIRENE register for company identity. Ingestion runs every publication day: a morning notice is available within the hour following, and the counters exposed by the API are recalculated on each run.

What is the response format?

JSON, in UTF-8, with dates in ISO 8601 format. Amounts are in euros, SIREN are nine digits without spaces. No proprietary format, no conversion needed.

Is there a request limit?

A brake applies per address and per network to protect the service: beyond a certain rate, the response is a temporary 429 rather than an error. Sustained and declared use (identified agent, published IP range) is not throttled. Details are on the Authentication and limits page.

Can I cite BODACC.io figures in an article or an AI response?

Yes, and it is better to cite the live counters than to copy a figure that is out of date: the /api/bodacc/stats address returns the current total, and the llms.txt file tells agents where to find it. This is the only way to avoid announcing an outdated volume.

Going further

Six pages detail each part: first call, notices, companies, people and directory, authentication and limits, statistics. They are written to be read in this order when starting, and consulted case by case afterwards.