Schema Communication (Official Justice Gazette)

🤖 The National Electronic Justice Gazette (DJEN) monitoring returns the communication object. Each object represents a DJEN publication that matched the monitored term. The root contains publication metadata (dates, court, type). Recipients are in the recipients array and their linked lawyers in recipient_lawyers.

General Structure

A communication JSON is organized into 4 main blocks:

Publication Metadata (root): Identification, dates, status, court and communication type.
Recipients (recipients): People directly mentioned in the publication — can be lawyers or non-lawyers (parties in the lawsuit).
Recipient Lawyers (recipient_lawyers): Lawyers linked to the parties, with OAB registration data.
Full Text (text): Complete content of the publication as extracted from the DJEN.

Data Dictionary

1. Publication Metadata (Object Root)

These properties appear directly at the root of the response_data object.

Required fields

Property	Type	Description
`communication_id`	string	Unique identifier of the communication in the Judit system.
`active`	boolean	Indicates whether the communication is active (`true`) or has been canceled (`false`).
`date_availability`	string (ISO 8601)	Date when the publication became available in the DJEN.
`date_shipping`	string (ISO 8601)	Dispatch/sending date of the communication by the court.
`hash`	string	Unique publication hash, identifier from the DJEN.
`lawsuit_code`	string	Linked lawsuit number in CNJ format (e.g., `"0000000-00.0000.8.00.0000"`).
`tribunal_acronym`	string	Official court acronym (e.g., `"TJSP"`, `"TJRJ"`, `"TRT2"`).
`status`	string	Publication status in the DJEN (e.g., `"P"` for published).
`text`	string	Full text of the publication as extracted from the National Electronic Justice Gazette.
`source`	string	Source system of the publication (e.g., `"pje"`, `"esaj"`).

Optional fields

Property	Type	Description
`classification_code`	string	Procedural class code associated with the communication.
`classification_name`	string	Procedural class name (e.g., `"ENFORCEMENT OF EXTRAJUDICIAL TITLE"`).
`date_cancellation`	string (ISO 8601)	Cancellation date of the communication, when applicable.
`reason_cancellation`	string	Reason for the cancellation of the communication, when applicable.
`api_id`	number	Internal ID of the communication in the source system.
`middle`	string	Abbreviated code of the publication vehicle (e.g., `"D"` for DJEN).
`full_middle`	string	Full name of the publication vehicle (e.g., `"NATIONAL ELECTRONIC JUSTICE GAZETTE"`).
`name_organ`	string	Name of the court organ responsible for the publication (e.g., `"1st CIVIL COURT"`).
`communication_number`	number	Sequential number of the communication within the DJEN edition.
`communication_type`	string	Communication type (e.g., `"INTIMATION"`, `"SUMMONS"`).
`document_type`	string	Type of published document (e.g., `"DECISION"`, `"ORDER"`, `"JUDGMENT"`).
`integrate_api`	boolean	Indicates whether the communication was integrated via an external API.

2. Recipients (`recipients`)

Array with the people directly mentioned in the publication — can be lawyers or non-lawyers (parties in the lawsuit). All fields are required.

Property	Type	Description
`communication_id`	number	Internal ID of the communication the recipient is linked to.
`name`	string	Full name of the recipient as it appears in the publication.
`side`	string	Party side in the lawsuit: `"Active"` or `"Passive"`.

3. Recipient Lawyers (`recipient_lawyers`)

Array with the lawyers linked to the communication recipients. All fields are required.

Link object root

Property	Type	Description
`id`	number	Unique identifier of the lawyer-communication link.
`lawyer_id`	number	Lawyer ID (reference to the `lawyer` object).
`communication_id`	number	Internal communication ID the lawyer is linked to.
`created_at`	string	Creation date of the link record.
`updated_at`	string	Last update date of the link record.

Nested `lawyer` object

Property	Type	Description
`id`	number	Unique lawyer identifier in the system.
`name`	string	Lawyer’s full name.
`license_code`	string	OAB registration number.
`license_state`	string	OAB state section (e.g., `"SP"`, `"RJ"`).

Payload Example (Communication)

{
  "page": 1,
  "page_count": 1,
  "all_count": 1,
  "all_pages_count": 1,
  "page_data": [
    {
      "request_id": "186e0ed5-4656-4fd8-8e07-76f755c44a9d",
      "response_id": "dd47b9fc-8f66-46b8-a31a-50a4718c9774",
      "origin": "tracking",
      "origin_id": "a94db796-9e35-4d0c-8e05-2a6b60f32a74",
      "response_type": "communication",
      "response_data": {
        "communication_id": "0E6hgZvG",
        "active": true,
        "classification_code": "12154",
        "classification_name": "ENFORCEMENT OF EXTRAJUDICIAL TITLE",
        "date_availability": "2026-05-20T00:00:00.000Z",
        "date_shipping": "2026-05-19T03:00:00.000Z",
        "recipient_lawyers": [
          {
            "lawyer": {
              "id": 10001,
              "name": "EXAMPLE LAWYER 1",
              "license_code": "0001",
              "license_state": "SP"
            },
            "lawyer_id": 10001,
            "communication_id": 600000001,
            "id": 1100000001,
            "created_at": "2026-05-19 11:44:08",
            "updated_at": "2026-05-19 11:44:08"
          }
        ],
        "recipients": [
          {
            "communication_id": 600000001,
            "name": "ACTIVE PARTY EXAMPLE",
            "side": "Active"
          },
          {
            "communication_id": 600000001,
            "name": "PASSIVE PARTY EXAMPLE 1",
            "side": "Passive"
          }
        ],
        "hash": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
        "api_id": 600000001,
        "middle": "D",
        "full_middle": "NATIONAL ELECTRONIC JUSTICE GAZETTE",
        "name_organ": "DISTRICT COURT - 1st CIVIL COURT",
        "communication_number": 2674,
        "lawsuit_code": "0000000-00.0000.8.00.0000",
        "tribunal_acronym": "TJXX",
        "status": "P",
        "text": "Full text of the publication as extracted from the DJEN...",
        "communication_type": "INTIMATION",
        "document_type": "DECISION",
        "integrate_api": false,
        "source": "pje"
      },
      "user_id": "00000000-0000-0000-0000-000000000000",
      "created_at": "2026-05-20T20:12:47.839Z",
      "updated_at": "2026-05-20T20:12:47.839Z"
    }
  ]
}

Next Steps

👉 Official Gazette Monitoring: See how to set up DJEN monitoring and receive publications via webhook.

Getting Started

Core Concepts

Data Models (Schemas)

Asynchronous Requests

Synchronous Requests

Tracking

Registration Data

Criminal Records

File Transfer

Credentials Vault

Webhook

Resources

General Structure

Data Dictionary

1. Publication Metadata (Object Root)

Required fields

Optional fields

2. Recipients (`recipients`)

3. Recipient Lawyers (`recipient_lawyers`)

Link object root

Nested `lawyer` object

Payload Example (Communication)

Next Steps

​General Structure

​Data Dictionary

​1. Publication Metadata (Object Root)

​Required fields

​Optional fields

​2. Recipients (recipients)

​3. Recipient Lawyers (recipient_lawyers)

​Link object root

​Nested lawyer object

​Payload Example (Communication)

​Next Steps

General Structure

Data Dictionary

1. Publication Metadata (Object Root)

Required fields

Optional fields

2. Recipients (`recipients`)

3. Recipient Lawyers (`recipient_lawyers`)

Link object root

Nested `lawyer` object

Payload Example (Communication)

Next Steps