Skip to main content

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.

New CNPJ format (IN 2229/24)Judit already accepts the new alphanumeric CNPJ format in compliance with the Brazilian Federal Revenue Normative Instruction No. 2229/2024.
  • Zero effort: no changes are required in your integration.
  • Test environment: use the document A1B2C3D4/E5F6-68 to validate the flow and receive a mock lawsuit in response.
The Grouped (Synthetic) Query delivers, in a single synchronous call, a statistical summary of every lawsuit linked to a document, grouped by class, subject, area, court, justice, phase, state, instance, party side and person type. Use it when the client needs a bird’s-eye view rather than the full list.
🤖 Endpoint: POST https://lawsuits.production.judit.io/lawsuits/synthetic. Synchronous response with aggregated counts. To list each lawsuit, use POST /lawsuits (Hot Storage). For a simple existence/count, use POST /lawsuits/count.

When to use

Executive dashboards

Judicial-exposure panels: counts per court, phase, instance, area — without listing every lawsuit.

Quick risk analysis

Onboarding or credit decisions: discover in milliseconds the judicial profile of a counterpart (civil vs. labor vs. tax).

Pre-segmentation

Before deciding between full or sample queries, see the size and distribution of the set.

Periodic reports

Weekly/monthly reports aggregated by portfolio without trafficking large lawsuit volumes.

Step 1: Create the Grouped Query (POST)

POST https://lawsuits.production.judit.io/lawsuits/synthetic

Examples by document type

{
    "search": {
        "search_type": "cpf",
        "search_key": "999.999.999-99"
    }
}

Payload parameters

ParameterTypeRequiredDescription
search.search_typestringYes"cpf", "cnpj", "oab" or "name".
search.search_keystringYesValue to search.
search.search_params.filterobjectNoStructural filters — same shape as the historical query.

Examples with filters

{
    "search": {
        "search_type": "cnpj",
        "search_key": "00.000.000/0001-00",
        "search_params": {
            "filter": {
                "side": "Passive",
                "tribunals": { "keys": ["TJSP","TRT2"], "not_equal": false },
                "amount_gte": 50000
            }
        }
    }
}

Request example (POST)

curl --request POST \
  --url 'https://lawsuits.production.judit.io/lawsuits/synthetic' \
  --header 'api-key: '"$JUDIT_API_KEY" \
  --header 'Content-Type: application/json' \
  --data '{
    "search": {
      "search_type": "cpf",
      "search_key": "999.999.999-99"
    }
  }'

Step 2: Read the response

The response is synchronous (HTTP 200) and aggregates the universe across multiple axes. lawsuits_count is the overall total; each axis is an array of { count, value }.
AxisWhat it groups
classificationsLawsuit classes (e.g. PROCEDIMENTO COMUM CÍVEL).
subjectsLawsuit subjects (e.g. ACIDENTE DE TRÂNSITO).
areasAreas of law (e.g. DIREITO CIVIL).
tribunalsCourt acronyms (e.g. TJSP, TRT1).
justicesBranch (State, Federal, etc.).
phasesCurrent procedural phase.
statesState (UF) where the lawsuit runs.
instancesInstance (1 or 2).
sidesSide of the searched party (PASSIVE, ACTIVE, INTERESTED).
person_typesParty type (REQUERENTE, AUTOR, RÉU, etc.).
lawsuits_countOverall total of lawsuits