Domsdatabasen - Danish Case Law Search avatar

Domsdatabasen - Danish Case Law Search

Pricing

from $1.00 / 1,000 results

Go to Apify Store
Domsdatabasen - Danish Case Law Search

Domsdatabasen - Danish Case Law Search

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

Pricing

from $1.00 / 1,000 results

Rating

0.0

(0)

Developer

Miguel González

Miguel González

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

12 days ago

Last modified

Categories

Features

Limited permissions

Share

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

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

Output example (abridged)

{
"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.