BODACC Insolvency Monitor 🇫🇷 (procédures collectives alerts) avatar

BODACC Insolvency Monitor 🇫🇷 (procédures collectives alerts)

Pricing

from $3.50 / 1,000 notice founds

Go to Apify Store
BODACC Insolvency Monitor 🇫🇷 (procédures collectives alerts)

BODACC Insolvency Monitor 🇫🇷 (procédures collectives alerts)

Track French insolvency filings on the official BODACC open-data feed. Watch companies by SIREN, sweep every new redressement judiciaire, liquidation judiciaire or sauvegarde, and get only what is new since your last run. No API key. Platform usage included.

Pricing

from $3.50 / 1,000 notice founds

Rating

0.0

(0)

Developer

Tagada Data

Tagada Data

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

BODACC Insolvency Monitor: French Collective Procedure Alerts

Watch French companies for insolvency filings and get back only what is new since your last run: every redressement judiciaire, liquidation judiciaire and sauvegarde, straight from the official BODACC feed. Give it a SIREN watchlist or a department, schedule it, and it reports (and charges) only for genuinely new filings, not the same list every day. Data comes straight from the official BODACC open-data API, no key required.

Built for credit and risk teams, collections and recovery desks, trade insurers, and B2B sales and prospecting teams who need to know when a customer, supplier or lead enters a formal procedure (works out of the box via API and MCP).

Why this actor

  • Watch specific companies: give it a SIREN or SIRET watchlist and get notified the day a filing appears against any of them, the same monitoring pattern credit-scoring vendors sell as a paid product, without the subscription.
  • Or sweep the whole feed: leave the watchlist empty and get every new collective procedure published, filterable by department and by procedure type.
  • One feed, a real diff: BODACC's own site and raw export hand you the same records every time you look and leave deduplication to you. This one keeps a persistent memory of what it has already seen and returns only notices published since your last run.
  • Categorized, not just dumped: each notice is classified as liquidation, redressement or sauvegarde from the court ruling text, so you can filter a full sweep down to the outcome you care about.
  • Official source, no key, no scraping: every field comes from the BODACC open-data API. No login, no third-party mirror.
  • Flat schema, no JSON spelunking: SIREN, company name, procedure category, court, ruling detail, department and city as plain columns, plus a direct link to the notice.
  • Monitor mode with a Slack-compatible webhook digest: schedule it and get pinged only when a company on your watchlist actually gets a new filing.
  • Fair pricing: you pay per notice actually returned. A quiet day on a scheduled watchlist costs nothing beyond the flat run fee.

Use cases

  • Credit and risk teams: put your customer and supplier SIREN numbers on a watchlist and get an alert the day one of them enters redressement or liquidation, before it shows up anywhere else.
  • Collections and recovery: know the moment a debtor files, so you can act while there is still something to recover.
  • Trade insurers and factoring: monitor your insured or financed book against new collective procedures as part of ongoing exposure checks.
  • B2B sales and prospecting: distressed companies are also companies that need help. Sweep new liquidations and redressements by department to build a targeted outreach list.
  • AI agents: plug it into Claude, Cursor or any MCP client and ask, "any new liquidation judiciaire filings in Paris this week?"

Input

{
"sirens": ["552100554"],
"sinceDays": 7,
"maxResults": 50
}

Watch a full department instead, filtered to the two most severe outcomes:

{
"departements": ["75", "92"],
"procedureTypes": ["liquidation", "redressement"],
"sinceDays": 7,
"monitorMode": true,
"webhookUrl": "https://hooks.slack.com/services/xxx/yyy/zzz"
}

sirens takes SIREN or SIRET numbers (a 14-digit SIRET is truncated to its SIREN automatically, spaces and dots are stripped). departements takes French department codes such as 75, 92, 2A or 971. Leave both empty to sweep every new collective procedure nationwide. procedureTypes narrows to liquidation, redressement and/or sauvegarde; leave it empty to keep every notice, including rulings that do not clearly state one of the three (plan modifications, closures and similar, still returned with a procedureCategory so you can see what they are). sinceDays and maxResults bound the run.

Output (one record per new or matched notice)

