Data sourcebodacc api

BODACC API for French commercial-announcement research

Search, retrieve and review official French BODACC commercial announcements through a source-backed AI-agent workflow.

dossaro lets an AI agent search official BODACC commercial announcements, preserve the notice and publication references, and retrieve or parse the official JSON, HTML or unit-PDF artifact where BODACC exposes it. BODACC is filing-event evidence, not a complete French company profile or ownership register.

Updated July 29, 2026

fr_bodacc
CompanyDocumentsFilingsRegulatory

RNE document parse depends on configured access.

Run this exact task

Install dossaro, then continue the research

The setup guide lets a capable agent add the remote MCP, start OAuth with the user and return to this task.

Install-and-run prompt
Review the dossaro MCP setup guide at https://dossaro.com/agent-setup/prompt.md, configure dossaro when possible, complete OAuth with the user, then perform this task: Search BODACC for this exact French company, SIREN, date range or commercial event; return the relevant official notices and available JSON, HTML or PDF evidence with publication dates, source references and limitations, without treating an event label as current ownership.

What the official source provides

The Bulletin officiel des annonces civiles et commerciales, or BODACC, publishes official French commercial notices. Its records can document company creations, modifications, sales and transfers, collective proceedings, accounts-related publications and other dated registry events.

BODACC exposes the official commercial-announcements search and an Opendatasoft records API. A record is event evidence: it identifies what was published, for which entity and on what date. It is not automatically the current legal state of the company.

That distinction matters in due diligence. A notice about an appointment, transfer or insolvency proceeding can change the review queue, but the analyst still needs the relevant company profile and any later notices before describing the present position. The company-register documents workflow explains how to keep the underlying artifact attached to the conclusion.

What dossaro adds

dossaro turns BODACC into a repeatable source operation for an AI agent. The agent can:

  • search commercial announcements by company, identifier, date or event context;
  • preserve the publication identifier and source URL returned by BODACC;
  • fetch the official structured record or HTML detail;
  • retrieve and parse a unit PDF when the public BODACC row exposes one;
  • keep the publication date, company identifiers and event label together;
  • return explicit no-result or source limitations instead of inventing a filing.

This is a publication-research capability. dossaro does not convert BODACC event labels into a shareholder map, beneficial-owner determination or full Registre national des entreprises profile.

For a target-list assignment, use BODACC as one evidence lane inside M&A target screening, not as the only source for deciding whether a company passes diligence.

Agent workflow

  1. Resolve the target's exact legal name and SIREN when available.
  2. Define the relevant event, publication date or review window.
  3. Search BODACC and retain all plausible records rather than selecting by name alone.
  4. Match the notice to the target using identifiers, location and publication context.
  5. Fetch the returned JSON or HTML reference.
  6. Retrieve or parse a returned unit-PDF reference when the source exposes it.
  7. Record the notice category, publication date, official URL and any access limitation.
  8. Compare later notices and the current company profile before describing current status.

The same sequence can be repeated across a French longlist. For cross-border work, a BODACC publication can sit beside a Greek GEMI company and document result while both retain their source-native identifiers.

Evidence and outputs

Strong inputs include:

  • exact legal name;
  • SIREN or another returned company identifier;
  • event category or research question;
  • publication or transaction date range;
  • whether the assignment needs metadata, official text or an available PDF.
OutputResearch use
Publication identifierKeeps follow-up calls tied to the selected BODACC notice
Company identifiersDistinguishes similarly named French entities
Notice category and textDescribes the official commercial event that was published
Publication dateEstablishes the point in time represented by the notice
JSON, HTML or PDF referencePreserves the source artifact available for review
LimitationSeparates no result, unavailable artifact and unsupported inference

When the assignment begins from a global company-data product, the OpenCorporates alternative workflow explains when to move from an aggregated record into direct source evidence such as BODACC.

Coverage and limitations

  • BODACC is an official publication source, not the complete RNE company profile.
  • A notice records a dated event; a later publication can supersede its practical relevance.
  • Company-event, appointment and termination labels are not beneficial-ownership evidence.
  • Not every record exposes a public unit PDF; JSON or HTML can be the available artifact.
  • A name match without a SIREN or equivalent identifier can be ambiguous.
  • Empty search results do not prove that no relevant corporate event occurred.
  • dossaro does not provide official-register, legal, tax or investment advice.

Run this exact task

Install dossaro, then continue the research

The setup guide lets a capable agent add the remote MCP, start OAuth with the user and return to this task.

Install-and-run prompt
Review the dossaro MCP setup guide at https://dossaro.com/agent-setup/prompt.md, configure dossaro when possible, complete OAuth with the user, then perform this task: Search BODACC for this exact French company, SIREN, date range or commercial event; return the relevant official notices and available JSON, HTML or PDF evidence with publication dates, source references and limitations, without treating an event label as current ownership.

Capability graph