# Ecuador Judicial Cases Lookup (`itsadry/judicatura-causas-ecuador`) Actor

Search judicial cases in Ecuador's Función Judicial by cédula, RUC, name or case number: case number, subject matter, offence and dates.

- **URL**: https://apify.com/itsadry/judicatura-causas-ecuador.md
- **Developed by:** [EC Data](https://apify.com/itsadry) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 case results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## Ecuador Judicial Cases Lookup (Función Judicial)

Search judicial cases and proceedings in Ecuador's **Función Judicial** public portal by ID number (cédula), RUC, name or case number. It calls the portal's JSON services directly (no browser), so it is fast and cheap to run.

### Input

```json
{
  "consultas": ["1790016919001", "09359-2026-01464"],
  "roles": ["actor", "demandado"],
  "maxCausasPorConsulta": 100,
  "incluirDetalle": false
}
```

| Field | Description | Default |
|---|---|---|
| `consultas` | List of values. Auto-detected: 10 or 13 digits = cédula/RUC; 14+ digits = case number; anything else = name | required |
| `roles` | Search the person as `actor` (plaintiff) and/or `demandado` (defendant). Not used for case numbers | both |
| `maxCausasPorConsulta` | Max cases returned per query and role | `100` |
| `incluirDetalle` | Add subject matter and action type (one extra request per case; slower) | `false` |
| `concurrencia` | Max parallel requests | `3` |
| `reintentos` | Retries with exponential backoff on network/server errors (4xx are not retried) | `3` |

### Output

One dataset item per case found. A query that fails or finds nothing is saved with `error` filled in in a separate dataset called `errores` (Storage tab of the run) and **you are not charged for it**; the run continues.

```json
{
  "consulta": "1790016919001",
  "rolConsultado": "actor",
  "numeroProceso": "17283202601609",
  "materia": "PENAL COIP",
  "tipoAccion": "ACCIÓN PENAL PÚBLICA",
  "delito": "189 ROBO, INC.1 (REFORMA 12 MAYO 2023)",
  "estado": "A",
  "fechaIngreso": "2026-09-27",
  "tieneDocumentoAdjunto": false,
  "error": null
}
```

Fields: `consulta`, `rolConsultado` (`actor`, `demandado` or `proceso`), `numeroProceso`, `materia`, `tipoAccion`, `delito`, `estado`, `fechaIngreso`, `tieneDocumentoAdjunto`, `error`. `materia` and `tipoAccion` are only filled when `incluirDetalle` is `true`.

### Use cases

- **KYC / due diligence**: check whether a person or company is involved in litigation.
- **AML**: spot criminal-matter cases (`materia`, `delito`) linked to a counterparty.
- **Credit and risk**: review litigation exposure before granting credit or signing contracts.

### Limitations

- Returns the case list and basic data; it does not return the full text of rulings or filings.
- Name searches may return homonyms: always confirm identity with a cédula/RUC or the case number.
- Data is whatever the portal publishes at query time; the Actor does not certify it.
- The portal may change or throttle traffic; keep `concurrencia` low.

### Responsible use of personal data

Judicial records are personal data, in some cases sensitive. Under Ecuador's **Ley Orgánica de Protección de Datos Personales (LOPDP)** you need a legitimate purpose and a legal basis, must process only what is necessary, and must respect data subjects' rights. Do not use results to discriminate or to build files on individuals without a lawful reason. You are responsible for your use of the data. This Actor is not affiliated with the Consejo de la Judicatura.

***

## Español

Consulta causas y procesos judiciales en el portal público de la **Función Judicial** por cédula, RUC, nombre o número de proceso. Usa directamente los servicios JSON del portal (sin navegador), por lo que es rápido y barato.

**Entrada:** lista `consultas` (se detecta sola: 10 o 13 dígitos = cédula/RUC; 14 o más dígitos = número de proceso; otro texto = nombre), `roles` (actor y/o demandado), `maxCausasPorConsulta`, `incluirDetalle`, `concurrencia` y `reintentos`.

**Salida:** un registro por causa. Si una consulta falla o no tiene causas, se guarda con `error` en un dataset aparte llamado `errores` (pestaña Storage de la ejecución), **no se cobra**, y la ejecución continúa.

**Casos de uso:** KYC, AML, debida diligencia y análisis de riesgo (exposición a litigios de una contraparte).

**Limitaciones:** no devuelve el texto de providencias; las búsquedas por nombre pueden traer homónimos, confirma con cédula/RUC; la información es la que publica el portal al momento de la consulta.

**Uso responsable (LOPDP):** los registros judiciales son datos personales, a veces sensibles. Úsalos con finalidad legítima y base legal, solo lo necesario y respetando los derechos de los titulares. Este Actor no está afiliado al Consejo de la Judicatura.

# Actor input Schema

## `consultas` (type: `array`):

Cada valor se detecta solo: 10 o 13 dígitos = cédula/RUC; 14 dígitos o más = número de proceso; otro texto = nombre.

## `roles` (type: `array`):

Busca a la persona como actor (demandante) y/o demandado. No aplica al número de proceso.

## `maxCausasPorConsulta` (type: `integer`):

Límite de causas devueltas por cada consulta y rol.

## `incluirDetalle` (type: `boolean`):

Agrega materia y tipo de acción (una petición extra por causa; más lento).

## `concurrencia` (type: `integer`):

Máximo de peticiones simultáneas a la Función Judicial.

## `reintentos` (type: `integer`):

Reintentos con espera exponencial ante errores de red o del servidor.

## Actor input object example

```json
{
  "consultas": [
    "1790016919001",
    "09359-2026-01464"
  ],
  "roles": [
    "actor",
    "demandado"
  ],
  "maxCausasPorConsulta": 100,
  "incluirDetalle": false,
  "concurrencia": 3,
  "reintentos": 3
}
```

# Actor output Schema

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

No description

# 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 = {
    "consultas": [
        "1790016919001",
        "09359-2026-01464"
    ],
    "roles": [
        "actor",
        "demandado"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("itsadry/judicatura-causas-ecuador").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 = {
    "consultas": [
        "1790016919001",
        "09359-2026-01464",
    ],
    "roles": [
        "actor",
        "demandado",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("itsadry/judicatura-causas-ecuador").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 '{
  "consultas": [
    "1790016919001",
    "09359-2026-01464"
  ],
  "roles": [
    "actor",
    "demandado"
  ]
}' |
apify call itsadry/judicatura-causas-ecuador --silent --output-dataset

```

## MCP server setup

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

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/x5Ipo6vfqJk0xfMvv/builds/O5BPvDgnU4lindHhh/openapi.json