# Domsdatabasen - Danish Case Law Search (`legaltech/domsdatabasen`) Actor

Search Danish court judgments in the official Domsdatabasen: boolean search, ECLI, final/appealed status, related cases across instances, full text.

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

### Domsdatabasen - Danish Case Law Search

Searches judgments of the Danish courts (Supreme Court, Eastern and Western High Courts, Maritime and Commercial Court, the 24 district courts and the courts of Greenland and the Faroe Islands) in Domsdatabasen, the official database of the Danish Court Administration, with native boolean search in Danish (AND/OR/NOT, also OG/ELLER/IKKE), phrases and \* wildcard; lookup by case number; filters by court, instance, proceeding type (civil/criminal) and dates; sorting by relevance or date. Returns court, case number, ECLI, date, instance, case type, subjects, headline and documents, and optionally the case record (final or appealed status, amounts claimed, anonymised parties, related cases in other instances), passages and full text. Limits: court, instance and type filters are applied to the search results; the server has occasional latency spikes.

### Use cases

- Find Danish judgments on an issue (e.g. rent and mould) in specific courts.
- Follow a case through the instances (district court → high court → Supreme Court).
- Check whether a judgment is final (Endelig) or under appeal (Appelleret).
- Retrieve a case by its number (BS-2390/2010-RAN).

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

- `courts`: opaque abbreviations (HJR = Supreme Court, OLR = Eastern High Court, VLR = Western High Court, KBH = Copenhagen City Court…) — pick by title.
- Search terms in Danish with AND/OR/NOT. Words match exactly (the actor quotes them, because the engine's fuzzy matching adds hundreds of false hits for short words): use the \* wildcard for Danish compounds and inflections, e.g. `skimmel*` also finds "skimmelsvamp", `huslej*` finds "huslejen".
- Use `sortOrder: "newest"` if you need a stable order (relevance ties may come back in a different order between runs).
- Every result includes `searchTerm` and `rank`; `passages` holds the paragraphs where the search terms appear, ready for LLM analysis.

### Input example

```json
{
    "searchTerms": ["huslej* AND skimmel*", "\"ophævelse af lejemål\""],
    "courts": ["HJR", "OLR", "VLR"],
    "dateFrom": "2020-01-01",
    "sortOrder": "newest",
    "maxResults": 20
}
```

### Output example (abridged)

```json
{
    "searchTerm": "\"ophævelse af lejemål\"",
    "court": "Højesteret",
    "courtCode": "HJR",
    "courtCaseNumber": "BS-45278/2022-HJR",
    "verdictDate": "2023-09-01",
    "instance": "3. instans",
    "headline": "Højesteret ændrer landsrettens afgørelse ...",
    "ecli": "ECLI:DK:...",
    "verdictStatus": "Endelig",
    "relatedCases": [{ "relation": "other instance", "courtCaseNumber": "...", "court": "Østre Landsret", "instance": "2. instans" }],
    "url": "https://domsdatabasen.dk/#/sag/..."
}
```

### 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 (DK) 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, in Danish. Syntax: AND / OR / NOT (also OG / ELLER / IKKE), "exact phrase", \* wildcard (huslej\*). Words match exactly: use \* for compounds and inflections (skimmel\* also finds skimmelsvamp).

## `caseNumbers` (type: `array`):

Retrieve cases by number, e.g. "BS-2390/2010-RAN".

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

Supreme Court, high courts, Maritime and Commercial Court, district courts… Empty = all. Codes are opaque: do NOT guess them; choose by reading the title (enumTitle) of each option.

## `instance` (type: `string`):

Instance of the case. Codes are opaque: do NOT guess them; choose by reading the title (enumTitle) of each option.

## `profession` (type: `string`):

Civil or criminal. Codes are opaque: do NOT guess them; choose by reading the title (enumTitle) of each option.

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

Judgment date, YYYY-MM-DD.

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

Judgment date, YYYY-MM-DD.

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

Sort criterion.

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

Maximum cases per search term.

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

Adds final/appealed status, amounts claimed, parties (anonymised) and related cases in other instances.

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

Paragraphs of the judgment containing the search terms.

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

Adds the full text of the main judgment.

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

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

## Actor input object example

```json
{
  "searchTerms": [
    "huslej* AND skimmel*"
  ],
  "caseNumbers": [],
  "courts": [],
  "instance": "",
  "profession": "",
  "sortOrder": "relevance",
  "maxResults": 20,
  "includeDetails": true,
  "passages": 3,
  "includeFullText": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

Dataset of cases returned by the search, one item per result. Main fields: searchTerm, court, courtCaseNumber, verdictDate, instance, caseType, headline, ecli, verdictStatus, 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": [
        "huslej* AND skimmel*"
    ],
    "caseNumbers": [],
    "courts": [],
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("legaltech/domsdatabasen").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": ["huslej* AND skimmel*"],
    "caseNumbers": [],
    "courts": [],
    "proxyConfiguration": { "useApifyProxy": False },
}

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

```

## MCP server setup

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

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/FaUG1XgyRUIk1GbFP/builds/5C4ebJvQmtYFZXgSQ/openapi.json
