German Insolvency API — Insolvenzbekanntmachungen
Pricing
from $0.005 / actor start
German Insolvency API — Insolvenzbekanntmachungen
German insolvency API. Monitor official company insolvency notices (Insolvenzbekanntmachungen, §9 InsO) from neu.insolvenzbekanntmachungen.de. Filter by company, court, date & notice type; consumer (Verbraucher) cases excluded. JSON output for KYB, credit risk & Bonität monitoring. Unofficial.
Pricing
from $0.005 / actor start
Rating
0.0
(0)
Developer
Patrick Lierse
Maintained by CommunityActor stats
0
Bookmarked
3
Total users
0
Monthly active users
6 days ago
Last modified
Categories
Share
German Insolvency Notices Monitor (Company / Regelinsolvenz)
Unofficial Apify actor that monitors official German company insolvency
announcements (Insolvenzbekanntmachungen, published under §9 InsO) from
neu.insolvenzbekanntmachungen.de.
Not affiliated with or endorsed by any German authority. Data source
attribution: neu.insolvenzbekanntmachungen.de (official announcements, §5 UrhG).
Example
Input
{"court": "München","noticeType": "eroeffnung","maxResults": 1}
Output (one dataset item per company notice, trimmed)
{"companyName": "CL Capital Investments GmbH","court": "München","caseNumber": "1542 IN 1744/25","noticeType": "Eröffnung","noticeDate": "2026-06-12","registeredAddress": "Hettstedt","registerReference": "HRB 12345"}
(Each item also carries sourceUrl, cachedAt and dataSource. Consumer /
personal-debtor notices are never emitted — see below.)
Please read first
- What this is. This actor searches the official German insolvency portal by company name, insolvency court, publication-date range and notice type, and returns structured, company-only notices (court, case number, notice type, date, registered seat, register reference). It is a monitoring tool for counterparty, supplier and debtor risk.
- Unofficial tool — not affiliated with or endorsed by any German authority. The data comes from the official portal but this actor is an independent third-party tool. Notices may contain errors; verify against the source before relying on them.
- Public-data basis (§9 InsO) and robots.txt. Insolvency announcements are
published to the public by statute under §9 InsO and are freely readable in a
browser. The portal's
robots.txtdisallows the search path (it targets indexing crawlers of a session-bound JSF app, not statutory public-record lookups). By default the actor searches the portal; setrespectRobots: trueto strictly honour robots.txt, in which case the actor will refuse to search. Either way it never evades rate limits or anti-bot measures. - Company data only — no consumer / personal data (GDPR). Consumer (Verbraucher / "IK") notices and bare natural-person debtors are filtered out in code and never appear in the output; the Vorname (first-name) field is never searched and the free-text notice body is never fetched. If you process the output you become the data controller for it under the GDPR.
- Full legal basis. See ./COMPLIANCE.md for the complete Legitimate Interest Assessment (LIA) and design rules.
What it does
Searches the official portal by company name, insolvency court, publication date range, and notice type, and returns structured, company-only results. Use it to monitor counterparties, suppliers, and debtors for insolvency events (openings, dismissals for lack of assets, decisions in proceedings, …).
Company notices only — by design
This actor returns company / legal-entity insolvencies only. Consumer (Verbraucher / "IK") notices and bare natural-person debtors are filtered out in code and never appear in the output. The Vorname (first-name) search field is never used, and the free-text notice body is not fetched. See ./COMPLIANCE.md for the full design rule and Legitimate Interest Assessment.
Input
| Field | Type | Default | Notes |
|---|---|---|---|
companyName | string | — | Debtor name/keyword (Firma/Nachname). Optional. |
court | string | — | Insolvency court name, e.g. "München". Optional. |
dateFrom | string | 14 days ago | Publication date from, YYYY-MM-DD. |
dateTo | string | today | Publication date to, YYYY-MM-DD. |
noticeType | enum | All | Eröffnung, Abweisung mangels Masse, … (Gegenstand). |
maxResults | int | 20 | 1–100. |
respectRobots | bool | false | See "robots.txt" below. |
The portal lists at most 1000 hits per search and refuses to list beyond that — keep date ranges tight for broad (no-name) queries.
Output (one dataset item per notice)
{"companyName": "CL Capital Investments GmbH","court": "München","caseNumber": "1542 IN 1744/25","noticeType": "Eröffnung","noticeDate": "2026-06-12","registeredAddress": "Hettstedt","registerReference": "HRB 12345","sourceUrl": "https://neu.insolvenzbekanntmachungen.de/ap/suche.jsf","cachedAt": "2026-06-12T20:00:00.000Z","dataSource": "neu.insolvenzbekanntmachungen.de/ap"}
No persons / personal-debtor fields are ever emitted. sourceUrl is the search
page: individual notices are JSF postbacks with no stable GET URL.
Polite by construction
- 30 requests/hour hard limit (sliding window, persisted across runs).
- 12-hour cache — repeat queries cost zero HTTP requests.
- Audit log of every request, saved to the run's key-value store (
AUDIT_LOG). - No proxy rotation, captcha solving, or anti-bot evasion. If the portal signals automated access is unwelcome, the actor pauses rather than adapts.
robots.txt
By default the actor searches the portal (respectRobots: false). The data
is publicly mandated by §9 InsO and freely accessible in a browser, and the
portal's robots.txt disallows the search path only because it is aimed at
indexing crawlers of a POST-only, session-bound JSF app — not at statutory
public-record lookups.
Set respectRobots: true to strictly honour robots.txt. In that mode, because
the portal disallows the search path, the actor will not search: it logs a
clear explanation, returns zero results, exits cleanly (no crash, no charge for
results), and tells you to set respectRobots: false to run a search. The actor
never evades rate limits or anti-bot measures regardless of this setting. See
./TECHNICAL_SPEC.md and ./COMPLIANCE.md.
Pricing (pay-per-event)
This actor uses Apify's standard auto-charged events. Suggested prices, to be configured by the operator in the Apify Console → Monetization (not set here):
| Event | Suggested price |
|---|---|
apify-actor-start (auto, per run) | $0.005 |
apify-default-dataset-item (auto, per result) | $4.00 / 1000 |
A future deep-record event is reserved for fetching the full notice text but
is not wired up (the notice body carries personal data and isn't needed).
Local development
export PATH="$HOME/node20/bin:$PATH"npm installnpm test # offline + edge-case + rate-limit testsnode test/run-local.mjs '{"court":"München","noticeType":"eroeffnung","respectRobots":false}'
Support
- Questions, bug reports, data-subject requests: https://apify.com/pat1987/german-insolvency-notices-monitor/issues
- Operator contact: patrick.lierse@googlemail.com
Disclaimer
Unofficial tool. Insolvency data originates from the official portal and may contain errors; verify against the source before relying on it. Users who process the output assume their own controller responsibilities under GDPR.