# Swedish Case Law Search (Rättspraxis, Domstolsverket) (`legaltech/domstol-se`) Actor

Search Swedish case law (HD, HFD, courts of appeal, Labour Court…) via the official rättspraxis API: summaries, statutes by SFS number, preparatory works.

- **URL**: https://apify.com/legaltech/domstol-se.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

### Swedish Case Law Search (Rättspraxis, Domstolsverket)

Searches Swedish court decisions through the official case-law (rättspraxis) API of the Swedish National Courts Administration: Supreme Court (NJA), Supreme Administrative Court (HFD, formerly RÅ), courts of appeal (RH), administrative courts of appeal, Labour Court (AD), Migration Court of Appeal, Land and Environment Court of Appeal, Patent and Market Court of Appeal, Market Court and others. Search in Swedish with native AND/OR/NOT lists (also OCH/ELLER/INTE), exact phrase and wildcard; lookup by case number or report number (NJA 2020 s. 123, RH 2026:19); filters by court, precedent value (prejudikat, guiding…), publication form, applied statutes by SFS number and dates. Returns court, date, case and report numbers, summary (sammanfattning), keywords, applied statutes with SFS numbers, preparatory works, cited literature, referenced decisions, PDF, passages and optional full text.

### Use cases

- Find Supreme Court or Labour Court precedents on an issue.
- Find every decision applying a statute by its SFS number (e.g. 1970:994, the Land Code).
- Retrieve a specific report (NJA, RH, AD, RÅ…).
- Get the official summaries and the preparatory works cited.

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

- `courts`: opaque codes (HDO = Supreme Court, HFD, ADO = Labour Court…) — pick by title.
- `sfsNumbers`: format "1970:994".
- `caseNumbers`: case number ("T 557-24") or report number ("RH 2026:19"). Search terms in Swedish.
- Free-text search: the official API matches inflected forms anywhere in the judgment and can only sort by date, so a plain query ("dolda fel fastighet") also matches long decisions that use the words in passing. The default `sortOrder: "relevance"` fixes the order: the actor fetches up to 500 matches and ranks first the decisions whose summary and keywords contain the terms. For exhaustive research on a statute, the `sfsNumbers` filter (e.g. "1970:994") is the most precise option; combine it with search terms to narrow the topic.
- Every result includes `searchTerm` and `rank`; `passages` holds the paragraphs where the search terms appear, ready for LLM analysis.

### Input example

```json
{
    "searchTerms": ["(uppsägning OR avskedande) AND arbetsbrist"],
    "courts": ["ADO"],
    "decisionTypes": ["PREJUDIKAT", "VAGLEDANDE_MEN_EJ_PREJUDICERANDE"],
    "dateFrom": "2020-01-01",
    "maxResults": 50
}
```

### Output example (abridged)

```json
{
    "court": "Svea hovrätts hyresrättsliga avgöranden",
    "decisionDate": "2019-03-26",
    "caseNumbers": ["ÖH 223-18"],
    "reportNumbers": ["RH 2019:27"],
    "decisionType": "VAGLEDANDE_MEN_EJ_PREJUDICERANDE",
    "summary": "Hyresnämndsmål. En hyresgäst har innehållit hyra som deponerats hos länsstyrelsen...",
    "statutes": [{ "reference": "12 kap. 20 §, 21 § ... jordabalken (1970:994)", "sfsNumber": "1970:994" }],
    "referencedDecisions": ["RBD 8:84, Svea hovrätts dom den 21 september 2001 i mål nr T 2118-01"],
    "url": "https://rattspraxis.etjanst.domstol.se/sok/publicering/5d3fe3bb-a339-46d0-b8b5-6746dffa42ec"
}
```

### 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 (SE) 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 Swedish. Syntax: words (implicit AND; also OCH), "exact phrase", OR / ELLER, NOT / INTE, parentheses and \* wildcard.

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

Retrieve decisions by case number ("T 557-24") or report number ("NJA 2020 s. 123", "RH 2026:19").

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

Supreme Court, Supreme Administrative Court, courts of appeal, administrative courts of appeal, Labour Court, Migration Court of Appeal… Empty = all. Codes are opaque: do NOT guess them; choose by reading the title (enumTitle) of each option.

## `decisionTypes` (type: `array`):

Binding precedent, guiding, etc. Codes are opaque: do NOT guess them; choose by reading the title (enumTitle) of each option.

## `publicationForms` (type: `array`):

Report (referat, with summary), notice (notis) or judgment. Codes are opaque: do NOT guess them; choose by reading the title (enumTitle) of each option.

## `sfsNumbers` (type: `array`):

Only decisions applying these statutes, e.g. "1970:994" (Land Code).

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

Relevance (default): the official API only sorts by date and matches inflected forms anywhere in long judgments, so the actor fetches up to 500 matches and ranks them, putting first the decisions whose summary and keywords contain the terms and where the terms appear together. Without search terms it falls back to newest first. Newest / Oldest: decision date.

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

Maximum per search term.

## `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 (SE) or your own proxyUrls; requests then use sticky sessions, IP rotation and a Chrome TLS fingerprint.

## Actor input object example

```json
{
  "searchTerms": [
    "hyra mögel"
  ],
  "caseNumbers": [],
  "courts": [],
  "decisionTypes": [],
  "publicationForms": [],
  "sfsNumbers": [],
  "sortOrder": "relevance",
  "maxResults": 20,
  "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, caseNumbers, reportNumbers, decisionType, summary, statutes, 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": [
        "hyra mögel"
    ],
    "caseNumbers": [],
    "courts": [],
    "decisionTypes": [],
    "publicationForms": [],
    "sfsNumbers": [],
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("legaltech/domstol-se").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": ["hyra mögel"],
    "caseNumbers": [],
    "courts": [],
    "decisionTypes": [],
    "publicationForms": [],
    "sfsNumbers": [],
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("legaltech/domstol-se").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": [
    "hyra mögel"
  ],
  "caseNumbers": [],
  "courts": [],
  "decisionTypes": [],
  "publicationForms": [],
  "sfsNumbers": [],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call legaltech/domstol-se --silent --output-dataset

```

## MCP server setup

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

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/L249v9Os0cLvpPum0/builds/26t48aNVfyYrUdmz5/openapi.json
