# Germany Insolvency Register Search (Insolvenzbekanntmachungen) (`regdata/germany-insolvency-scraper`) Actor

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.

- **URL**: https://apify.com/regdata/germany-insolvency-scraper.md
- **Developed by:** [getregdata](https://apify.com/regdata) (community)
- **Categories:** Lead generation, Automation, Agents
- **Stats:** 1 total users, 1 monthly users, 97.1% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $28.00 / 1,000 insolvency search sessions

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Germany Insolvency Register Search (Insolvenzbekanntmachungen)

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:

```json
{
  "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 run** - you are not charged for Apify platform usage, only one search-session fee per run. That fee is the same whether the run checks a single name or a full 100-name watchlist, so watchlist monitoring costs the same as a single lookup. See the **Pricing** tab on this page for the current figure. You are only charged once the register has actually answered - a run that the register blocks is not charged. The free Apify plan returns a small preview; upgrade to a paid plan for full searches. No subscription, no minimum.

### Is it legal, and where does the data come from?

Data comes from the official **Insolvenzbekanntmachungen** portal at [neu.insolvenzbekanntmachungen.de](https://neu.insolvenzbekanntmachungen.de/ap/suche.jsf), 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):

```json
{ "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:

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

### Input options

| Field | Type | Description |
|------|------|-------------|
| `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`). |

### 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](https://apify.com/regdata/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

```bash
## 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" }'
```

```javascript
// 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
## 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](https://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](https://apify.com/regdata/germany-handelsregister-scraper).

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

### Related actors

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

| Country | Actors |
|---|---|
| Poland | [BDO](https://apify.com/regdata/bdo-waste-registry-scraper) · [CRBR](https://apify.com/regdata/crbr-beneficial-owners-scraper) · [KRS (financials)](https://apify.com/regdata/poland-krs-financial-scraper) · [EKW](https://apify.com/regdata/ekw-ksiegi-wieczyste-scraper) · [KNF](https://apify.com/regdata/knf-registry-scraper) · [KRS (board)](https://apify.com/regdata/krs-fullnames-scraper) · [KRZ](https://apify.com/regdata/krz-debtor-scraper) · [MSiG](https://apify.com/regdata/msig-scraper) · [KYB check](https://apify.com/regdata/poland-kyb-check) · [PEP (Sejm)](https://apify.com/regdata/poland-parliamentary-pep-scraper) · [REGON (sites)](https://apify.com/regdata/polish-premises-prospector) · [REGON](https://apify.com/regdata/polish-regon-scraper) · [UOKiK](https://apify.com/regdata/uokik-clauses-scraper) |
| Germany | **Insolvenzbekanntmachungen (this actor)** · [Handelsregister](https://apify.com/regdata/germany-handelsregister-scraper) |
| Spain | [BORME](https://apify.com/regdata/borme-corporate-acts-scraper) · [Registro Mercantil](https://apify.com/regdata/spain-company-directory-scraper) · [Registro Público Concursal](https://apify.com/regdata/spain-concursal-scraper) |
| Italy | [INI-PEC](https://apify.com/regdata/italy-pec-lookup) · [Registro Imprese](https://apify.com/regdata/italy-registro-imprese-scraper) |
| Austria | [Ediktsdatei](https://apify.com/regdata/austria-ediktsdatei-scraper) · [WKO](https://apify.com/regdata/wko-business-directory-scraper) |
| France | [Societe.com](https://apify.com/regdata/societe-com-scraper) |
| Belgium | [KBO / BCE](https://apify.com/regdata/belgium-kbo-company-scraper) |
| Czechia | [ISIR](https://apify.com/regdata/czech-isir-insolvency-scraper) |
| Slovakia | [RPVS](https://apify.com/regdata/slovakia-rpvs-ubo-scraper) |
| Cyprus | [DRCOR](https://apify.com/regdata/cyprus-drcor-company-scraper) |
| Ireland | [CRO](https://apify.com/regdata/ireland-cro-company-scraper) |
| Portugal | [Publicações MJ](https://apify.com/regdata/portugal-corporate-acts-scraper) |
| Nigeria | [CAC](https://apify.com/regdata/nigeria-cac-company-scraper) |
| Colombia | [RUES](https://apify.com/regdata/colombia-rues-company-scraper) |
| USA | [California SoS](https://apify.com/regdata/california-sos-business-scraper) · [California UCC](https://apify.com/regdata/california-ucc-lien-scraper) |
| UAE | [ADGM](https://apify.com/regdata/uae-adgm-public-register-scraper) |
| Global | [Adverse media](https://apify.com/regdata/adverse-media-screener) |

**Common combinations:** company register -> [UBO](https://apify.com/regdata/crbr-beneficial-owners-scraper) -> [insolvency/debtors](https://apify.com/regdata/krz-debtor-scraper) -> [adverse media](https://apify.com/regdata/adverse-media-screener) is the standard KYB/onboarding chain.

For Poland that whole chain is one call: [Poland KYB Risk Check](https://apify.com/regdata/poland-kyb-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. The component registry lookups it runs bill as usual, plus a small orchestration fee.

> Full suite: [apify.com/regdata](https://apify.com/regdata) · Callable from any MCP client via [mcp.apify.com](https://mcp.apify.com)

# Actor input Schema

## `name` (type: `string`):

The debtor to look up: a company name (e.g. "Wirecard") or a person's surname. Matched as a contains-search across the official insolvency register. Leave empty when using a watchlist.

## `watchlist` (type: `array`):

A list of company names or surnames to check in one run (up to 100). Ideal for scheduled monitoring - run this Actor daily against your counterparties and get any new insolvency publications. Overrides the single "name" field when set. For more than 100 names, split them across several runs or scheduled tasks.

## `firstName` (type: `string`):

Optional first name, to narrow an individual-debtor search.

## `city` (type: `string`):

Optional city to narrow the search (matches the debtor's registered seat or place of residence).

## `exactMatch` (type: `boolean`):

Off (default): contains-search - the term is matched anywhere in the name. On: match the term exactly as typed (you may include the portal wildcard \* yourself).

## `state` (type: `string`):

Optional filter by German state - narrows the search and helps a broad term stay under the register's 1,000-match cap. Use a name ("Bayern", "Nordrhein-Westfalen") or a code ("BY", "NW").

## `dateFrom` (type: `string`):

Start of the publication-date window (YYYY-MM-DD). Defaults to two weeks ago. For a one-off historical check, widen this - a targeted name search returns matches from any date. Broad terms over long windows may hit the 1,000-match cap.

## `dateTo` (type: `string`):

End of the publication-date window (YYYY-MM-DD). Defaults to today.

## `subject` (type: `string`):

Optional filter by the type of decision within the proceeding.

## `maxResults` (type: `integer`):

Maximum publications to export across all queries in this run.

## Actor input object example

```json
{
  "name": "Bau",
  "exactMatch": false,
  "state": "NO_CODE",
  "subject": "NO_CODE",
  "maxResults": 200
}
```

# Actor output Schema

## `publications` (type: `string`):

Insolvency publication records in the default dataset.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "name": "Bau"
};

// Run the Actor and wait for it to finish
const run = await client.actor("regdata/germany-insolvency-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "name": "Bau" }

# Run the Actor and wait for it to finish
run = client.actor("regdata/germany-insolvency-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "name": "Bau"
}' |
apify call regdata/germany-insolvency-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=regdata/germany-insolvency-scraper",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/Sq3Tr2mrg5XlBMh3F/builds/a1qeVRd8UP5pAan09/openapi.json