Receive and parse a remittance file
A caller POSTs the object key of a file already present in the shared inbound bucket, the institution id, and the SISBAJUD file-type code; the service runs the receive and parse pipeline synchronously. A bad body maps to 422; a missing inbound object to 404; a benign concurrent skip to 200.
Authorizations
JWT bearer token issued by the identity provider.
Body
The SISBAJUD file-type code.
"REMESSA"
The institution's BACEN CNPJ code (8 digits) used for file header validation.
"12345678"
The institution id the file belongs to.
"44444444-4444-4444-4444-444444444444"
The object key of the file already present in the shared inbound bucket.
"inbound/2026/07/14/remessa-001.txt"
Response
OK
The reception outcome (processed or skipped).
"processed"
The resolved SISBAJUD environment (processed outcomes only).
"production"
The persisted file id (processed outcomes only).
"dddddddd-dddd-dddd-dddd-dddddddddddd"
The skip reason (skipped outcomes only).
"skipped"

