Skip to main content
POST
Receber e analisar um arquivo de remessa

Autorizações

Authorization
string
header
obrigatório

JWT bearer token issued by the identity provider.

Corpo

application/json
fileType
string
obrigatório

The literal SISBAJUD file-type code — a 4-digit numeric code, NOT a descriptive label such as "REMESSA". Production: 5301 (remessa de bloqueio, 684-wide), 5303 (resultado de validação sintática, 24-wide), 5308 (requisição de informações AJUD308, 723-wide). Homologation: 5311, 5313, 5318 (same three kinds, in that order). Any other value is rejected with 422 / SBJ-0006.

Exemplo:

"5301"

institutionCode
string
obrigatório

The institution's BACEN CNPJ code (8 digits) used for file header validation.

Exemplo:

"12345678"

institutionId
string
obrigatório

The institution id the file belongs to.

Exemplo:

"44444444-4444-4444-4444-444444444444"

objectKey
string
obrigatório

The object key of the file already present in the shared inbound bucket.

Exemplo:

"inbound/2026/07/14/remessa-001.txt"

Resposta

OK

status
string
obrigatório

The reception outcome (processed or skipped).

Exemplo:

"processed"

environment
string

The resolved SISBAJUD environment (processed outcomes only).

Exemplo:

"production"

fileId
string

The persisted file id (processed outcomes only).

Exemplo:

"dddddddd-dddd-dddd-dddd-dddddddddddd"

reason
string

The skip reason (skipped outcomes only): 'lock_held' when another worker holds the file lock and is processing it, or 'skipped' for an idempotent re-delivery.

Exemplo:

"lock_held"