Skip to main content
POST
Submit SLB0006 entry query

Authorizations

Authorization
string
header
required

JWT bearer token issued by the identity provider.

Headers

X-Idempotency
string
required

Idempotency key. Required on every mutation.

X-TTL
string

Idempotency key TTL in seconds.

Body

application/json
controlNumberSLB
string

Entry control number (NumCtrlSLB) — asks for that one entry (RSLB0006). Mutually exclusive with referenceDate.

Maximum string length: 20
Example:

"SLB20260915000000001"

entryKind
enum<string>

Optional debit/credit filter (TpDeb_Cred). It is a FILTER, not a mode: it composes with all three.

Available options:
D,
C
Example:

"D"

referenceDate
string

Reference date (DtRef) — asks for all entries of that date (RSLB0005). Mutually exclusive with controlNumberSLB.

Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}$
Example:

"2026-09-14"

Response

Accepted

correlationId
string
required

Request-scoped correlation identifier echoing X-Request-ID.

Example:

"req-7a3f9c2e"

id
string
required

Correlation id (the outbound NUOp). The answer leg is correlated to it.

Example:

"46026562202609150000001"

messageType
string
required

The SLB wire code that was submitted.

Example:

"SLB0002"

movementDate
string
required

BACEN business date (DtMovto) stamped on the frame, derived server-side.

Example:

"2026-09-15"

numCtrlPart
string
required

This participant's own control number for the message — the handle BACEN quotes back on the answer.

Example:

"20260915000000000001"

status
string
required

SUBMITTED when the message was queued for the rail, PENDING_APPROVAL when the configured alçada band parked it awaiting signatures.

Example:

"SUBMITTED"

submittedAt
string
required

RFC3339 UTC timestamp the message was submitted.

Example:

"2026-09-15T12:00:00Z"