# Italian Administrative Case Law - Consiglio di Stato and TAR (`legaltech/giustizia-amministrativa`) Actor

Search judgments of the Italian Consiglio di Stato, CGA Sicilia and the 29 TAR (official OpenGA open data) with outcome, operative part and reporting judge.

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

### Italian Administrative Case Law - Consiglio di Stato and TAR

Searches decisions of the Italian administrative courts (Consiglio di Stato, the Sicilian CGA and the 29 regional administrative courts, TAR) in two modes: full text of all decisions with the official search engine of giustizia-amministrativa.it (default; judgments, orders and opinions, newest first, ECLI and snippet), or the subject of the appeal (oggetto del ricorso) in the official OpenGA open data (judgments since 2017, with outcome and dates). Boolean search (AND/OR/NOT, phrases, \* wildcard) and filters by court, decision date range (by year in full-text mode), outcome (esito: accoglie, respinge, inammissibile…), chamber and appeal number (NRG). Returns structured metadata (seat, chamber, type, number, NRG, dates, hearing type, outcome, whether it closes the case, subject, appeal type) and, by reading the judgment on the official portal, the reporting judge (relatore), the operative part (P.Q.M.), relevant passages and optional full text. Limits: outcome and appeal-number filters only exist in subject mode (used automatically when they are set); the Bolzano and Trento courts only have metadata in subject mode; some decisions have no published text.

### Use cases

- Find Consiglio di Stato judgments upholding challenges to exclusions from public tenders in a period.
- Analyse a regional TAR's case law on a topic (e.g. residence permits).
- Follow every judgment issued in an appeal by its number (NRG).
- Get the operative part (P.Q.M.) and the reporting judge of each judgment.

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

- `courts`: opaque codes (cds, cga, tar_rm, tar_mi…) — pick by title. Empty = all courts (slower).
- `searchIn`: "fulltext" (default) searches the whole text of the decisions; "subject" searches only the subject of the appeal (OpenGA) and supports relevance sorting, exact dates and outcome. Search terms in Italian (appalto, esclusione, permesso di soggiorno).
- `outcome` (subject mode): text contained in the outcome, e.g. "ACCOGLIE" or "RESPINGE".
- `appealNumbers`: "2394/2024" or "202402394".
- Not every judgment has its text on the official portal: in a 2026 sample of the Consiglio di Stato, about 80 % of the public-hearing (udienza pubblica) judgments had text, but only about 25 % of the camera di consiglio ones (access to documents, ottemperanza…), and the most recent weeks have fewer. Those results come with `textAvailable: false`, `relatore` and `dispositivo` set to null and a `textNote`. Set `onlyWithText: true` to return only judgments with text.
- Every result includes `searchTerm` and `rank`; `passages` holds the paragraphs where the search terms appear, ready for LLM analysis.

### Input example

```json
{
    "searchTerms": ["appalt* AND esclusione"],
    "courts": ["cds", "tar_rm"],
    "dateFrom": "2025-01-01",
    "outcome": "accoglie",
    "maxResults": 20,
    "includeText": true,
    "passages": 3
}
```

### Output example (abridged)

```json
{
    "searchTerm": "appalt* AND esclusione",
    "rank": 3,
    "court": "Consiglio di Stato",
    "section": "SEZIONE V",
    "type": "SENTENZA",
    "number": "6126/2026",
    "appealNumber": "...",
    "publicationDate": "2026-07-28",
    "hearingType": "UDIENZA PUBBLICA",
    "outcome": "ACCOGLIE APPELLO INCIDENTALE",
    "definesCase": true,
    "subject": "...",
    "appealType": "APPELLO RITO APPALTI (ex art. 120 c.p.a.)",
    "relatore": "Gianluca Rovelli",
    "dispositivo": "P.Q.M. Il Consiglio di Stato in sede giurisdizionale (Sezione Quinta), definitivamente pronunciando...",
    "passages": ["..."],
    "textUrl": "https://mdp.giustizia-amministrativa.it/visualizza/?..."
}
```

### Notes and limits

- Bolzano and Trento (TRGA) return metadata only; their texts are not available in the standard portal format.
- Texts are returned exactly as published by the official portal, with no additional anonymisation.
- Source: Giustizia Amministrativa — search engine of www.giustizia-amministrativa.it (Decisioni e pareri) and OpenGA open data (openga.giustizia-amministrativa.it). If the search engine is unavailable, the actor falls back to OpenGA and says so in the log.

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

Italian terms. Syntax: AND / OR / NOT, "exact phrase", \* wildcard (appalt\*), parentheses and -word. In full-text mode they are searched in the whole text of the decisions; in subject mode, in the subject of the appeal (oggetto del ricorso).

## `searchIn` (type: `string`):

Full text uses the official search engine of giustizia-amministrativa.it over all decisions (judgments, orders, opinions), newest first, with year-level date filtering. Subject searches the OpenGA metadata (oggetto del ricorso) of judgments and is the only mode that supports outcome, appeal number, exact dates and relevance sorting; it is used automatically when those filters are set. Codes are opaque: do NOT guess them; choose by reading the title (enumTitle) of each option.

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

Consiglio di Stato, CGA Sicilia and the regional administrative courts (TAR). Empty = all (slower). Codes are opaque: do NOT guess them; choose by reading the title (enumTitle) of each option.

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

YYYY-MM-DD. Open data starts in 2017.

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

YYYY-MM-DD.

## `outcome` (type: `string`):

Text contained in the outcome, e.g. "ACCOGLIE", "RESPINGE", "IRRICEVIBILE", "INAMMISSIBILE". Subject mode only (switches to it automatically).

## `section` (type: `string`):

Chamber (contains), e.g. "SEZIONE V".

## `appealNumbers` (type: `array`):

Only judgments in these appeals: "2394/2024" or "202402394". Subject mode only (switches to it automatically).

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

Subject mode only: publication date or relevance. Full-text results come newest first, as in the portal.

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

Maximum number of decisions returned per search term.

## `includeText` (type: `boolean`):

Opens each judgment on the official portal to extract the reporting judge, operative part (P.Q.M.) and relevant passages. Disable for metadata only (much faster).

## `onlyWithText` (type: `boolean`):

Skip judgments whose text is not yet published on the official portal (frequent for camera di consiglio rulings and the most recent weeks); the actor keeps reading candidates until it reaches maxResults. Requires Read the judgment.

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

Paragraphs of the judgment containing the search terms (requires "Read the judgment").

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

## Actor input object example

```json
{
  "searchTerms": [
    "appalto AND esclusione"
  ],
  "searchIn": "fulltext",
  "courts": [
    "cds"
  ],
  "appealNumbers": [],
  "sortOrder": "newest",
  "maxResults": 20,
  "includeText": true,
  "onlyWithText": false,
  "passages": 3,
  "includeFullText": false,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

Dataset of judgments returned by the search, one item per result. Main fields: searchTerm, court, section, number, publicationDate, outcome, subject, relatore, dispositivo, textUrl. 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": [
        "appalto AND esclusione"
    ],
    "courts": [
        "cds"
    ],
    "appealNumbers": [],
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("legaltech/giustizia-amministrativa").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": ["appalto AND esclusione"],
    "courts": ["cds"],
    "appealNumbers": [],
    "proxyConfiguration": { "useApifyProxy": False },
}

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

```

## MCP server setup

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

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/sHRomgSWHGHGvAsnk/builds/eddLhkXKcF5fehBvL/openapi.json
