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-68to validate the flow and receive a mock lawsuit in response.
on_demand: true).
🤖 Endpoint:POST https://lawsuits.production.judit.io/entities.search_typeacceptscpf,cnpjorname.response_typeis alwaysentity. For real-time response (Receita Federal), sendon_demand: truein the payload.
When to use
Onboarding and KYC
Validate name, registration status and address during customer onboarding without extra friction.
Database enrichment
Update CRM/ERP records with consolidated data by CPF/CNPJ.
Anti-fraud
Cross-check user-supplied data against the official source in seconds.
Corporate group mapping
Use the response to discover branches and corporate relationships linked to a CNPJ.
Datalake vs. On-Demand (Federal Revenue)
| Trait | Datalake (default) | On-Demand (on_demand: true) |
|---|---|---|
| Latency | ms | seconds |
| Source | Judit cache | Brazilian Federal Revenue (live) |
| Freshness | Last Judit collection | Current Receita state |
| Cost | Lower | Higher |
| Best for | Fast onboarding, mass enrichment | Critical compliance, high-risk decisions |
Step 1: Create the query (POST)
POST https://lawsuits.production.judit.io/entities
Examples by document type
Payload parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
search.search_type | string | Yes | "cpf", "cnpj" or "name". |
search.search_key | string | Yes | Document or name to search. |
search.response_type | string | Yes | Always "entity". |
search.on_demand | boolean | No | If true, forces a live read from the Brazilian Federal Revenue. |
search.reveal_partners_documents | boolean | No | (CNPJ) Returns unmasked partner documents. |
Request example (POST)
Step 2: Read the response
The response comes in the same POST body. Main fields:| Field | Type | Description |
|---|---|---|
request_id | string | Unique query identifier. |
response_data | array | List of found entities (follows the Entity Schema). |
response_data[].entity_type | string | "person" (PF) or "company" (PJ). |
response_data[].main_document | string | CPF or CNPJ. |
response_data[].addresses | array | Associated addresses. |
response_data[].contacts | array | Phones and emails. |
response_data[].partners | array | (PJ) Partners and administrators. |
Response examples
Full structure of each item: see Entity Schema. Field glossary: Glossary.
When querying by CNPJ with
reveal_partners_documents: true, partner CPFs/CNPJs are returned without masking. Only use it when you have a clear legal basis (KYC, AML, due diligence) — and never persist the unmasked values longer than necessary.