Skip to main content
GET
Get PIX key entry details

Authorizations

Authorization
string
header
required

JWT bearer token issued by the identity provider.

Path Parameters

entryId
string
required

The PIX key value (URL-encoded).

Example:

"foo@bar.com"

Query Parameters

account_id
string
required

The CRM account id of the caller.

Example:

"acc-123"

ispb
string

The ISPB of the direct participant whose directory answers. This deployment may act as SEVERAL direct SPI participants - one ISPB each, each with its own customers and its own DICT credential - and this field is the only thing on the request that says which of them is read. 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 payerIspb on a transaction: never a credential, never read from a header or a path, and it never widens what your token can reach. Read the participant that holds the keys, or the listing comes back empty for an account that has them. Sending it empty (ispb=) reads the same as omitting it.

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

"12345678"

Response

OK

endToEndId
string
required

The SPI end-to-end identifier.

Example:

"E1234567890"

key
string
required

The PIX key value.

Example:

"foo@bar.com"

payee
object
required

The resolved recipient bank data.