Germany Insolvency Register Search (Insolvenzbekanntmachungen) avatar

Germany Insolvency Register Search (Insolvenzbekanntmachungen)

Pricing

from $28.00 / 1,000 insolvency search sessions

Go to Apify Store
Germany Insolvency Register Search (Insolvenzbekanntmachungen)

Germany Insolvency Register Search (Insolvenzbekanntmachungen)

Search Germany's official insolvency register (Insolvenzbekanntmachungen) by company or debtor name. Get court, case number, publication date, seat and the Handelsregister reference. No API key.

Pricing

from $28.00 / 1,000 insolvency search sessions

Rating

0.0

(0)

Developer

getregdata

getregdata

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

Search the official German insolvency register - Insolvenzbekanntmachungen, the Bund-Länder justice portal where every German court publishes its insolvency proceedings - by company or debtor name, and get clean structured JSON: court, case number (Aktenzeichen), publication date, debtor name and seat, and - for companies - the commercial-register reference (e.g. Koblenz, HRB 25603) that cross-links straight to the Handelsregister. There is no open public API for this register - this actor is the keyless API for it.

No login, no API key, nothing to configure - just send a name.

An insolvency publication is the single most important negative signal in German B2B: it tells you a company (or a sole trader) is in bankruptcy or restructuring, or has had a filing dismissed for lack of assets. Screening a counterparty against it is essential for credit risk, KYB/KYC, onboarding, and debtor monitoring.

What data do you get?

One record per insolvency publication:

{
"publicationDate": "27.02.2026",
"publicationDateISO": "2026-02-27",
"caseNumber": "1542 IN 1356/20",
"court": "München",
"debtorName": "Wirecard Global Sales GmbH",
"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"
}

For individuals, debtorName is "Surname, Firstname" and is split into debtorLastName / debtorFirstName, with register fields null. For companies, registerCourt + registerType + registerNumber are the direct link to the Handelsregister record.

How much does it cost?

Pay per search - you are not charged for Apify platform usage, only per search performed. See the Pricing tab on this page for the current figure. The free Apify plan returns a small preview; upgrade to a paid plan for full, uncapped searches. No subscription, no minimum.

Data comes from the official Insolvenzbekanntmachungen portal at neu.insolvenzbekanntmachungen.de, operated by the German federal and state justice administrations. Insolvency publications are a public disclosure open to anyone; this actor reads the open public search and does not log in or bypass any paywall or access control. Every record is stamped with its source URL and retrieval timestamp. Use the data lawfully (KYB, credit risk, counterparty due diligence, B2B) - this is not a consumer report, so do not use it for consumer-credit decisions.

How do I use it?

Click Try it and search by a company or debtor name (contains-match, last two weeks by default):

{ "name": "Wirecard" }

Check for older insolvencies by widening the window ({ "name": "Wirecard", "dateFrom": "2020-01-01" }), or monitor a watchlist on a daily schedule to catch new publications for your counterparties:

{ "watchlist": ["Muster Bau GmbH", "Beispiel Handel AG", "Nord Logistik GmbH"] }

Input options

FieldTypeDescription
namestringCompany name or surname. Contains-match by default.
watchlistarrayA list of names to check in one run (the monitoring use case). Overrides name.
firstNamestringOptional first name, to narrow an individual-debtor search.
citystringOptional seat / place of residence to narrow the search.
statestringOptional German state (Bayern/BY, Nordrhein-Westfalen/NW, ...) - narrows a broad term.
exactMatchbooleanOff (default) = contains-search; on = match the term exactly.
dateFrom / dateTostringPublication-date window (YYYY-MM-DD). Default: last two weeks.
subjectstringOptional filter by decision type (openings, dismissals for lack of assets, residual-debt-discharge, ...).
maxResultsintegerCap on exported publications (default 200).

Pairs with the Handelsregister (the full German due-diligence flow)

This actor is the debtor / insolvency check half of a German KYB workflow. Chain it with the identity half:

  1. Germany Handelsregister Scraper - confirm the company, its officers (with dates of birth), and registration (HRB/HRA + register court).
  2. This actor - screen that same company name against the insolvency register, and match the registerCourt + registerNumber back to the Handelsregister record.

