Retrieve Details of a Legal Process by Number

Endpoint

GET https://api.verifik.co/v2/co/rama/proceso

Append the processNumber as the final path segment (for example GET …/rama/proceso/11001400301220098008000). The value is typically the llaveProceso returned by Colombian Legal Processes. The response includes process metadata, parties (subjects), and procedural steps (actions).

Headers

Name	Value
Accept	application/json
Authorization	Bearer <token>

Parameters

name	type	required	description
processNumber	string	yes	Path parameter: judicial process id (min. 7 characters, no spaces). Often copied from llaveProceso on the list endpoint.

Request

JavaScript

import axios from "axios";

const processNumber = "18738473";

const { data } = await axios.get(
	`https://api.verifik.co/v2/co/rama/proceso/${processNumber}`,
	{
		headers: {
			Accept: "application/json",
			Authorization: `Bearer ${process.env.VERIFIK_TOKEN}`,
		},
	},
);
console.log(data);

Python

import os, requests

process_number = "18738473"
url = f"https://api.verifik.co/v2/co/rama/proceso/{process_number}"
headers = {
    "Accept": "application/json",
    "Authorization": f"Bearer {os.getenv('VERIFIK_TOKEN')}",
}
r = requests.get(url, headers=headers)
print(r.json())

PHP

<?php

$processNumber = '123456789';
$client = new \GuzzleHttp\Client();

$response = $client->request(
  'GET',
  "https://api.verifik.co/v2/co/rama/proceso/{$processNumber}",
  [
    'headers' => [
      'Accept' => 'application/json',
      'Authorization' => 'Bearer ' . getenv('VERIFIK_TOKEN'),
    ],
  ],
);

echo $response->getBody();

Swift

import Foundation

let processNumber = "123456789"
let url = URL(string: "https://api.verifik.co/v2/co/rama/proceso/\(processNumber)")!
var request = URLRequest(url: url)
request.httpMethod = "GET"
request.setValue("application/json", forHTTPHeaderField: "Accept")
request.setValue("Bearer \(ProcessInfo.processInfo.environment["VERIFIK_TOKEN"] ?? "")", forHTTPHeaderField: "Authorization")

let task = URLSession.shared.dataTask(with: request) { data, _, _ in
  if let data = data { print(String(data: data, encoding: .utf8) ?? "") }
}
task.resume()

Response

200

{
  "data": {
    "actions": [
      {
        "actuacion": "XXXXXX XXXXX",
        "anotacion": "ARCHIVO FEBRERO DE 2014.PAQUETE 285.",
        "cant": "8",
        "codRegla": "00                              ",
        "consActuacion": "8",
        "conDocumentos": false,
        "fechaActuacion": "2014-02-10T00:00:00",
        "fechaFinal": "string",
        "fechaInicial": "string",
        "fechaRegistro": "2014-02-10T00:00:00",
        "idRegActuacion": "12345678",
        "llaveProceso": "11001310300520130078000"
      }
    ],
    "details": {
      "claseProceso": "Divisorios",
      "contenidoRadicacion": "ESCRITURA",
      "despacho": "JUZGADO 005 CIVIL DEL CIRCUITO DE BOGOTÁ ",
      "esPrivado": false,
      "fechaConsulta": "2021-12-17T15:53:20.15",
      "fechaProceso": "2013-11-28T00:00:00",
      "idConexion": "180",
      "idRegProceso": "123456",
      "llaveProceso": "12345678987654321",
      "ponente": "XXXX XXXX XXX XXXX",
      "recurso": "Sin Tipo de Recurso",
      "subclaseProceso": "Sin Subclase de Proceso",
      "tipoProceso": "Declarativo",
      "ubicacion": "Archivo",
      "ultimaActualizacion": "2021-12-16T18:27:25.95"
    },
    "processNumber": "18738473",
    "subjects": [
      {
        "cant": "2",
        "esEmplazado": false,
        "idRegSujeto": "15775331",
        "identificacion": "string",
        "nombreRazonSocial": "XXXX XXXX XXXX XXXX",
        "tipoSujeto": "Demandante"
      }
    ]
  },
  "signature": {
    "dateTime": "August 30, 2022 1:26 PM",
    "message": "Certified by Verifik.co"
  },
  "id": "ABC12"
}

404

{
  "code": "NotFound",
  "message": "Record not found."
}

409

{
  "code": "MissingParameter",
  "message": "\"processNumber\" length must be at least 7 characters long"
}

Features

• Case file detail: Court, matter type, class, and timeline fields from Rama Judicial.
• Parties: Demandantes, demandados, and related subjects when available.
• Actuaciones: Chronological procedural steps with annotations.

Use Cases

• Case monitoring: Follow a known llaveProceso after listing processes for a person or company.
• Due diligence: Pull structured court data for a specific file number.

Notes

• processNumber is a path segment, not a query parameter (some clients may label it processNumber in forms).
• 409 responses usually mean a missing or invalid processNumber (including shorter than 7 characters).