Skip to main content
Rama Judicial is Colombia’s national judicial branch registry. Croma exposes five endpoints over it: search processes by party, list the cases a document number is a party to, resolve a case by its registration number (radicación), which returns case metadata plus action history in a single call, and the email directory, twice over: the official mailbox of every despacho judicial and administrative area, browsable by place and specialty, or resolved directly from a court code or a radicado.

Search processes

POST /co/rama-judicial/cases-by-entity/v1 Live finds processes by entity name.

List cases by document

POST /co/rama-judicial/cases-by-document/v1 Live lists the cases a document number is a party to. It matches the document, not the name, so it also finds cases where the person was registered with one surname or a misspelled name, and it does not return namesakes.
Returns found, the document, total, truncated and cases[]. Every case carries registration_number, case_class, department, city, court and is_private. Pass a registration_number to the resolve-by-radicación endpoint for the parties and actuaciones of a public case.
A document with no cases returns found: false with HTTP 200, not an error. A private case is listed with is_private: true and has no further detail. At most 100 cases are listed per document: when there are more, total carries the real count and truncated is true.
Courts register cases in more than one system. A complete check of a person runs this endpoint and the search by party: each finds cases the other does not.

Resolve by radicación

POST /co/rama-judicial/cases-by-radicado/v1 Live resolves a case by its 23-digit registration number and returns metadata plus the first 40 actuaciones (actions) available. When no public case matches, found is false and primary_case is null.

Resolve many radicados (batch)

POST /co/rama-judicial/cases-by-radicado/v1/batch Live resolves up to 50 radicados in one request. Items are resolved concurrently and returned in the same order, each with its own status, so one bad radicado never fails the batch.
Each item counts as one request against your quota. See Batch requests for the response envelope and partial-failure handling.

Find a court’s email

POST /co/rama-judicial/emails-search/v1 Dataset Searches the judicial branch’s official mailbox directory: every despacho judicial and administrative area, filterable by place, kind of office, specialty, seccional, or the court code that prefixes every radicado.
Returns as_of (how current the data is), the applied filters, total, page, per_page, total_pages, count and results[], ordered by office name. Every result carries email, name, account_type (“Despacho Judicial” or “Área”), corporation, specialty, department, city, district (the seccional), court_code, and the canonical *_key twins the filters match by prefix.
The directory is served from Croma’s own copy, refreshed weekly from the Rama Judicial’s official directory, so searches answer fast and do not depend on the upstream being reachable. as_of says when the copy was last brought up to date.

Resolve a court’s email from a case

POST /co/rama-judicial/emails-by-court/v1 Dataset Resolves the official mailbox of one court from its 12-digit code, or directly from a full radicado. No paging: every account the directory holds for the code comes back at once, the despacho’s own mailbox first.
Returns as_of, found, the (sliced) court_code, count and mailboxes[], each with the same fields as an emails-search result.
A code the directory does not hold returns found: false with HTTP 200, not an error. Some courts publish no dedicated mailbox and are served by a centro de servicios; searching the email directory by place and specialty is the fallback.
The case endpoints reach a live upstream that can be slow or briefly unavailable, and may return 502 upstream_error; retry with backoff. The email directory is served from Croma’s own copy and does not depend on it.

Full reference

Schemas, all response fields, and an interactive playground.