The same pattern powers the EU suite: source the party (registry + UBO), then check the party (insolvency + adverse media).

What you can do with it

  • Credit risk & onboarding - before extending terms, check whether a customer or supplier is in insolvency, restructuring, or was dismissed for lack of assets.
  • KYB / KYC - screen a counterparty (or officers/UBOs surfaced by the other registry actors) against the German insolvency register.
  • Debtor & portfolio monitoring - run a watchlist on a daily schedule and get alerted to new insolvency publications.
  • Legal & collections - find the court, case number, and register reference for a proceeding.

Run it from code

# cURL - start a run and get the dataset back
curl -X POST "https://api.apify.com/v2/acts/regdata~germany-insolvency-scraper/run-sync-get-dataset-items?token=YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{ "name": "Wirecard" }'
// Node.js - apify-client
import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('regdata/germany-insolvency-scraper').call({ name: 'Wirecard' });
const { items } = await client.dataset(run.defaultDatasetId).listItems();
# Python - apify-client
from apify_client import ApifyClient
client = ApifyClient("YOUR_TOKEN")
run = client.actor("regdata/germany-insolvency-scraper").call(run_input={"name": "Wirecard"})
items = client.dataset(run["defaultDatasetId"]).list_items().items

Integrations

Runs anywhere Apify does: call it from the REST API, schedule a daily watchlist monitor, pipe results into n8n / Make / Zapier, or use it from any MCP client (Claude, Cursor) via mcp.apify.com.

FAQ

Is it legal to scrape the insolvency register? Yes. Insolvency publications are a public disclosure open to anyone. This actor reads the open public search only. Use the data lawfully for B2B / credit-risk / due-diligence purposes; it is not a consumer report.

Do I need an account or API key? No. No login, no key, nothing to configure - just an Apify account.

How do I monitor a set of counterparties? Pass a watchlist array and schedule a daily run - you get any new insolvency publications for those names.

What does an empty result mean? That the name has no insolvency publication in the window - a clean answer for a credit check, not a failure. Crucially, it means that and nothing else: an empty result is only ever reported when the register actually answered. If the register does not answer, the run fails (non-zero exit) and says so; names it could not screen are named in the status message and written to an UNSCREENED key-value record, and are not charged. A term the register rejects as matching too many publications is reported as exactly that - never as "no insolvencies", which would be the opposite of the truth. And names never reached because maxResults ran out are listed as UNKNOWN rather than passed off as clear. An outage will never be handed to you as an all-clear.

How do I link an insolvency to the company record? For companies, use registerCourt + registerNumber to look the company up in the Handelsregister actor.

What export formats are supported? JSON, CSV, Excel, or XML, or read live via the API.

Limitations

  • 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.

Part of a suite of official government registry actors - no public API to build or maintain, pay per result, nothing to configure.

CountryActors
PolandBDO · CRBR · KRS (financials) · EKW · KNF · KRS (board) · KRZ · MSiG · KYB check · PEP (Sejm) · REGON (sites) · REGON · UOKiK
GermanyInsolvenzbekanntmachungen (this actor) · Handelsregister
SpainBORME · Registro Mercantil · Registro Público Concursal
ItalyINI-PEC · Registro Imprese
AustriaEdiktsdatei · WKO
FranceSociete.com
BelgiumKBO / BCE
CzechiaISIR
SlovakiaRPVS
CyprusDRCOR
IrelandCRO
PortugalPublicações MJ
NigeriaCAC
ColombiaRUES
USACalifornia SoS · California UCC
UAEADGM
GlobalAdverse media

Common combinations: company register -> UBO -> insolvency/debtors -> adverse media is the standard KYB/onboarding chain.

For Poland that whole chain is one call: Poland KYB Risk Check takes a NIP or KRS and returns identity, beneficial owners and insolvency - screened against the company and every beneficial owner - as a single verdict, billed once per completed check.

Full suite: apify.com/regdata · Callable from any MCP client via mcp.apify.com