{
"id": "A202601341192",
"siren": "843905241",
"companyName": "LIMA DE ARAUJO, Flavia, LIMA DE ARAUJO (EI)",
"procedureCategory": "liquidation",
"judgmentNature": "Jugement de clôture pour insuffisance d'actif",
"judgmentDate": "2026-07-08",
"judgmentDetail": "Jugement prononçant la clôture de la procédure de liquidation judiciaire pour insuffisance d'actif.",
"noticeType": "Avis initial",
"court": "Greffe du Tribunal de Commerce de Bourg-en-Bresse",
"departement": "01",
"departementName": "Ain",
"region": "Auvergne-Rhône-Alpes",
"city": "Certines",
"postalCode": "01240",
"publicationDate": "2026-07-17",
"url": "https://www.bodacc.fr/pages/annonces-commerciales-detail/?q.id=id:A202601341192",
"changeType": null,
"retrievedAt": "2026-07-17T19:45:51.771Z"
}
FieldMeaning
idThe notice's BODACC announcement ID
sirenThe company's SIREN number
companyNameCompany or trader name (commercant)
procedureCategoryliquidation, redressement, sauvegarde or other
judgmentNatureThe ruling's stated nature, in French, as published
judgmentDateThe ruling's date, as published (formatting varies by year)
judgmentDetailThe ruling's full detail text: administrator, deadlines and similar
noticeTypeNotice type, e.g. Avis initial, Avis d'annulation
courtThe commercial court (tribunal) that issued the ruling
departement / departementNameFrench department code and name
regionRegion name
city / postalCodeCompany location
publicationDateDate the notice was published in BODACC
urlDirect link to the notice on bodacc.fr
changeTypeMonitor mode: new; null on one-off runs
retrievedAtWhen this run fetched the notice

On a one-off run (monitorMode off) you get every match with changeType set to null. In monitor mode the first run seeds the baseline and reports everything as new; later runs return only notices published since.

Pricing

Pay per event, no subscription. Users on higher Apify plans get automatic discounts.

EventPriceWhen
Run started$0.001Flat, once per run
Notice found$0.005Per new/matched notice returned with its data
Digest sent$0.03Monitor mode only, per Slack/webhook digest actually posted

A thousand notices costs $5, and in monitor mode a quiet watchlist costs almost nothing: the persistent seen-set means you are never billed twice for the same notice, so a scheduled run that finds nothing new only pays the tiny run fee. That is the difference from a raw export that bills you for the whole result set on every run.

FAQ

How do I get alerted when one of my customers files for insolvency? Put their SIREN numbers in sirens, turn on monitorMode, add a Slack webhook URL and schedule the actor. You get a digest only when one of them actually gets a new BODACC filing, and you are only charged for new notices.

What counts as a collective procedure? BODACC's own category (familleavis: collective) covering the formal French insolvency and restructuring procedures: redressement judiciaire, liquidation judiciaire and procédure de sauvegarde, plus the rulings that follow them (plan modifications, closures, conversions and annulments). This actor watches that whole category and tags each notice with the outcome it belongs to.

Can I just watch new liquidations in a region? Yes. Set departements to the codes you want and procedureTypes to ["liquidation"], and schedule it. You get every new liquidation judiciaire filed in those departments as it publishes.

Is BODACC data free? The data is public and the official BODACC API is keyless and open, so there is no login, no scraping and no third-party aggregator. You pay only for this actor's convenience: the SIREN watchlist, the diffing, the flat schema and the webhook alerts.

How is this different from just querying the API myself? The API returns the full matching set on every call, and the ruling detail is buried in an encoded field you have to parse yourself to know what actually happened. This actor decodes it, classifies it, and remembers what it already showed you, returning only notices published since, tagged new. That is the difference between a raw feed and a monitor.

Does it work with AI agents? Yes. Like every Apify actor it is exposed via REST API and MCP, so Claude, Cursor and similar tools can call it directly, for instance to answer "has this SIREN filed for liquidation this year?"


Something missing?

If you need an extra field, another source, or a different output, open an issue on this Actor and describe it. I read every request and small additions usually ship within days. More monitors and data Actors are on my profile, including the Federal Register monitor, the ClinicalTrials.gov monitor, and a Companies House monitor.

Keywords: BODACC, BODACC API, procédure collective, redressement judiciaire, liquidation judiciaire, procédure de sauvegarde, SIREN monitor, SIRET lookup, French company insolvency, insolvency monitoring France, credit risk monitoring, business bankruptcy alerts France, trade credit insurance, collections monitoring, B2B prospecting distressed companies, tribunal de commerce, BODACC for AI agents, MCP.