Read rediscount query result
Reads the result of a previously submitted rediscount consulta by its correlation id (the outbound NUOp). PENDING until BACEN answers, then ANSWERED — or TRUNCATED, which is its own terminal state rather than a flavour of ANSWERED. An open-position answer carries at most 40 operations, and when the day has more BACEN cuts it short and names a file holding the remainder. That file travels over a transport no SPB rail code touches, so the identifier is recorded for an operator to collect out of band and the answer is never presented as complete.
Authorizations
JWT bearer token issued by the identity provider.
Path Parameters
Correlation id returned by POST /v1/str/rediscount-queries (the outbound NUOp; 23 characters: ISPB[8]+DATE[8]+SEQ[7]).
23^[0-9A-Z]{8}[0-9]{15}$Response
OK
Request-scoped correlation identifier echoing X-Request-ID.
"req-7a3f9c2e"
Correlation id (the outbound NUOp).
"12345678202606150000014"
ISPB of the querying institution.
^[0-9A-Z]{8}$"12345678"
BACEN business date (DtMovto) the consulta asked about.
"2026-06-15"
PENDING until BACEN answers. ANSWERED once the whole answer arrived in the message itself and was projected. TRUNCATED whenever the projected rows are NOT the whole answer: BACEN either cut the message short (SitCons 5 or 7) or answered entirely by file (SitCons 6). In every one of those cases the missing part — the remainder, or the whole of it — exists only as a file named by fileIdentifier, retrievable out of band by an operator, and nothing in this rail fetches it. So TRUNCATED is never a complete position, and reading these rows as one understates it.
PENDING, ANSWERED, TRUNCATED "ANSWERED"
RDC message code that was put on the wire.
"RDC0006"
Identifier of the file holding the remainder of a TRUNCATED answer (IdentdArq). It is RECORDED so an operator can collect it out of band; nothing in this rail fetches it.
"RDC0006-20260615-0001"
Answer-completeness code BACEN sent (SitCons), verbatim.
"1"

