Germany Insolvency Register API
Insolvency proceedings from the German insolvency announcements register. You get clean, structured records with the source registry attached - keyed off the HRB identifier.
Prefer a file in your inbox? We can run this for you every morning and send the new records as a file - nothing to set up or keep running. German insolvency notices for a watchlist · get a free one-day sample.
- →Structured JSON, not HTML or PDFs
- →Source registry attached to every record
- →Read live at query time - current filings
- →Queried by HRB
What the Insolvenzbekanntmachungen API costs
$0.0045 per name searched
$0.0009 per insolvency publication
plus an actor-start charge of $0.00005 once per run (one per GB of memory, minimum one).
No subscription and no minimum.
$0.005 per answered call
$0.004 when nothing is on file. Insolvency publications: proceedings, court, case reference, type, status and dates, link to the official notice.
Order an API key →Apify rates in USD for the BRONZE tier, synced from Apify's pricing API. Higher Apify plans pay less.All prices
How to query Insolvenzbekanntmachungen
| Parameter | What it does |
|---|---|
| name | string | Company name or surname. Contains-match by default. |
| watchlist | array | A list of names to check in one run (the monitoring use case). Overrides name. |
| firstName | string | Optional first name, to narrow an individual-debtor search. |
| city | string | Optional seat / place of residence to narrow the search. |
| state | string | Optional German state (Bayern/BY, Nordrhein-Westfalen/NW, ...) - narrows a broad term. |
| exactMatch | boolean | Off (default) = contains-search; on = match the term exactly. |
| dateFrom / dateTo | string | Publication-date window (YYYY-MM-DD). Default: last two weeks. |
| subject | string | Optional filter by decision type (openings, dismissals for lack of assets, residual-debt-discharge, ...). |
| maxResults | integer | Cap on exported publications (default 200). Each publication is billed, so this also caps the per-publication cost. |
| includeNoticeDetails | boolean | Off (default). On = open each publication and add the administrator (name, address, phone, email), claims deadline, opening date, review hearing and, for companies, the full text. |
Sample record (JSON, people masked)
{
"publicationDate": "27.02.2026",
"publicationDateISO": "2026-02-27",
"caseNumber": "1542 IN 1356/20",
"court": "München",
"debtorName": "…",
"debtorType": "company",
"seat": "München",
"register": "München, HRB 223366",
"registerCourt": "München",
"registerType": "HRB",
"registerNumber": "223366",
"matchedName": "Wirecard",
"jurisdiction": "DE",
"source": "Insolvenzbekanntmachungen (Bund-Länder-Justizportal)",
"sourceUrl": "https://neu.insolvenzbekanntmachungen.de/ap/suche.jsf",
"retrievedAt": "2026-07-02T00:00:00.000Z"
} What it does not do
- The register caps any single search at 1,000 matches; a term that is too broad is reported back so you can refine it (fuller name, add a state, or a shorter date range).
- Targeted name searches return matches from any date range; the two-week default keeps broad terms fast. Widen dateFrom for a historical check.
- Query-driven, not a bulk copy of the register - by design this is for targeted checks.
Insolvenzbekanntmachungen (Germany) does not offer a clean public API for programmatic queries. getregdata reads the official source directly and returns structured JSON, keyed off the HRB identifier - so you get API-like access without an official endpoint.
Install the getregdata agent skills or MCP server, or run the regdata/germany-insolvency-scraper actor on Apify. Query by HRB or company name and receive structured, source-attributed records. It is free to install; you pay per result on Apify.
Insolvency proceedings from the German insolvency announcements register.
Not ready to run it yourself? Tell us which companies or filters you need. We run it once and send you the file, and a quote if you want it regularly. No newsletter, no sales calls.
Your request is in our inbox. We reply within one business day, from [email protected].
The form could not send just now - nothing is lost. Send it as an e-mail instead (your text is already filled in), or write to [email protected].
Prefer e-mail? [email protected] · We use your details only to answer you. Privacy