Create a MED value recovery
Opens a value recovery as the creator PSP (JDPI recuperacao-valores/incluir, contract 2.20). The creator ISPB is derived from configuration. grafoRastreamento.vlrMinTransacao is a graph-traversal FILTER threshold, never a posting amount.
Authorizations
JWT bearer token issued by the identity provider.
Headers
Idempotency key for this write: any stable business string you choose, sent as the X-Idempotency request header - the same header, by the same name, that the Midaz ledger takes, so one integration sends one thing by one name. Send the SAME value again to retry safely: the plugin projects it deterministically into the GUID form JDPI requires (contract 6), so a repeat lands in the same JDPI dedup slot inside JD's 24h window and the operation is applied once. The raw value is never forwarded verbatim, so correlate JDPI-side logs with the projection rather than with what you sent. The header is REQUIRED: omitting it is refused 400 PIX-0061 before any JDPI call. BREAKING CHANGE: this value used to be the body field idempotencyKey, which no longer exists.
"med-recovery-2024-0001"
Body
Creator-contact email (required).
"ops@example.com"
Creator-contact phone (required).
"+5511999999999"
EndToEndId of the root transaction being recovered.
"E1234567820240101000000000000001"
Situation code (0=Golpe, 1=Nao autorizada, 2=Coercao, 3=Acesso fraudulento, 4=Outros, 5=Desconhecida).
0
Free-text detail; required when situationType=4 (Outros).
"Suspected scam."
Optional graph-traversal FILTER parameters; omit to use JDPI defaults.
The ISPB of the direct participant this operation acts as. This deployment may act as SEVERAL direct SPI participants - one ISPB each, each with its own customers and its own JDPI credential - and this field is the only thing on the request that says which of them acts. OPTIONAL while it acts as a single participant: omit it and that one acts. REQUIRED once it acts as several - omitted is 422 PIX-0127, and an ISPB this deployment does not act as is 422 PIX-0128. It is ROUTING DATA you supply and guarantee, exactly like payerIspb on a transaction: never a credential, never read from a header or a path, and it never widens what your token can reach. It also selects the JDPI channel the call goes out on, so a MED write made under the wrong one reaches a JD that has never heard of this institution. Send it as an absent key, not an empty string; an empty value is refused 400 PIX-0061.
^[0-9]{8}$"12345678"
Response
Accepted
True when the return deadline has been reached or passed (computed at read time); false when no deadline is set.
false
Creator-contact email.
"ops@example.com"
Creator-contact phone.
"+5511999999999"
JDPI creation timestamp (RFC 3339 UTC).
"2024-01-01T12:00:00.000Z"
ISPB of the recovery creator.
"12345678"
EndToEndId of the root transaction being recovered.
"E1234567820240101000000000000001"
Value-recovery GUID (the natural key).
"b2c3d4e5-f6a7-8901-bcde-f23456789012"
Situation code (0..5).
0
Human-readable situationType label.
"Golpe/Estelionato"
stRecValores lifecycle code (0=created .. 6=cancelled).
0
Human-readable stRecValores label.
"Criada"
JDPI last-modification timestamp (RFC 3339 UTC) — the watermark.
"2024-01-01T12:05:00.000Z"
Free-text detail (required when situationType=4 Outros).
"Suspected scam."
idCorrelacao — the DICT support identifier for this consultar call; quote it to JD when disputing whether the read happened.
"a9f13566e19f5ca51329479a5bae60c5"
dtHrRetornoDict — when DICT answered this consultar (contract 2.21).
"2025-08-27T10:30:05.025Z"
Creator-side 72h return deadline (RFC 3339 UTC; contract §2.22/§5), from the analysis stage close; null unless this institution is the creatorIspb on an analyzed recovery.
"2024-01-04T12:00:00.000Z"

