Colombia Rama Judicial Court Case Scraper

Scrape Colombian court case records from the Rama Judicial Consulta de Procesos Nacional Unificada (CPNU) by company name, person name, or exact radicado. Here is one real result, with every field the actor returns (the actuaciones array holds 7 movements; 2 are shown here, all values real):

{
  "radicado": "13001310300320170056402",
  "despacho": "DESPACHO 000 - TRIBUNAL SUPERIOR - CIVIL - FAMILIA - CARTAGENA *",
  "processType": "Sin Tipo de Proceso",
  "processClass": "Sin Tipo de Proceso",
  "subClass": "Sin Subclase de Proceso",
  "recurso": "Sin Tipo de Recurso",
  "ponente": "MAG. JOHN FREDDY SAZA PINEDA",
  "ubicacion": "Secretaria",
  "courtCode": "130012213000",
  "contenidoRadicacion": "3C: 200,201-400,401-649 VERBAL REIVINDICATORIO EN APELACIÒN DE AUTO",
  "department": "BOLÍVAR",
  "cityCode": "13001",
  "filingYear": 2017,
  "demandantes": ["GRUPO ARGOS S.A."],
  "demandados": ["WALFREDO PACHECO HERNANDEZ", "EDGARDO PACHECO POLO", "NARCILA PACHECO DE GUERRERO", "JUAN ANDRES PACHECO", "BONIFACIO PACHECO DE LA ROSA"],
  "otrosSujetos": [],
  "sujetosProcesales": [
    {"name": "GRUPO ARGOS S.A.", "role": "demandante", "roleLabel": "Demandante", "docType": null, "docNumber": null},
    {"name": "WALFREDO PACHECO HERNANDEZ", "role": "demandado", "roleLabel": "Demandado", "docType": null, "docNumber": null}
  ],
  "sujetosCount": 6,
  "partiesRaw": "Demandante: GRUPO ARGOS S.A. | Demandado: WALFREDO PACHECO HERNANDEZ | Demandado: EDGARDO PACHECO POLO | Demandado: NARCILA PACHECO DE GUERRERO | Demandado: JUAN ANDRES PACHECO | Demandado: BONIFACIO PACHECO DE LA ROSA",
  "filingDate": "2019-08-27",
  "lastActionDate": "2019-12-18",
  "lastActionDaysAgo": 2443,
  "lastUpdate": "2026-08-05",
  "isPrivate": false,
  "idProceso": 59607293,
  "url": "https://consultaprocesos.ramajudicial.gov.co",
  "actuacionesCount": 7,
  "actuaciones": [
    {"consecutivo": 7, "actuacion": "Auto decide recurso", "anotacion": "CONFIRMA AUTO DE 30 DE AGOSTO DE 2019", "date": "2019-12-18", "startDate": null, "endDate": null, "registeredDate": "2019-12-18", "hasDocuments": false},
    {"consecutivo": 1, "actuacion": "Reparto y Radicación", "anotacion": "REPARTO Y RADICACION DEL PROCESO REALIZADAS EL martes, 27 de agosto de 2019 con secuencia: 12599", "date": "2019-08-27", "startDate": null, "endDate": null, "registeredDate": "2019-08-27", "hasDocuments": false}
  ],
  "observedAt": "2026-08-26T12:28:20.980Z",
  "error": null
}

The most complete Colombia Rama Judicial scraper available, and the only one on the Apify Store. It returns every field the Consulta de Procesos platform exposes for each judicial process, from the court, judge, parties, and process classification to the full timeline of actuaciones (case movements), plus derived fields (filing year, city and court codes, days since last action, party count) and 11 filters to target exactly the cases you need. Optional AI add-ons summarize, translate, and extract structured data from each case.

📥 Input · 📤 Output · 💰 Pricing · ▶️ Examples

Table of contents

• What it does
• How we compare
• Use cases
• Quickstart
• Input reference
• Output reference
• Example output record
• Run via API and CLI
• Fetch results
• Billing and limits
• FAQ and troubleshooting

What it does

