Digital Certificate Registration

curl --location 'https://crawler.prod.judit.io/credentials/certificate' \
--header 'api-key: <api-key>' \
--header 'Content-Type: application/json' \
--data '{
  "customer_key": "teste",
  "system_name": "ESAJ - TJSP - 1º grau",
  "file_base64": "<pfx-content-in-base64>",
  "password": "123456"
}'

curl --location 'https://crawler.prod.judit.io/credentials/certificate' \
--header 'api-key: <api-key>' \
--header 'Content-Type: application/json' \
--data '{
  "customer_key": "teste",
  "system_name": "ESAJ - TJSP - 1º grau",
  "file_base64": "<pfx-content-in-base64>",
  "password": "123456",
  "custom_data": {
    "secret": "JBSWY3DPEHPK3PXP"
  }
}'

{
	"message": "CERTIFICATE_CREATED",
	"customer_key": "teste",
	"subject_cn": "HOLDER NAME:12345678909",
	"not_after": "2027-01-01T00:00:00.000Z",
	"uploaded_at": "2026-07-31T17:00:00.000Z"
}

POST

credentials

certificate

curl --location 'https://crawler.prod.judit.io/credentials/certificate' \
--header 'api-key: <api-key>' \
--header 'Content-Type: application/json' \
--data '{
  "customer_key": "teste",
  "system_name": "ESAJ - TJSP - 1º grau",
  "file_base64": "<pfx-content-in-base64>",
  "password": "123456"
}'

curl --location 'https://crawler.prod.judit.io/credentials/certificate' \
--header 'api-key: <api-key>' \
--header 'Content-Type: application/json' \
--data '{
  "customer_key": "teste",
  "system_name": "ESAJ - TJSP - 1º grau",
  "file_base64": "<pfx-content-in-base64>",
  "password": "123456",
  "custom_data": {
    "secret": "JBSWY3DPEHPK3PXP"
  }
}'

{
	"message": "CERTIFICATE_CREATED",
	"customer_key": "teste",
	"subject_cn": "HOLDER NAME:12345678909",
	"not_after": "2027-01-01T00:00:00.000Z",
	"uploaded_at": "2026-07-31T17:00:00.000Z"
}

The certificate cannot be sent through the POST /credentials route. Certificate fields inside custom_data are rejected with the CERTIFICATE_FIELDS_NOT_ALLOWED error.

string

required

Content of the .pfx / .p12 (PKCS#12) file converted to Base64, on a single line, with no breaks. File must be at most 64 KB.

string

required

Password of the .pfx file. Not the court portal password.

string

System and court where the certificate will be used, for example ESAJ - TJSP - 1º grau. Use * to register it as a wildcard credential.

string

Credential identifier defined by you. If omitted, the default value * is used.

object

Extra credential data. Only send it when the court also requires two-factor authentication.

Show properties

string

2FA secret (secret) — the fixed setup key of the authenticator app, never the temporary 6-digit code.

curl --location 'https://crawler.prod.judit.io/credentials/certificate' \
--header 'api-key: <api-key>' \
--header 'Content-Type: application/json' \
--data '{
  "customer_key": "teste",
  "system_name": "ESAJ - TJSP - 1º grau",
  "file_base64": "<pfx-content-in-base64>",
  "password": "123456"
}'

curl --location 'https://crawler.prod.judit.io/credentials/certificate' \
--header 'api-key: <api-key>' \
--header 'Content-Type: application/json' \
--data '{
  "customer_key": "teste",
  "system_name": "ESAJ - TJSP - 1º grau",
  "file_base64": "<pfx-content-in-base64>",
  "password": "123456",
  "custom_data": {
    "secret": "JBSWY3DPEHPK3PXP"
  }
}'

{
	"message": "CERTIFICATE_CREATED",
	"customer_key": "teste",
	"subject_cn": "HOLDER NAME:12345678909",
	"not_after": "2027-01-01T00:00:00.000Z",
	"uploaded_at": "2026-07-31T17:00:00.000Z"
}

If a certificate for the same holder already exists in that credential, the message will be CERTIFICATE_UPDATED and the previous certificate is discarded.

Possible errors

Code	HTTP	When it happens
`PFX_MALFORMED`	400	Invalid Base64 or corrupted PFX file
`PFX_PASSWORD_INVALID`	400	Wrong file password
`PFX_NO_PRIVATE_KEY`	400	File has no private key
`PFX_NO_CERTIFICATE`	400	File has no certificate
`PFX_EXPIRED`	400	Certificate expired
`PFX_NOT_YET_VALID`	400	Certificate not valid yet
`PFX_TOO_LARGE`	400	File larger than 64 KB
`CERTIFICATE_HOLDER_MISMATCH`	409	New certificate belongs to a different holder (CPF/CN)
`CREDENTIAL_TYPE_CONFLICT`	409	A username/password credential already exists for the same credential and `customer_key` combination

Full guide, including converting the file to Base64 and the Postman walkthrough: Credentials Vault — digital certificate.

Authorizations

api-key

string

header

required

API key for authentication

Body

application/json

file_base64

string

required

PFX/P12 file content encoded as a single-line Base64 string

password

string

required

Password of the PKCS#12 file (not the court portal password)

system_name

string

e.g. "ESAJ - TJSP - 1º grau" or * (wildcard)

customer_key

string

Client-defined identifier for the credential. Defaults to *

custom_data

object

Extra credential data. Only required when the court also enforces two-factor authentication.

Show child attributes

Response

Certificate created or updated

message

enum<string>

Available options:

CERTIFICATE_CREATED,

CERTIFICATE_UPDATED

customer_key

string

subject_cn

string

Certificate holder (CN)

not_after

string<date-time>

Certificate expiration date

uploaded_at

string<date-time>

Requests · Asynchronous Queries

Responses · Query Results

Tracking · Monitoring

Lawsuits · Synchronous Queries (JUDIT Cache)

Lawsuits · Registration Data

Lawsuits · Lawsuit Attachments

Credentials Vault

Authorizations

Body

Response