# DGSI - Portuguese Case Law Search (`legaltech/dgsi`) Actor

Search Portuguese case law (STJ, STA, Courts of Appeal, TCA, Tribunal dos Conflitos) in the official DGSI databases: headnotes (sumário), descriptors, outcome and full text.

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

### DGSI - Portuguese Case Law Search

Searches court decisions (acórdãos) in the official DGSI databases of the Portuguese Ministry of Justice: Supremo Tribunal de Justiça (STJ), Supremo Tribunal Administrativo (STA), Tribunal dos Conflitos, the five Courts of Appeal (Relações of Porto, Lisboa, Coimbra, Guimarães and Évora), the two Central Administrative Courts (TCA Sul and Norte) and the Constitutional Court up to 1998. Supports full-text search with AND/OR/NOT, exact phrases and the \* wildcard (Spanish and Portuguese operators Y/E, O/OU, NO/NÃO are translated automatically), filters by court, reporting judge (relator), subject descriptor and decision date range, and sorting by relevance or date added. For each decision it returns case number, reporting judge, descriptors, decision date, vote, procedural type, outcome, the official headnote (sumário) and, optionally, the full text. A second run can fetch specific decisions by URL (documentUrls). Limits: DGSI returns at most 1,000 hits per query and court; maxResults is the total per search term (when several courts are searched, results alternate between courts in hierarchical order, or are merged by date).

### Use cases

- Find Supreme Court (STJ) or Court of Appeal case law on a legal issue (e.g. culpable insolvency) within a date range.
- List decisions by a given reporting judge or with a given subject descriptor.
- Compare how different Courts of Appeal decide the same issue.
- Extract official headnotes (sumários) for quick review or LLM analysis.
- Download the full text of specific decisions from their URLs (documentUrls).

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

- `databases`: opaque codes (jstj, jsta, jtrp…) — pick by their title. Empty = all courts (slower).
- `searchTerms`: one search per item, written in Portuguese. Use `AND` between concepts and quotes for phrases: `"insolvência culposa" AND gerente`.
- Dates use YYYY-MM-DD (`dateFrom`, `dateTo`).
- To read full decisions: search first, then pass the returned `documentUrl` values in `documentUrls` with `includeFullText: true`.
- Every result includes `searchTerm` and `rank`; `passages` holds the paragraphs where the search terms appear, ready for LLM analysis.

### Coverage

| Code | Court |
|---|---|
| `jstj` | Supremo Tribunal de Justiça |
| `jsta` | Supremo Tribunal Administrativo |
| `jcon` | Tribunal dos Conflitos |
| `jtrp` / `jtrl` / `jtrc` / `jtrg` / `jtre` | Courts of Appeal (Porto, Lisboa, Coimbra, Guimarães, Évora) |
| `jtca` / `jtcn` | Central Administrative Courts (South / North) |
| `atco1` | Constitutional Court (until 1998); for current case law use `legaltech/tribunal-constitucional-pt` |

### Input example

```json
{
    "searchTerms": ["\"insolvência culposa\" OU (falência E dolo)"],
    "databases": ["jstj", "jtrp"],
    "dateFrom": "2022-01-01",
    "dateTo": "2023-12-31",
    "maxResults": 20,
    "includeFullText": false
}
```

### Output example (abridged)

```json
{
    "searchTerm": "\"insolvência culposa\" OU (falência E dolo)",
    "database": "jtrp",
    "court": "Tribunal da Relação do Porto",
    "rank": 1,
    "relevance": "93%",
    "processNumber": "8053/21.1T8PRT.P1",
    "relator": "FILIPE CAROÇO",
    "descriptors": ["ENCERRAMENTO DO PROCESSO DE INSOLVÊNCIA", "EXONERAÇÃO DO PASSIVO RESTANTE"],
    "documentNumber": "RP202211108053/21.1T8PRT.P1",
    "decisionDate": "11/10/2022",
    "decisionDateISO": "2022-11-10",
    "vote": "UNANIMIDADE",
    "proceduralMeans": "APELAÇÃO",
    "decision": "CONFIRMADA",
    "summary": "I - A situação em que é o Administrador da Insolvência...",
    "otherFields": { "Privacidade": "1" },
    "documentUrl": "https://www.dgsi.pt/jtrp.nsf/.../e386eff3a3db4ba48025890f0054a3eb?OpenDocument"
}
```

### Notes and limits

- DGSI returns at most 1,000 hits per query. For broader searches, split by date ranges.
- The DGSI server rejects some queries starting with parentheses or quoted phrases; the actor reorders the query to avoid this and logs a clear message if a query is still rejected.

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

Terms to search in the text of the decisions (Portuguese). Lotus Domino syntax: AND, OR, NOT, "exact phrase", \* wildcard (insolv\*). Spanish/Portuguese operators Y/E, O/OU and NO/NÃO (uppercase) are translated automatically.

## `databases` (type: `array`):

DGSI databases to search. Empty = all. Codes are opaque: do NOT guess them; choose by reading the title (enumTitle) of each option.

## `relator` (type: `string`):

Name (or part) of the reporting judge, e.g. "ANA RESENDE".

## `descriptor` (type: `string`):

Subject descriptor assigned to the decision, e.g. "QUALIFICAÇÃO DE INSOLVÊNCIA".

## `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, or date the document was added to DGSI (not exactly the decision date).

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

Maximum decisions per search term in total (all selected databases together, merged by relevance or date). DGSI returns at most 1,000 per query and database.

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

Adds the `text` field with the full decision. Greatly increases output size.

## `documentUrls` (type: `array`):

URLs of decisions (the `documentUrl` field from previous results) to fetch directly. Maximum 100 per run.

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

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

## Actor input object example

```json
{
  "searchTerms": [
    "insolvência AND culposa"
  ],
  "databases": [
    "jstj"
  ],
  "sortOrder": "relevance",
  "maxResults": 10,
  "includeFullText": false,
  "documentUrls": [],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

Dataset of decisions returned by the search, one item per result. Main fields: searchTerm, court, decisionDateISO, processNumber, relator, descriptors, decision, summary, documentUrl. 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": [
        "insolvência AND culposa"
    ],
    "databases": [
        "jstj"
    ],
    "documentUrls": [],
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("legaltech/dgsi").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": ["insolvência AND culposa"],
    "databases": ["jstj"],
    "documentUrls": [],
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("legaltech/dgsi").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": [
    "insolvência AND culposa"
  ],
  "databases": [
    "jstj"
  ],
  "documentUrls": [],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call legaltech/dgsi --silent --output-dataset

```

## MCP server setup

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

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/NT91Kh7ZhDN9QKR3o/builds/36fMXikzVyCtHgbNd/openapi.json
