# Austria Insolvency & Court Publications Scraper (`regdata/austria-ediktsdatei-scraper`) Actor

Scrape Austrian insolvency data from the Ediktsdatei - bankruptcies, reorganizations, debt settlements, court auctions, and Firmenbuch announcements. Official court publications with no API alternative.

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

## Pricing

from $3.00 / 1,000 insolvency records

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

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#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

## Austria Insolvency & Court Publications Scraper | Osterreichische Ediktsdatei

Screen Austrian insolvency proceedings - bankruptcies (Konkursverfahren), reorganizations (Sanierungsverfahren), and debt settlements (Schuldenregulierungsverfahren) - from the official **Ediktsdatei** court database, as structured JSON. The official data feed requires an IWG government license and a formal application; this actor is the pay-per-use, no-paperwork alternative to the same court-published data.

**No login, no API key, nothing to configure** - a name or filter in, structured insolvency records out.

### What data do you get?

One record per court publication:

```json
{
  "debtorName": "SIGNA Development Selection AG",
  "caseNumber": "28 S 8/24h",
  "court": "Handelsgericht Wien",
  "proceedingType": "Konkursverfahren",
  "status": "Eroeffnung",
  "publicationDate": "15.01.2024",
  "administrator": "Dr. Andrea Gisinger, Rechtsanwaltin",
  "details": "Full publication text...",
  "creditorMeetingDate": "12.03.2024 um 09:00",
  "filingDeadline": "28.02.2024",
  "sourceUrl": "https://edikte.justiz.gv.at/edikte/id/idedi8.nsf/..."
}
```

| Field | Description |
|-------|-------------|
| `debtorName` | Debtor - person or company (Schuldner) |
| `caseNumber` | Court case number / Aktenzeichen |
| `court` | Court name (e.g. "Handelsgericht Wien") |
| `proceedingType` | Konkursverfahren, Sanierungsverfahren, or Schuldenregulierungsverfahren |
| `status` | Proceeding status (Eroeffnung, Aufhebung, etc.) |
| `publicationDate` | Date of publication (DD.MM.YYYY) |
| `administrator` | Insolvency administrator (Masseverwalter) name |
| `details` | Full text of the publication |
| `creditorMeetingDate` / `filingDeadline` | Creditor meeting date and claim-filing deadline, where mentioned |
| `sourceUrl` | Direct URL to the publication |

### How much does it cost?

**Pay per result** - you are not charged for Apify platform usage, only per record. The price drops on higher Apify subscription tiers.

| Volume | Cost |
|--------|------|
| Start cost | $0.005 |
| Per result | $0.005 |
| ~100 results | ~$0.51 |
| ~1,000 results | ~$5.01 |

Apify's $5 monthly free credit covers ~1,000 records. One-off counterparty checks stay free; recurring credit-risk watchlists (~2,000 records/month ≈ ~$10 gross, ~$5 net after the credit) are where you cross into paid use. Commercial insolvency-monitoring feeds run into the hundreds per month for the same court-published data.

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

