Pular para o conteúdo principal
GET
Consult a PIX Automatico schedule situation

Autorizações

Authorization
string
header
obrigatório

JWT bearer token issued by the identity provider.

Parâmetros de caminho

endToEndId
string
obrigatório

The payment-transaction id (32-char).

Exemplo:

"E00038166202409171500y6j6mt9l0pi"

Parâmetros de consulta

ispb
string

The ISPB of the direct participant this consult is made AS. It is ROUTING DATA you supply and guarantee - never a credential, never read from a header or a path, and it never widens what your token can reach. While exactly ONE participant of this deployment holds this recurrence, the recorded row names the direct participant whose books it lives in, and that is authoritative: naming that one changes nothing, naming another is refused. It DECIDES when TWO do - this deployment can be both PSPs of one recurrence inside its own economic group, and then it holds one row per side, in two participants' books, with no way to choose between them. OPTIONAL in every other case: omit it and the row, or the tenant default when there is no row, answers. Omitting it with a row on each side is 422 PIX-0127, an ISPB this deployment does not act as is 422 PIX-0128, and one that holds none of the recorded rows is 400 PIX-0061. Sending it empty (ispb=) reads the same as omitting it.

Pattern: ^[0-9A-Z]{8}$
Exemplo:

"12345678"

Resposta

OK

endToEndId
string
obrigatório

The payment-transaction id (32-char).

Exemplo:

"E00038166202409171500y6j6mt9l0pi"

localStatus
string
obrigatório

Local ScheduleStatus projected from the JDPI situation.

Exemplo:

"Accepted"

localStatusKnown
boolean
obrigatório

False when the JDPI situation carries no projected local status.

Exemplo:

true

payer
object
obrigatório

The scheduled pagador.

purpose
integer<int64>
obrigatório

finalidadeAgendamento (0=first attempt, 1=post-due retry, 2=resend after a settlement error). Always present, including 0.

Exemplo:

0

recipient
object
obrigatório

The scheduled recebedor.

recurrenceId
string
obrigatório

The recurrence id (RR...).

Exemplo:

"RR0435879820240605njua7shf40o"

stJdPi
integer<int64>
obrigatório

JDPI overall situation (-1/0/9/10/11).

Exemplo:

9

stJdPiProc
integer<int64>
obrigatório

JDPI intermediate situation (0/1/2/5/7/8/9/10/11).

Exemplo:

9

acceptRejectAt
string

Accept/reject timestamp (dtHrAceiteRejeite, UTC).

Exemplo:

"2024-09-17T15:10:05Z"

amount
integer<int64>

Scheduled amount in centavos.

Exemplo:

55000

cancellations
object[] | null

Cancellation history (cancelamento).

debtor
object

The scheduled devedor; absent when the debtor is the payer.

dueDate
string

Due date (aaaa-mm-dd).

Exemplo:

"2024-09-24"

errorCode
string

JDPI error code.

Exemplo:

""

errorDesc
string

JDPI error description.

Exemplo:

""

infoBetweenClients
string

Free-text receiver-to-payer info.

Exemplo:

""

pendingReason
enum<string>

Set only on the by-endToEndId consult, never on the list: why the payer's §5.4.2 debit, which the SPI already settled, is not yet in the payer's ledger. INSUFFICIENT_BALANCE: the ledger refused it for funds, and JD's redelivery posts it once the payer is funded. TRACER_DENIED: the client's Tracer refused it (a rule or a limit), and JD's redelivery posts it once the Tracer lets it through. No deadline is known. Absent when nothing waits, and when the consult names a participant other than the payer's.

Opções disponíveis:
INSUFFICIENT_BALANCE,
TRACER_DENIED
Exemplo:

"INSUFFICIENT_BALANCE"

recipientReceivedAt
string

Recipient PSP reception timestamp (UTC).

Exemplo:

"2024-09-17T10:25:49Z"

reconciliationId
string

The receiver conciliation id.

Exemplo:

"JDPI2024091700000000000000000000001"

requestedAt
string

JDPI request timestamp (UTC).

Exemplo:

"2024-09-17T10:10:05Z"

scheduleStatus
integer<int64>

stAgendamento (0=Aceito, 1=Rejeitado). Absent when JDPI did not report it.

Exemplo:

0

situationAt
string

Situation timestamp (UTC).

Exemplo:

"2024-09-18T16:34:18Z"

waitingSince
string<date-time>

With pendingReason: when this deployment first tried to post the debit (UTC).

Exemplo:

"2026-10-25T12:00:00Z"