This is a Rama Judicial scraper and consulta de procesos Colombia API in one actor. It searches the Colombian judiciary's Consulta de Procesos Nacional Unificada (CPNU) platform by company or person name, or by exact radicado (23-digit process number), and writes one normalized record per judicial process to the run's dataset. Each record carries the radicado, court (despacho) with its full and city-level codes, process type, class and subclass, reporting magistrate (ponente), department, and the parties (plaintiffs, defendants, other subjects) as arrays, as a structured sujetosProcesales list with roles, and as a raw string. With details on, it also returns the full timeline of actuaciones (case movements) with dates, notes, and start/end dates. Missing source values are returned as null, never invented.

Eleven input filters let you target exactly the cases you want: party type, court/city code, party role (plaintiff or defendant), one or more departments, filing date range, and last-action date, plus toggles to include or skip details and movements for speed. Three optional paid AI add-ons layer on top: a plain-language Spanish summary, an English translation and summary, and structured extraction of the case (claim type, court, amounts). Each is charged only when it produces usable output.

How we compare

There is currently no other Colombia Rama Judicial or Colombian court-records scraper on the Apify Store, so on Apify this is the only turnkey option. The real alternatives are a few standalone Colombian commercial APIs and web portals (for example apitude.co, coresoft.solutions, NBI, expedientes.co) and generic US-court scrapers (PACER, RECAP, CourtListener) that do not cover Colombia at all.

Capability	This actor	Typical Colombian court API/portal	US court scrapers (PACER / CourtListener)
Colombia Rama Judicial coverage	Yes, nationwide (CPNU)	Yes	No
Search by company / person name	Yes (batch, many per run)	Usually one at a time	N/A
Search by exact radicado	Yes (batch)	Yes	N/A
Full actuaciones (movement) timeline	Yes, with dates and notes	Rarely	N/A
Structured parties with roles	Yes (sujetosProcesales)	Partial	N/A
Filters (role, department, date range, active)	Yes, 11 inputs	Minimal	N/A
Derived fields (filing year, codes, days-since-action)	Yes	No	N/A
Bulk multi-search in one run	Yes	No	N/A
Export to JSON, CSV, Excel	Yes	Varies	Yes
Pay per result, no charge on failure	Yes	Contact-sales pricing	Varies

Why choose this actor: you get the full case surface (parties, classification, and every movement) in one call, bulk multi-name and multi-radicado search, filters no portal offers, and transparent pay-per-result billing with no charge on empty or failed runs.

Use cases

• Legal due diligence and KYB in Colombia. Pull the litigation history of a company (razón social) before onboarding, investing, or signing, and see plaintiffs, defendants, courts, and case status.
• Litigation risk and background checks. Screen counterparties, suppliers, or individuals for active and past court processes across all Colombian departments.
• Law-firm case monitoring. Track your own or opposing parties' dockets and watch new actuaciones (movements) by filtering on last-action date.
• Debt collection and recovery. Find judicial processes tied to a debtor and follow their procedural stage.
• Compliance, AML, and vendor screening. Add Colombian court-record checks to onboarding and periodic review workflows.
• Journalism and investigations. Research litigation involving public companies, officials, or organizations, with the full movement history.

Quickstart

Open the actor, paste this into the input, and press Run. It returns up to 10 judicial processes for a company, with the full actuaciones timeline.

{
  "searchNames": ["GRUPO ARGOS S.A."],
  "tipoPersona": "jur",
  "maxRecords": 10,
  "withDetails": true,
  "withActuaciones": true,
  "onlyActive": false
}

Search by name with searchNames (set tipoPersona to jur for a company or nat for a person), or look up exact processes with radicados. A broad company name can match more than a thousand processes; narrow it with despacho (a court or city code prefix) or the role, departments, and date-range filters. For a faster metadata-only run, set withActuaciones to false.

Input reference

