SISBAJUD error list

Error format The Lerian SISBAJUD Mensageria and the Lerian SISBAJUD executor use the same error codes, SBJ-0001 to SBJ-0011, with the same HTTP statuses. A license refusal answers 403 with an LCS- code. An operation error uses RFC 9457 problem details with the application/problem+json media type:

{
  "type": "https://errors.lerian.studio/v1/SBJ-0001",
  "title": "Bad Request",
  "status": 400,
  "detail": "institutionId path parameter must be a valid non-nil UUID.",
  "code": "SBJ-0001"
}

Field definitions

code – A stable identifier for the error, in the form SBJ-NNNN. Branch on this value.
type – A URI that identifies the error in the Lerian error catalog. Built as https://errors.lerian.studio/v1/<code>.
title – The HTTP status text (for example, Bad Request).
status – The HTTP status code.
detail – Guidance for this occurrence of the error. For 5xx responses, the detail carries the static text internal error, so use code to branch.
errors – Optional list of per-field validation details, each with a message and a location.

Some refusals happen before the request reaches an operation, for example an unsupported method or a rate limit. They answer the same code and title in a plain JSON body. The execution API, which the executor calls on the Mensageria, is different: its 409 and 422 responses use a problem body without an SBJ- code.

Client errors

`code`	Description	Status
SBJ-0001	The request has malformed syntax. Check the path identifiers, the timestamp format, and the field lengths.	400
SBJ-0003	Authentication failed. Send a valid bearer token.	401
SBJ-0004	The caller identity lacks permission for this resource.	403
SBJ-0005	The resource does not exist. Check the identifier in the path.	404
SBJ-0007	The request conflicts with the current state of the resource, such as a duplicate create or a request that already reached a terminal state.	409
SBJ-0010	The request payload, or the file content the request asked for, is above the accepted size.	413
SBJ-0006	The syntax is correct, but the service cannot process the request. A value falls outside the accepted set, or the resource is in the wrong state for the operation.	422
SBJ-0009	The caller sent too many requests in the current window. Wait for the number of seconds in the `Retry-After` header, then send the request again.	429
SBJ-0011	A client error outside the codes above, such as an unsupported HTTP method. The response keeps its original status, so read the HTTP status of the response.	Other `4xx`

Server errors

`code`	Description	Status
SBJ-0002	The service failed unexpectedly. A server error with no other code also answers `SBJ-0002`. Send the request again, and contact support if the failure continues. For a key rotation, read Credentials and key rotation before you send it again.	500
SBJ-0008	A dependency this endpoint needs is unavailable. Contact your platform team if the failure continues.	503

SISBAJUD Mensageria · Institutions

SISBAJUD Mensageria · Orders and files

SISBAJUD Mensageria · Monitoring

SISBAJUD Mensageria · Return files

SISBAJUD Mensageria · LGPD requests

SISBAJUD Mensageria · Security

SISBAJUD Mensageria · Compliance

SISBAJUD Mensageria · Lerian STA dead-letter

SISBAJUD executor · Institutions and Midaz connector

SISBAJUD executor · Orders that need attention

SISBAJUD executor · Ledger routing

SISBAJUD executor · Security

SISBAJUD executor · Audit

Error handling

SISBAJUD error list

Client errors

Server errors

​Client errors

​Server errors

Client errors

Server errors