# Rechtspraak - Dutch Case Law Search (`legaltech/rechtspraak`) Actor

Search Dutch court decisions via the official Rechtspraak Open Data API: filters by court and area of law, summary, relations between instances, full text.

- **URL**: https://apify.com/legaltech/rechtspraak.md
- **Developed by:** [Miguel González](https://apify.com/legaltech) (community)
- **Categories:** Automation
- **Features:** Limited permissions
- **Stats:** 3 total users, 2 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

### Rechtspraak - Dutch Case Law Search

Searches decisions of the Dutch courts (Supreme Court and its Procurator General, Council of State, Central Appeals Tribunal, Trade and Industry Appeals Tribunal, courts of appeal, district courts and the courts of the Dutch Caribbean) with the official search engine of the Dutch judiciary (uitspraken.rechtspraak.nl, the same full-text search as the website, over 970,000 published decisions) and the official Open Data API for metadata and text. Full-text search with implicit AND, OR, NOT/-word, "exact phrases" and \* wildcard (also EN/OF/NIET), sorted by relevance or date; official filters by court, area of law (rechtsgebied), type (judgment or Advocate General opinion) and decision dates; lookup by ECLI. Returns ECLI, court, dates, case number, procedure, area of law, summary, cited statutes, relations with other instances, journal publications, passages and optional full text.

### Use cases

- Find tenancy decisions on a specific problem in a given court and period.
- Retrieve a decision by ECLI with its relations (cassation, appeal) and annotated publications.
- Analyse recent Supreme Court (Hoge Raad) case law in an area of law.
- Get Advocate General opinions (Conclusie).

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

- `courts` and `legalAreas`: opaque codes (HR, RVS, RBAMS… / civielRecht_verbintenissenrecht…) — pick by title.
- Words separated by spaces must all appear (AND). Use OR for alternatives and -word to exclude. `sortOrder`: relevance (default), newest or oldest.
- `totalFound` is the number of matches in the search engine (with OR, the sum of each branch).
- Search terms in Dutch. `eclis`: "ECLI:NL:HR:2020:1".
- Every result includes `searchTerm` and `rank`; `passages` holds the paragraphs where the search terms appear, ready for LLM analysis.

### Input example

```json
{
    "searchTerms": ["huurprijs AND (schimmel OR vocht)"],
    "legalAreas": ["civielRecht_verbintenissenrecht"],
    "courts": ["RBROT", "RBAMS"],
    "dateFrom": "2023-01-01",
    "sortOrder": "relevance",
    "maxResults": 20
}
```

### Output example (abridged)

```json
{
    "ecli": "ECLI:NL:HR:2020:1",
    "court": "Hoge Raad",
    "decisionDate": "2020-01-10",
    "caseNumbers": ["19/01199"],
    "procedure": ["Cassatie"],
    "legalAreas": ["Bestuursrecht; Belastingrecht"],
    "summary": "artikel 53 Successiewet, art. 6:228 BW, vernietiging schenkingsovereenkomst wegens dwaling.",
    "relations": [{ "ecli": "ECLI:NL:GHARL:2019:414", "type": "cassatie", "instance": "eerdereAanleg" }],
    "publications": ["BNB 2020/37 met annotatie van A.O. Lubbers", "NTFR 2020/157 met annotatie van mr. A. de Vries"],
    "url": "https://uitspraken.rechtspraak.nl/details?id=ECLI%3ANL%3AHR%3A2020%3A1"
}
```

### Notes and limits

- Searches use the official search engine of uitspraken.rechtspraak.nl; metadata and text come from the Open Data API (data.rechtspraak.nl). If the search engine is unavailable, the actor falls back to scanning the newest decisions of the Open Data API (capped by `maxDocumentsToScan`) and says so in the log.
- `maxResults` applies per search term (max 1000).

### 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 (NL) 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`):

Full-text search over all published decisions (the same search engine as uitspraken.rechtspraak.nl), in Dutch. Syntax: words separated by spaces or AND (all must appear), OR, NOT / -word, "exact phrase", parentheses and \* wildcard (also EN / OF / NIET). Combine with court, area of law and dates.

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

Specific decisions, e.g. "ECLI:NL:HR:2020:1".

## `courts` (type: `array`):

Supreme Court (Hoge Raad), Council of State, CRvB, CBb, courts of appeal, district courts, Dutch Caribbean courts… Codes are opaque: do NOT guess them; choose by reading the title (enumTitle) of each option.

## `legalAreas` (type: `array`):

Rechtsgebied (civil, criminal, administrative law and sub-areas). Codes are opaque: do NOT guess them; choose by reading the title (enumTitle) of each option.

## `documentType` (type: `string`):

Judgments or Advocate General opinions. Codes are opaque: do NOT guess them; choose by reading the title (enumTitle) of each option.

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

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

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

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

## `sortOrder` (type: `string`):

Order of the results (decision date or relevance, as on the website).

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

Maximum per search term.

## `maxDocumentsToScan` (type: `integer`):

Only used if the search engine is unavailable: the actor then scans the newest decisions of the Open Data API (no text search) and stops after this many.

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

Number of paragraphs containing the search terms returned in `passages` (0 = none). Ideal for LLM analysis.

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

Adds the `text` field with the full decision. Greatly increases output size; enable only if needed.

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

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

## Actor input object example

```json
{
  "searchTerms": [
    "huurprijs schimmel"
  ],
  "eclis": [],
  "courts": [],
  "legalAreas": [],
  "documentType": "",
  "sortOrder": "relevance",
  "maxResults": 20,
  "maxDocumentsToScan": 500,
  "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, ecli, court, decisionDate, caseNumbers, procedure, legalAreas, summary, 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": [
        "huurprijs schimmel"
    ],
    "eclis": [],
    "courts": [],
    "legalAreas": [],
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("legaltech/rechtspraak").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": ["huurprijs schimmel"],
    "eclis": [],
    "courts": [],
    "legalAreas": [],
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("legaltech/rechtspraak").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": [
    "huurprijs schimmel"
  ],
  "eclis": [],
  "courts": [],
  "legalAreas": [],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call legaltech/rechtspraak --silent --output-dataset

```

## MCP server setup

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

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/Uz6FFu892EVmnjXJ1/builds/T5WvaeESYbTxQNp6p/openapi.json
