API integration for BODACC
We build your BODACC connector
We wire the official French commercial gazette into your CRM or credit tool: alerts on insolvency proceedings, strike-offs and business transfers, matched to the SIREN already on file.
- Senior product team
- public-data connectors in production
- from scoping to monitoring
What does the BODACC API provide and why integrate it into a business tool?
The BODACC publishes official legal notices for French companies: incorporations, amendments, collective proceedings, strikes-off, business sales. The API provides access to this structured feed in near real time, free of charge. You integrate it to automate client portfolio monitoring: being alerted the moment a client enters a collective proceeding or is struck off, or to enrich a company record with its recent legal history. It is a source of commercial intelligence and risk management that many teams still check manually today.
What our clients build on the BODACC API
Insolvency watch on the book
Every morning, familleavis=collective notices for customers and suppliers reach the account owner, with an optional credit freeze.
Strike-off alert before invoicing
An RCS strike-off published in BODACC blocks the invoice or the maintenance contract, before a certain unpaid bill.
Detecting a business transfer
Sales and transfers feed an insurance or collections tool, with the notice PDF as a file exhibit.
Credit onboarding check
A credit line is refused if a recent insolvency proceeding is attached to the file's SIREN.
What it changes in your credit tool
Engineering in service of a measurable outcome: an alert on publication day, not a manual quarterly review.
The primary source, not an aggregator
Sirene does not publish judgments. BODACC is the free gazette for insolvency, strike-offs and transfers, with a PDF link you can put in a file.
A filter, not a 50-million-row dump
Account filings alone exceed 26 million notices. We only sync the families your product actually uses.
A match to the SIREN you already know
The registre field sticks the notice to the customer record. We do not create a company from a notice: homonyms, ND, multiple establishments.
A fallback behind Pappers
You already sell an aggregator: BODACC checks it is not a day late. You have no credit budget: this is the only insolvency brick that holds.
How we ship your BODACC connector
Scoping
Which notice families, which publication window, how we match the SIREN. We settle the filter before writing a line of code.
Development
ODSQL connector, a defensive parser for JSON-as-text, a persistent queue, exports for history and records for the daily watch.
Acceptance testing
Replay on your real book, match checks, testing the offset + limit ceiling and what happens when a jugement field is unreadable.
Monitoring
An alert if the publication window stops moving, a call log, a dashboard of unmatched notices. You see the gap before sales does.
What the BODACC API allows
- Filter by notice family
- Insolvency, strike-offs, transfers, creations, account filings: we pull only the families that matter, not 50 million rows.
- Matching on registre
- The registre field, often a SIREN, links the notice to a record already identified, with no paid aggregator.
- A link to the original notice
- url_complete and the PDF flags give you an exhibit, not just a boolean « proceeding detected ».
- Export beyond pagination
- records stop at 10,000 results. A historical replay goes through the exports endpoint (JSON, CSV, Parquet).
The vocabulary of the BODACC API
- familleavis
- The notice's business code: collective, radiation, vente, creation, dpc, immatriculation. That is the filter, not the whole gazette. Account filings (dpc) are more than half the volume.
- dateparution
- The gazette publication date, not the judgment date. A Monday judgment may only be published several days later. Selling « alert on judgment day » is false.
- registre
- The field that matches the company, often a SIREN. The exact format is not uniform: a naive filter misses notices. We test on a sample before freezing the rule.
- ODSQL
- Huwise query language: where, select, group_by, order_by, limit, offset. This is not a Pappers-style company API. Without ODSQL there is no targeted watch.
- records vs exports
- records paginates up to 10,000 results (limit 100). Beyond that, Huwise requires exports. Mixing the two produces a truncated extract nobody notices.
- ND
- A non-disclosure mark on natural persons. Treating ND as a gap to « fill in » from another source is a forbidden reconstitution. DILA is explicit: the dataset contains personal data.
The real constraints of the BODACC API
This is not GET /entreprise/{siren}
It is Opendatasoft. A consolidated record (directors, accounts, proceeding) does not exist: you parse listepersonnes and jugement, and match to the SIREN already on file.
records pagination stops at 10,000
limit max 100, offset + limit under 10,000. A job for « every proceeding this week » goes through exports filtered on dateparution, or a bounded where. Otherwise the extract is silent.
BODACC is a gazette, not a live register
The notice has a dateparution. Monday's judgment may appear several days later. We alert on publication day, not on hearing day.
Personal data and ND marks
Licence ouverte 2.0, DILA attribution, URL and date. Natural persons may be masked. We store only what the watch needs, not a file of directors.
BODACC API or Pappers?
Two ways to see an insolvency proceeding. The right choice depends on what you must do with it, not on the sticker price.
| Criterion | BODACCOfficial gazette | PappersPaid aggregator |
|---|---|---|
| Access | Open, no key | Subscription, billed per credit |
| API shape | Opendatasoft, ODSQL | REST by SIREN / SIRET |
| Insolvency proceedings | Primary gazette source | Consolidated paid record |
| Directors and accounts | No, parse them yourself | Yes, under the plan you buy |
| Returned object | A notice, not a company | An enriched company record |
| Freshness | Gazette publication date | Depends on the vendor refresh |
| The right case | Free watch on the book | A packaged KYC file |
The two combine: BODACC for the primary source and the free fallback, Pappers for the consolidated record. That is a scoping call.
What we measure on a BODACC integration
The other company APIs
If BODACC does not cover the need, these options come up during scoping.
BODACCWe build your BODACC connectorThis page
INSEE / SireneIdentification and location by SIREN or SIRET. No judgment, no proceeding.
PappersA consolidated record: directors, accounts, documents, proceedings already packaged.
Annuaire des entreprisesDINUM public search by name, no key, Sirene and RNE combined.We combine BODACC with
The stack around BODACC on our projects.
BODACC integration: your questions
This is not a REST client by SIREN. You speak Huwise Explore v2.1: a persisted window on dateparution, a where on familleavis, a defensive parser for JSON-as-text fields, a match to the SIREN already on file and a hold for unmatched notices. The daily watch goes through records; a historical replay goes through exports, because offset + limit cannot exceed 10,000. A key, if one appears later, is not the point: there is none today. The point is the product filter and GDPR (personal data, ND marks).
Access to the DILA instance is free, under Licence ouverte 2.0, with an attribution duty. The cost is the connector: filter, parser, queue, matching, monitoring. An insolvency watch on a book already identified by SIREN is a short piece of work. A territorial history, a bulk export or a fuzzy match on registre is a project of its own. We scope the perimeter and give a firm estimate before we start.
Pappers returns a company record. BODACC returns a gazette notice, which you match yourself. Pappers is paid and consolidates directors, accounts and proceedings. BODACC is the free primary source of notices (creations, strike-offs, transfers, proceedings, account filings). Sirene, for its part, identifies and locates, but does not publish the judgment. In practice we combine them: Sirene for the SIRET, BODACC for the watch, an aggregator if the KYC file requires it.
Yes, but in ODSQL, typically a where on the registre field, not via GET /entreprise/{siren}. The field format is not guaranteed uniform (bare SIREN, RCS prefix, spaces). A filter that is too strict misses notices; one that is too wide matches badly. We test the rule on a sample before freezing it, and we never auto-create a customer record from a notice: homonyms, multiple establishments, masked natural persons.
No. BODACC publishes a notice on a dateparution. The judgment may be several days earlier. An alert « on the morning of the judgment » is not tenable. What the connector does is alert on publication day, with a link to the original notice. For a credit tool, that already ends the manual quarterly review. Promising more is selling a live register that does not exist. For a credit tool, publication-day is already the end of the manual quarterly review. We write that into the scope, not a live-register promise.
A BODACC integration project?
Let's talk. 30 minutes to scope the need, check what the DILA instance actually allows, and tell you frankly what is feasible.
Discuss my BODACC project