Field	Type	Required	Default	Description
searchNames	string[]	no	["GRUPO ARGOS S.A."]	Company names (razón social) or person names to search. Batch: one search per name.
radicados	string[]	no	(empty)	Exact 23-digit radicado (process number) to look up directly. Batch.
tipoPersona	enum	no	jur	Whether the searched name is a legal entity (jur) or a natural person (nat).
despacho	string	no	(empty)	Optional court or city code prefix to narrow a name search at the source, for example 11001 for Bogotá.
onlyActive	boolean	no	false	When on, keep only processes flagged active by the source.
role	enum	no	any	Keep only cases where the searched name is demandante (plaintiff) or demandado (defendant). any keeps all.
departments	string[]	no	(empty)	Keep only cases whose department matches one of these values (contains, case-insensitive), for example ANTIOQUIA.
filedFrom	string	no	(empty)	Keep only cases filed on or after this date (YYYY-MM-DD).
filedTo	string	no	(empty)	Keep only cases filed on or before this date (YYYY-MM-DD).
lastActionFrom	string	no	(empty)	Keep only cases whose last action was on or after this date (YYYY-MM-DD).
withDetails	boolean	no	true	When on, fetch the detail page (type, class, ponente, court code, location). Adds the details event per process.
withActuaciones	boolean	no	true	When on (and details on), fetch the full actuaciones timeline. Turn off to skip movement pagination for a faster run.
maxRecords	integer	no	10	Maximum number of court process records across all searches. Free Apify plans are capped at 10.
withSummary	boolean	no	false	Paid AI add-on. Plain-language Spanish summary of the case. Charged only on usable AI output. Requires a paid Apify plan.
withTranslate	boolean	no	false	Paid AI add-on. Clear English translation and summary of the case. Charged only on usable AI output. Requires a paid Apify plan.
withExtract	boolean	no	false	Paid AI add-on. Extract structured case data (claim type, court, amounts). Charged only on usable AI output. Requires a paid Apify plan.

The role, departments, filedFrom, filedTo, and lastActionFrom filters are applied to the returned records; cases filtered out are never charged. despacho, onlyActive, and tipoPersona are applied at the source.

Output reference

One dataset item per judicial process. Types: string, integer, boolean, string[], object[], or null when the source value is absent.

Field	Type	Description
radicado	string	23-digit process number (unique per process).
despacho	string	Court or office handling the process.
courtCode	string	Full court code (codDespachoCompleto). Present with details on.
cityCode	string	City / court prefix (first 5 digits of the radicado).
filingYear	integer	Year the process was filed, derived from the radicado or filing date.
processType	string	Process type (tipo de proceso).
processClass	string	Process class (clase de proceso).
subClass	string	Process subclass (subclase).
recurso	string	Type of appeal or recurso.
ponente	string	Reporting magistrate or judge.
ubicacion	string	Current physical location of the file.
contenidoRadicacion	string	Filing content description.
department	string	Department (region) of the court.
demandantes	string[]	Plaintiffs.
demandados	string[]	Defendants.
otrosSujetos	string[]	Other subjects and interveners. Empty array when none.
sujetosProcesales	object[]	Structured parties. Each has name, role (demandante/demandado/otro), roleLabel, docType, docNumber. Document numbers are not exposed by the source and are null.
sujetosCount	integer	Number of parties.
partiesRaw	string	All parties with their roles as a single raw string.
filingDate	string	Filing date (YYYY-MM-DD).
lastActionDate	string	Date of the last case movement (YYYY-MM-DD).
lastActionDaysAgo	integer	Whole days between the last action and the run date.
lastUpdate	string	Date the source last updated the record (YYYY-MM-DD). Present with details on.
isPrivate	boolean	true when the process is marked private.
idProceso	integer	Internal process ID on the platform.
url	string	Rama Judicial consultation URL.
actuacionesCount	integer	Number of actuaciones (case movements).
actuaciones	object[]	Movement timeline. Each element has consecutivo, actuacion, anotacion, date, startDate, endDate, registeredDate, and hasDocuments. Present when details and movements are on.
aiSummary	string	AI plain-language Spanish summary, or null unless the add-on is enabled.
aiSummaryEn	string	AI English translation and summary, or null unless the add-on is enabled.
aiExtract	object	AI-extracted structured case data (claim type, court, amounts), or null unless enabled.
observedAt	string	ISO 8601 timestamp of when the record was collected.
error	string	null on success. On a failed or over-broad search, a single item with a populated error field is written instead, and it is not charged.

