Documentation Index
Fetch the complete documentation index at: https://docs.judit.io/llms.txt
Use this file to discover all available pages before exploring further.
๐ค Thelawsuitobject is returned in JSON format. The root property that contains the lawsuit metadata is calledresponse_data. The history is returned in thestepsarray and the parties involved in thepartiesarray. Remember that authentication to query this object is done via theapi-keyheader, not a Bearer Token.
General Structure
The lawsuit JSON is organized into 5 main blocks:- Header (response_data): Metadata, judge, county, case value, and status.
- Parties (parties): Array containing the poles (active/passive), documents, and lawyers.
- Case Updates (steps): Array with the chronological history of case updates.
- Attachments (attachments): Array of documents (PDFs, HTML) linked to the case updates.
- Related (related_lawsuits): Array of attached or linked lawsuits.
Data Dictionary
1. Lawsuit Header (response_data)
| Property | Type | Description |
|---|---|---|
code | string | Unique lawsuit number in the CNJ standard. |
name | string | Description/Name of the lawsuit (e.g., โACTIVE PARTY X PASSIVE PARTYโ). |
area | string | Area of law (e.g., โDIREITO CIVILโ, โDIREITO ADMINISTRATIVOโ). |
subject / subjects | array | Subjects of the case, based on the CNJ unified table. |
classifications | array | Procedural classes (e.g., โPROCEDIMENTO COMUMโ), based on the CNJ. |
distribution_date | string | Date on which the lawsuit was filed/assigned at the court. |
instance | string | Degree of jurisdiction (e.g., โ1ยช INSTรNCIAโ, โ2ยช INSTรNCIAโ). |
judge | string | Name of the magistrate or responsible rapporteur. |
justice_description | string | Type of body (e.g., โJUSTIรA ESTADUALโ, โJUSTIรA FEDERALโ, โSTJโ). |
tribunal_acronym | string | Official acronym of the originating court (e.g., โTJSPโ, โTRF4โ). |
county | string | County where the action is running. |
city / state | string | City and state (Federative Unit) of the county. |
amount | number | Value assigned to the case. |
phase | string | Procedural phase (e.g., โCONHECIMENTOโ). (Not returned in Document Query) |
status | string | Macro-status of the lawsuit (โATIVOโ or โFINALIZADOโ). (Not returned in Document Query) |
situation | string | Granular status captured directly in the courtโs system. |
secrecy_level | integer | Level of secrecy (0 = Public. Levels 1 to 5 indicate degrees of restriction). |
2. Involved Parties (parties)
Array of objects representing the parties.
| Property | Type | Description |
|---|---|---|
name | string | Full name or company name of the party. |
main_document | string | Main CPF or CNPJ linked to the party. |
side | string | Pole in the lawsuit: ACTIVE (Plaintiff), PASSIVE (Defendant), INTERESTED, or UNKNOWN. |
person_type | string | Procedural role (e.g., โAUTORโ, โRรUโ, โTESTEMUNHAโ, โTERCEIROโ). |
documents | array | List of objects with document_type (e.g., โCPFโ, โCNPJโ) and document (the number). |
lawyers | array | List of lawyers associated with the party (contains name and oab). |
Notice about Lawyers: If the court does not clearly specify which party the lawyer belongs to, the lawyer object will be listed directly in the main
parties array, with a generic role/side.3. Case Update History (steps)
(Array absent in Document Query responses)
| Property | Type | Description |
|---|---|---|
step_id | string | Unique internal identifier of the case update. |
step_date | string | Date of the procedural case update. |
step_type | string | Code/Type of the case update mapped in the CNJ table. |
content | string | Full descriptive text of the case update (e.g., โAto ordinatรณrio praticadoโฆโ). |
private | boolean | Returns true if this specific case update runs under secrecy. |
4. Attached Documents (attachments)
(Array absent in Document Query responses)
| Property | Type | Description |
|---|---|---|
step_id | string | ID of the case update (step) that generated this attachment. |
attachment_date | string | Date the document was added. |
attachment_name | string | Title or name of the file (e.g., โPetiรงรฃo Inicialโ, โContestaรงรฃoโ). |
extension | string | Format of the extracted file (e.g., โPDFโ, โHTMLโ). |
Complete JSON Example (Standard Query)
Below is the typical structural representation returned by the Judit API when querying a complete judicial lawsuit:See response example
See response example
Integration Examples (Retrieving a Lawsuit)
Important: In the examples below, we are using the Synchronous Query Base URL of our Datalake to retrieve thelawsuitobject instantly. Remember to pass theapi-keyheader.
Next Steps
Now that you know the anatomy of a lawsuit, see how to capture them:- ๐ Enumerations and Domains: See the complete list of statuses, instances, and secrecy levels.
- ๐ Asynchronous Search: Learn how to request our bots to search for new lawsuits in the courts.