# Brandenburg Case Law Search (Entscheidungsdatenbank) (`legaltech/gerichtsentscheidungen-brandenburg`) Actor

Search decisions of Brandenburg and joint Berlin-Brandenburg courts in the official decision database: ECLI, procedural history, Tenor, full text.

- **URL**: https://apify.com/legaltech/gerichtsentscheidungen-brandenburg.md
- **Developed by:** [Miguel González](https://apify.com/legaltech) (community)
- **Categories:** Automation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 results

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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

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

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

### Brandenburg Case Law Search (Entscheidungsdatenbank)

Searches decisions of the courts of Brandenburg and of the joint Berlin-Brandenburg courts (higher administrative, labour, social and fiscal courts) in the official decision database of the Brandenburg state law portal, with full-text search (AND natively; phrases, OR, NOT and \* wildcard verified locally), lookup by exact file number (Aktenzeichen) or ECLI, and filters by court (31 courts) and date range. Returns court and chamber, date, type, file number, ECLI, procedural history (Verfahrensgang), statutes, headnote (Leitsatz), operative part (Tenor), passages with margin numbers and optional full text.

### Use cases

- Search case law of the Brandenburg Higher Regional Court or the Berlin-Brandenburg Higher Administrative Court on an issue.
- Retrieve a decision by file number or ECLI.
- Get the operative parts of a court's decisions over a period.

### How to use (guide for AI agents)

- `court`: pick the exact title from the list (OLG Brandenburg, LG Potsdam…).
- Search terms in German joined by AND; phrases are verified locally.
- `fileNumbers`: exact match ("3 U 5/25" does not return "13 U 5/25").
- Every result includes `searchTerm` and `rank`; `passages` holds the paragraphs where the search terms appear, ready for LLM analysis.

### Input example

```json
{
    "searchTerms": ["\"fristlose Kündigung\" AND Zahlungsverzug"],
    "court": "OLG Brandenburg",
    "dateFrom": "2020-01-01",
    "maxResults": 20
}
```

### Output example (abridged)

```json
{
    "searchTerm": "\"fristlose Kündigung\" AND Zahlungsverzug",
    "rank": 1,
    "court": "OLG Brandenburg 3. Zivilsenat",
    "decisionType": "Urteil",
    "decisionDate": "2023-11-07",
    "fileNumber": "3 U 120/22",
    "ecli": "ECLI:DE:OLGBB:2023:1107.3U120.22.00",
    "tenor": "Die Berufung der Klägerin gegen das am 24.06.2022 verkündete Urteil ... wird zurückgewiesen...",
    "passages": ["I. Die Klägerin begehrt von dem Beklagten ..."],
    "url": "https://gerichtsentscheidungen.brandenburg.de/gerichtsentscheidung/..."
}
```

### Source

Only official sources are used (courts, ministries or the open data published by the courts themselves). Results are returned as published by the source.

### Proxy

No proxy is needed: the source is an official open service. If it starts blocking, enable `proxyConfiguration` (Apify RESIDENTIAL (DE) recommended, or your own `proxyUrls`). Requests then go through a sticky session (same IP, own cookies) with a Chrome TLS fingerprint (impit), and the IP is rotated on 403/429 or network errors.

# Actor input Schema

## `searchTerms` (type: `array`):

One search per item, full text, in German. Syntax: AND / OR / NOT, "exact phrase", parentheses, \* wildcard and -word (phrases, OR, NOT and wildcards are checked locally against the text).

## `fileNumbers` (type: `array`):

Retrieve decisions by exact file number, e.g. "3 U 5/25".

## `eclis` (type: `array`):

Retrieve decisions by ECLI.

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

Court of Brandenburg (or joint Berlin-Brandenburg court). Pick the exact title from the list.

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

Decision date, start of range (YYYY-MM-DD).

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

Decision date, end of range (YYYY-MM-DD).

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

Maximum decisions per search term. The portal pages 20 results at a time.

## `includeDetails` (type: `boolean`):

Opens each decision to add ECLI, statutes, procedural history, headnote and operative part.

## `passages` (type: `integer`):

Paragraphs (with margin numbers) containing the search terms.

## `includeFullText` (type: `boolean`):

Adds full operative part and reasons with margin numbers.

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

Optional. The source usually works without a proxy. If it blocks, use Apify RESIDENTIAL (DE) or your own proxyUrls; requests then use sticky sessions, IP rotation and a Chrome TLS fingerprint.

## Actor input object example

```json
{
  "searchTerms": [
    "Mietminderung AND Schimmel"
  ],
  "fileNumbers": [],
  "eclis": [],
  "court": "",
  "maxResults": 20,
  "includeDetails": true,
  "passages": 3,
  "includeFullText": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `results` (type: `string`):

Dataset of decisions returned by the search, one item per result. Main fields: searchTerm, court, decisionDate, decisionType, fileNumber, ecli, leitsatz, tenor, url. See the dataset schema for the full list of fields.

# 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 = {
    "searchTerms": [
        "Mietminderung AND Schimmel"
    ],
    "fileNumbers": [],
    "eclis": [],
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("legaltech/gerichtsentscheidungen-brandenburg").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 = {
    "searchTerms": ["Mietminderung AND Schimmel"],
    "fileNumbers": [],
    "eclis": [],
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("legaltech/gerichtsentscheidungen-brandenburg").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 '{
  "searchTerms": [
    "Mietminderung AND Schimmel"
  ],
  "fileNumbers": [],
  "eclis": [],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call legaltech/gerichtsentscheidungen-brandenburg --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,legaltech/gerichtsentscheidungen-brandenburg"
        }
    }
}
```

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/TK1e9PTBDv349PaIL/builds/L8tJ0KZ6xbsI7gvKK/openapi.json