Example output record

Real record from a live run, input {"radicados": ["13001310300320170056402"], "withDetails": true, "withActuaciones": true}. Same process as the hero example, with the complete 7-movement actuaciones timeline:

{
  "radicado": "13001310300320170056402",
  "despacho": "DESPACHO 000 - TRIBUNAL SUPERIOR - CIVIL - FAMILIA - CARTAGENA *",
  "courtCode": "130012213000",
  "cityCode": "13001",
  "filingYear": 2017,
  "processType": "Sin Tipo de Proceso",
  "ponente": "MAG. JOHN FREDDY SAZA PINEDA",
  "ubicacion": "Secretaria",
  "department": "BOLÍVAR",
  "demandantes": ["GRUPO ARGOS S.A."],
  "demandados": ["WALFREDO PACHECO HERNANDEZ", "EDGARDO PACHECO POLO", "NARCILA PACHECO DE GUERRERO", "JUAN ANDRES PACHECO", "BONIFACIO PACHECO DE LA ROSA"],
  "sujetosCount": 6,
  "filingDate": "2019-08-27",
  "lastActionDate": "2019-12-18",
  "lastActionDaysAgo": 2443,
  "lastUpdate": "2026-08-05",
  "isPrivate": false,
  "idProceso": 59607293,
  "url": "https://consultaprocesos.ramajudicial.gov.co",
  "actuacionesCount": 7,
  "actuaciones": [
    {"consecutivo": 7, "actuacion": "Auto decide recurso", "anotacion": "CONFIRMA AUTO DE 30 DE AGOSTO DE 2019", "date": "2019-12-18", "startDate": null, "endDate": null, "registeredDate": "2019-12-18", "hasDocuments": false},
    {"consecutivo": 6, "actuacion": "Envío Expediente", "anotacion": "por medio de OFICIO No. 2737 DIRIGIDO A JUEZ TERCERO CIVIL DEL CIRCUITO DE CARTAGENA DEVOLVIENDO EXPEDIENTE DE 4 cuadernos con 38, 200, (201-400), (401-649) folios.", "date": "2019-10-16", "startDate": null, "endDate": null, "registeredDate": "2019-10-16", "hasDocuments": false},
    {"consecutivo": 5, "actuacion": "Fijacion estado", "anotacion": "Actuación registrada el 08/10/2019 a las 17:04:01.", "date": "2019-10-08", "startDate": null, "endDate": null, "registeredDate": "2019-10-08", "hasDocuments": false},
    {"consecutivo": 4, "actuacion": "Auto decide recurso", "anotacion": "SE CONFIRMA FALLO IMPUGNADO", "date": "2019-10-08", "startDate": null, "endDate": null, "registeredDate": "2019-10-08", "hasDocuments": false},
    {"consecutivo": 3, "actuacion": "Al despacho", "anotacion": "informando que se le dio cumplimiento a lo ordenado en el auto que le antecede y se recibió respuesta por parte del Juzgado Tercero Civil del Circuito de Cartagena.", "date": "2019-09-18", "startDate": null, "endDate": null, "registeredDate": "2019-09-18", "hasDocuments": false},
    {"consecutivo": 2, "actuacion": "Al despacho", "anotacion": "Rad. 2019-485-14", "date": "2019-08-28", "startDate": null, "endDate": null, "registeredDate": "2019-08-28", "hasDocuments": false},
    {"consecutivo": 1, "actuacion": "Reparto y Radicación", "anotacion": "REPARTO Y RADICACION DEL PROCESO REALIZADAS EL martes, 27 de agosto de 2019 con secuencia: 12599", "date": "2019-08-27", "startDate": null, "endDate": null, "registeredDate": "2019-08-27", "hasDocuments": false}
  ],
  "observedAt": "2026-08-26T12:28:20.980Z",
  "error": null
}

Run via API and CLI

Start a run and wait for it to finish, then read the dataset. Replace <TOKEN> with your Apify API token.

Run synchronously and get dataset items in one call:

