# French Administrative Case Law - Conseil d'État, CAA, TA (`legaltech/conseil-etat`) Actor

Search French administrative case law (Conseil d'État, CAA, TA) in the official open data: boolean full-text search, Lebon status, passages, full text.

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

### French Administrative Case Law - Conseil d'État, CAA, TA

Searches decisions of the French administrative courts in their official open data (opendata.justice-administrative.fr): Council of State (Conseil d'État, since September 2021), administrative courts of appeal (CAA) and administrative tribunals (TA, since 2022). Native full-text search (Elasticsearch) with AND/OR/NOT (also ET/OU/SAUF), phrases, parentheses and wildcard; filters by court code, date range and only decisions published or mentioned in the official Lebon reports. Returns court, formation, case number, decision type, reading date, Lebon publication status, ECLI, relevant passages and optional full text. Limits: up to 9,999 decisions per query, sorted by date; Council of State case law before 2021 is in ArianeWeb, not in this database.

### Use cases

- Find Council of State emergency orders (référé-liberté) on an issue (e.g. emergency housing).
- Compare case law across administrative courts of appeal.
- Keep only decisions published in the Lebon reports (highest doctrinal value).
- Extract passages for LLM analysis.

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

- `courts`: exact codes — "CE", "CAA13"…"CAA78", "TA" + number (e.g. "TA75" = Paris).
- Search terms in French with Elasticsearch operators: `"référé liberté" AND (hébergement OR logement)`.
- `lebonOnly: true` keeps only the decisions with the highest doctrinal value.
- Every result includes `searchTerm` and `rank`; `passages` holds the paragraphs where the search terms appear, ready for LLM analysis.

### Input example

```json
{
    "searchTerms": ["\"référé liberté\" ET (hébergement OR logement)"],
    "courts": ["CE"],
    "dateFrom": "2025-01-01",
    "maxResults": 50
}
```

### Output example (abridged)

```json
{
    "court": "Conseil d'Etat",
    "courtCode": "CE",
    "chamber": "Juge des référés",
    "caseNumber": "520632",
    "decisionType": "Ordonnance",
    "decisionDate": "2026-10-22",
    "publication": "Inédit au recueil Lebon",
    "passages": ["4. Il ressort des pièces de la procédure de première instance que..."],
    "url": "https://opendata.justice-administrative.fr/recherche/shareFile/CE/..."
}
```

### Notes and limits

- The official database returns up to 9,999 decisions per query, newest first; date and Lebon filters are applied to that set.
- For Council of State case law before 2021 the official source is ArianeWeb.

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

Full-text search (Elasticsearch), in French: AND / OR / NOT (also ET / OU / SAUF), "exact phrase", parentheses and \* wildcard.

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

Court codes: CE (Conseil d'État), CAA13, CAA31, CAA33, CAA44, CAA54, CAA59, CAA69, CAA75, CAA78 (administrative courts of appeal) or TA + code (administrative tribunals, e.g. TA75 = Paris). Empty = all.

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

Reading date of the decision, YYYY-MM-DD.

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

Reading date, YYYY-MM-DD.

## `lebonOnly` (type: `boolean`):

Only decisions published in the recueil Lebon or mentioned in its tables (A/B).

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

Maximum per search term (newest first).

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

## Actor input object example

```json
{
  "searchTerms": [
    "expulsion AND logement"
  ],
  "courts": [
    "CE"
  ],
  "lebonOnly": false,
  "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, chamber, caseNumber, decisionDate, decisionType, publication, 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": [
        "expulsion AND logement"
    ],
    "courts": [
        "CE"
    ],
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

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

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

```

## MCP server setup

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

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/ZaEDleNvrWvQtAYi1/builds/SxFpkL5PTNzmqRq9U/openapi.json
