Skip to main content
🤖 Support: atendimento@judit.io or WhatsApp +55 11 92050-1949. Sales (new key, plans, feature enablement): comercial@judit.io or WhatsApp +55 11 93618-6732. Status: https://status.judit.io. When opening a ticket, include endpoint, HTTP status, date and time with time zone, request_id/tracking_id/response_id and the request body (no headers). Never send the api-key, not even masked.

​
Channels

Support by email

atendimento@judit.io — errors, unexpected behavior and integration questions.

Support by WhatsApp

+55 11 92050-1949 — quick integration questions and ticket follow-up.

Sales

+55 11 93618-6732 or comercial@judit.io — new API Key, plans, feature enablement and limits.

API status

Check for an ongoing incident before opening a ticket.

​
Before opening a ticket

1

Check the status

See status.judit.io. If there is an ongoing incident, follow it there.
2

Identify the error

Look up the HTTP code and error.name in Error Codes. If the response came with response_type: application_error, check the code in response_data on the same page.
3

Review the most common causes

  • api-key header present and without Bearer (Authentication).
  • Right host for the route (requests, tracking or lawsuits).
  • page_size between 5 and 100 on list routes, and both created_at_gte and created_at_lte sent on GET /requests (both are required).
  • Volume within the rate limit. On a 429, wait the time given in the Retry-After header.

​
What to send in the ticket

Copy the template below and fill it in. The more complete it is, the faster the diagnosis. In the request body, keep the search_key of the failing case, but anonymize personal data that is not needed for the diagnosis.
Do not send your api-key through any channel, not even partially or masked. Judit identifies your account by the request_id, tracking_id or response_id and will never ask for your key.

​
Information by type of problem

  • request_id returned by POST /requests.
  • Current request status (GET /requests/{request_id}) and how long it has been in it.
  • For divergent data: the search_key (CNJ, CPF, CNPJ, OAB or name), what came in the response and what the court shows, ideally with a screenshot or link to the public search.
  • tracking_id and the tracking status (GET /tracking/{tracking_id}).
  • Date of the last update received and what was expected (e.g. a step published by the court on DD/MM that did not arrive).
  • Registered callback_url and whether it is the account URL or was sent in the request.
  • Affected request_id or tracking_id and, if any, the callback_id received.
  • What your server answered (HTTP status and response time) at the time of the problem.
  • Lawsuit CNJ, instance and attachment_id.
  • HTTP status and message received on download.

​
Scope