curl -X POST "https://api.apify.com/v2/acts/scrapers_lat~colombia-rama-judicial-scraper/run-sync-get-dataset-items?token=<TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"searchNames":["GRUPO ARGOS S.A."],"tipoPersona":"jur","despacho":"11001","withDetails":true,"maxRecords":10}'

Start a run asynchronously:

curl -X POST "https://api.apify.com/v2/acts/scrapers_lat~colombia-rama-judicial-scraper/runs?token=<TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"radicados":["13001310300320170056402"],"withDetails":true,"withActuaciones":true}'

Apify CLI:

apify call scrapers_lat/colombia-rama-judicial-scraper \
  --input '{"searchNames":["GRUPO ARGOS S.A."],"tipoPersona":"jur","role":"demandante","maxRecords":10}'

Fetch results

Every run writes to a dataset. Fetch items as JSON, CSV, or Excel by changing format:

# JSON
curl "https://api.apify.com/v2/datasets/<DATASET_ID>/items?token=<TOKEN>&clean=true&format=json"

# CSV
curl "https://api.apify.com/v2/datasets/<DATASET_ID>/items?token=<TOKEN>&clean=true&format=csv"

# Paginate large datasets
curl "https://api.apify.com/v2/datasets/<DATASET_ID>/items?token=<TOKEN>&offset=1000&limit=1000"

<DATASET_ID> is returned as defaultDatasetId in the run object. Use offset and limit to page through large result sets. clean=true drops empty and internal fields.

Billing and limits

• Pay per result. You are charged per judicial process record returned (result event). See the pricing tab for the current per-result price.
• Details add-on. When withDetails is on, each process that is enriched with its detail page charges the details event. Turn it off for listing-only, lower-cost runs.
• Paid AI add-ons. ai_summary, ai_translate, and ai_extract are separate events, each billed only when they produce usable output. Leave them off to pay for results only.
• No charge on failure. If a run errors, a search is too broad, or a case is filtered out, the actor does not charge for it. Empty runs cost nothing.
• Spend cap respected. Set maxTotalChargeUsd on the run; once reached, the actor stops emitting and charging further billable results.
• Free Apify plans are capped at 10 records per run, and paid AI add-ons are disabled. Upgrade for higher maxRecords and the AI add-ons.

FAQ and troubleshooting

What is a radicado? The radicado is the 23-digit numero de radicación that uniquely identifies a Colombian judicial process, for example 13001310300320170056402. Put one or more in radicados to look up exact cases.

My search returned an error about too many records. Why? A broad company name can match more than a thousand processes, and the platform then asks for more specific criteria. Narrow the search by adding a despacho court or city code prefix, or by role, department, and date filters, or look up exact radicados. That error record is not charged.

Can I search by cédula or NIT (document number)? The public Consulta de Procesos platform does not offer a document-number search endpoint, so this actor searches by name and by radicado. Party document numbers are not published by the source, so docType and docNumber are returned as null.

How do I find only recently active cases? Set lastActionFrom to a date, and optionally onlyActive on. Each record also includes lastActionDaysAgo so you can sort by recency.

Company or person: which tipoPersona? Use jur for a legal entity (company, razón social) and nat for a natural person.

Why is the actuaciones array empty or missing? Turn withDetails and withActuaciones on to fetch the detail page and the movement timeline. Some processes also have no registered movements yet.

Do the AI add-ons need a paid plan? Yes. The AI summary, translate, and extract add-ons require a paid Apify plan and are charged only when they return usable output.

Is this an official Rama Judicial tool? No. This actor is independent and has no affiliation with the Rama Judicial of Colombia. It reads only data that is publicly available through the Consulta de Procesos platform.

Related scrapers

• Colombia Company Financials Scraper: Colombian company financial statements from Supersociedades.
• Argentina Companies Scraper: Argentine company registry and tax IDs.

More scrapers at scrapers.lat

Built and maintained by scrapers.lat, where we publish scrapers for US and Latin American public platforms: company registries, government data, finance, e-commerce and more. Browse the catalog or request a custom scraper at scrapers.lat.

---

Independent tool, not affiliated with the Rama Judicial of Colombia. Accesses only publicly available Consulta de Procesos data.