Data comes from [edikte.justiz.gv.at](https://edikte.justiz.gv.at/), the official court-publication database operated by the Austrian Federal Ministry of Justice. It is a **public register** published by law (Ediktsdateigesetz) for transparency and creditor protection, covering all 9 federal states and all Austrian courts. No authentication or access control is bypassed. You remain responsible for lawful, GDPR-compliant use downstream.

### How do I use it?

Click **Try it** and paste this input:

```json
{ "searchQuery": "Benko", "proceedingType": "all", "maxResults": 20 }
```

Search by debtor name (min. 3 characters), or browse a publication window - e.g. every insolvency published in Vienna in the first half of August (`{ "state": "Wien", "dateFrom": "2026-08-01", "dateTo": "2026-08-20", "maxResults": 25 }`).

**Set `dateFrom` and `dateTo` whenever you are browsing rather than searching by name.** The register can filter on publication date itself, so a date window is the difference between reading a handful of pages and reading thousands. It also changes what you get back: without a date window and without a `searchQuery` there is nothing for the register to narrow on, and the actor falls back to a broad debtor query that returns only companies with "GmbH" in the name - no sole traders, no partnerships, and no private individuals in a Schuldenregulierungsverfahren. The run log says so when this happens.

### Input options

| Parameter | Type | Required | Default | Description |
|-----------|------|----------|---------|-------------|
| `searchQuery` | string | No | - | Debtor or company name (min. 3 characters) |
| `proceedingType` | string | No | `all` | Konkursverfahren, Sanierungsverfahren, Schuldenregulierungsverfahren, or all |
| `court` | string | No | - | Filter by court name (e.g. "Handelsgericht Wien") |
| `state` | string | No | `all` | Austrian federal state (Bundesland) |
| `dateFrom` / `dateTo` | string | No | - | Publication date range (YYYY-MM-DD). Applied by the register itself - the one filter that makes a browse run cheap. Strongly recommended. |
| `entryType` | string | No | `all` | Initial entries, changes, or all |
| `maxResults` | integer | No | 100 | Max matching records (0 = unlimited). `proceedingType` is checked per edict, so filtering by it can read more pages than this number. |

### What you can do with it

- **Credit-risk screening** - check whether an Austrian customer, supplier, or partner is insolvent before extending terms.
- **Due diligence** - verify a target company before an M\&A transaction or investment.
- **Supplier monitoring** - schedule runs to detect insolvency proceedings for key suppliers early.
- **Debt recovery** - track filing deadlines (Anmeldefrist) and creditor-meeting dates so you never miss one.
- **KYC / AML** - screen Austrian business partners against insolvency records.

### Run it from code

```bash
## cURL - start a run and get the dataset back
curl -X POST "https://api.apify.com/v2/acts/regdata~austria-ediktsdatei-scraper/run-sync-get-dataset-items?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "searchQuery": "Benko", "maxResults": 20 }'
```

```javascript
// Node.js - apify-client
import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('regdata/austria-ediktsdatei-scraper').call({ searchQuery: 'Benko', maxResults: 20 });
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/austria-ediktsdatei-scraper").call(run_input={"searchQuery": "Benko", "maxResults": 20})
items = client.dataset(run["defaultDatasetId"]).list_items().items
```

### Integrations

Runs anywhere Apify does: call it from the **REST API**, **schedule** a daily insolvency watchlist, 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 Ediktsdatei?** Yes. It is a public register published by law for transparency and creditor protection. No access control is bypassed. Use the data lawfully for credit-risk / KYB / due-diligence purposes.

**Do I need an IWG license or an API key?** No. The official data feed needs an IWG license and a formal application; this actor reads the free public pages, so no license and no key - just an Apify account.

**How do I monitor for new insolvencies?** Schedule a run with your proceeding-type / state filters (or a name watchlist), and pull new publications as they appear.

**What are the proceeding types?** Konkursverfahren (bankruptcy), Sanierungsverfahren (reorganization), Schuldenregulierungsverfahren (debt settlement).

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

### Limitations

- Name searches require at least 3 characters.
- Results per search follow the Ediktsdatei's own pagination limits; narrow with a state or date range for large sweeps.
- The source may change its page structure without notice.

### 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](https://apify.com/regdata/germany-insolvency-scraper) · [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 (this actor)** · [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)

### Informationen auf Deutsch

#### Was ist dieser Actor?

Dieser Actor durchsucht die **Ediktsdatei** (edikte.justiz.gv.at) - die offizielle osterreichische Datenbank fur gerichtliche Bekanntmachungen: alle Insolvenzverfahren (Konkurs, Sanierung, Schuldenregulierung) in Osterreich. Das Justizministerium bietet einen Datenfeed an, dieser erfordert jedoch eine **IWG-Lizenz** mit formalem Antragsverfahren. Dieser Actor liefert strukturierte JSON-Daten, pay-per-use, ohne Lizenzvertrag und ohne Anmeldung.

#### Fur wen?

- **Kreditrisiko-Manager** - Uberwachung der Zahlungsfahigkeit von Kunden und Lieferanten.
- **Due-Diligence-Teams** und **Kanzleien** - Prufung von Zielunternehmen, Aktenzeichen und Masseverwaltern.
- **Compliance-Abteilungen** - KYC/AML-Screening gegen Insolvenzregister.
- **Inkassounternehmen** - Uberwachung von Anmeldefristen und Glaubigerversammlungen.

#### Welche Daten?

Schuldnername, Aktenzeichen, Gericht, Verfahrensart, Verfahrensstand, Masseverwalter, Termin der Glaubigerversammlung, Anmeldefrist und den vollstandigen Bekanntmachungstext. Keine Abos - Sie zahlen nur pro Ergebnis.

***

### Ediktsdatei - Osterreichische Insolvenzbekanntmachungen

Automatisierter Zugriff auf die Ediktsdatei der osterreichischen Justiz. Insolvenzverfahren, Sanierungsverfahren, Schuldenregulierungen. Strukturierte JSON-Daten, pay-per-use, ohne IWG-Lizenz. Ideal fur Kreditrisikoanalyse, Insolvenzmonitoring und Due Diligence in Osterreich.

# Actor input Schema

## `searchQuery` (type: `string`):

Name of the debtor or company to search for (minimum 3 characters). Partial match supported. | Name des Schuldners oder Unternehmens (mindestens 3 Zeichen).

## `proceedingType` (type: `string`):

Type of insolvency proceeding to filter. 'all' returns all types. | Art des Insolvenzverfahrens. 'all' gibt alle Verfahrensarten zuruck.

## `court` (type: `string`):

Filter by court name (e.g. 'Handelsgericht Wien', 'Landesgericht Linz'). Leave empty for all courts. | Nach Gericht filtern. Leer lassen fur alle Gerichte.

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

Filter by Austrian federal state. | Nach Bundesland filtern.

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

Only return edicts published on or after this date (YYYY-MM-DD). Setting it is strongly recommended: it is the only filter the register applies server-side, so it is what keeps a browse-style run short, and it removes the need for the GmbH fallback query - without it a run with no searchQuery returns ONLY debtors whose name contains 'GmbH'. | Nur Veroeffentlichungen ab diesem Datum.

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

Only return edicts published up to this date (YYYY-MM-DD). Applied per edict, not by the register, so a narrow window costs one page fetch per candidate. | Nur Veroeffentlichungen bis zu diesem Datum.

## `entryType` (type: `string`):

Filter by entry type: 'initial' for new proceedings, 'changes' for updates, 'all' for both. | Ersteintrage, Anderungen, oder beides.

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

Maximum number of matching records to return. Default: 100. Set to 0 for unlimited. This caps matches, not work: dateTo and proceedingType are checked per edict, so reaching the cap can require many more page fetches than the cap itself. | Maximale Anzahl der Ergebnisse.

## `proxyConfiguration` (type: `object`):

Optional. The register rate-limits by IP, so a proxy is worth setting for large or unbounded runs (maxResults 0, wide date windows, or state=all). Bounded runs with a dateFrom/dateTo window make few enough requests that a direct connection is fine. Verified 2026-08-25: direct, Apify Proxy datacenter, and residential with country AT all reach the register. | Optional. Apify Proxy fuer grosse Abfragen empfohlen.

## Actor input object example

```json
{
  "proceedingType": "all",
  "state": "all",
  "entryType": "all",
  "maxResults": 100
}
```

# Actor output Schema

## `searchResults` (type: `string`):

Insolvency records with debtor name, case number, court, proceeding type, status, administrator, creditor meeting dates, filing deadlines, and full publication text.

# 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 = {
    "searchQuery": ""
};

// Run the Actor and wait for it to finish
const run = await client.actor("regdata/austria-ediktsdatei-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 = { "searchQuery": "" }

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

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

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

```

## CLI example

```bash
echo '{
  "searchQuery": ""
}' |
apify call regdata/austria-ediktsdatei-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,regdata/austria-ediktsdatei-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

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