Skip to main content
GET
List MED fraud markers (local base)

Authorizations

Authorization
string
header
required

JWT bearer token issued by the identity provider.

Query Parameters

cpf_cnpj
string
deprecated

Deprecated: send taxId instead. Both names are accepted; sending both with different values is refused 400 PIX-0148. Restrict to the markers associated with this document. Required when created_from is absent.

Example:

"12345678901"

taxId
string

Restrict to the markers associated with this document. Required when created_from is absent. Replaces the deprecated cpf_cnpj, which is still accepted.

Example:

"12345678901"

created_from
string

dtHrCriacaoInicio — restrict to the markers created at or after this instant (aaaa-mm-ddTHH:mm:ss.sssZ). Required when cpf_cnpj is absent.

Example:

"2026-04-01T00:00:00.000Z"

ispb
string

The ISPB of the direct participant this read is made as. This deployment may act as SEVERAL direct SPI participants - one ISPB each, each with its own JDPI credential - and a fraud marker names no row this deployment holds, so this field is the only thing that says which JD instance to ask. OPTIONAL while it acts as a single participant: omit it and that one answers. 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 payer_ispb on the limits routes: never a credential, never read from a header or a path, and it never widens what your token can reach. Read as the SAME participant that created the marker, or the JD you ask has never heard of it. Sending it empty (ispb=) reads the same as omitting it.

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

"12345678"

Response

OK

data
object[] | null
required

The list of fraud markers.

dictCorrelationId
string

idCorrelacao — the DICT support identifier for this listing call; quote it to JD when disputing whether the read happened.

Example:

"a7f12465e19f5ca51329479a5bae60c2"

dictReturnedAt
string

dtHrRetornoDict — when DICT answered this listing (contract 2.19).

Example:

"2025-01-02T10:30:05.025Z"