> ## Documentation Index > Fetch the complete documentation index at: https://developers.portao3.com.br/llms.txt > Use this file to discover all available pages before exploring further. # List the realm's Pix keys > Lists the Pix keys of every wallet of every organization in your realm. The list is not paginated or sorted. Filter by `status`, which takes its values comma-separated (`?status=ACTIVE,REMOVED`). Only the keys of the environment in `x-environment` are listed, so send `x-environment: LIVE` for production keys. Removed keys and keys whose registration failed stay listed — filter by `ACTIVE` for the keys in use. ## OpenAPI ````yaml /api-reference/banking.openapi.json get /realms/{realmId}/pix-dict openapi: 3.0.3 info: title: Banking version: 1.0.0 description: >- Portão 3 banking API. Every endpoint requires a bearer token in the Authorization header (Authorization: Bearer ) unless its page states otherwise; see the Authentication guide. That requirement is not repeated per endpoint. Generated by tools/openapi from code (routes + security) and the hand-written spec (request/response bodies). Banking attaches a zod validationSchema at the route; request bodies are resolved from it (object + array roots). Responses have no presenter layer, so they stay tier=unknown. Confidence tiers: generated:typed=300 copied:manual=0 unknown=20. servers: - url: https://api.banking.v2.portao3.com.br/ description: production - url: https://api.banking.dev.3pers.com.br/ description: development security: [] tags: - name: Accounts - name: Account Limits - name: Wallets - name: Transaction Limits - name: Transfers - name: Cards - name: Card Limits - name: Cards 3DS - name: Pix Payments - name: Pix Keys - name: PIX Charges - name: PIX Automatic - name: PIX Initiation (Open Finance) - name: PIX Infractions (MED) - name: Boleto Payments - name: Boleto Charges - name: TED Payments - name: Transactions - name: Transaction Reversals - name: Spend Review - name: Cashback - name: Currency Codes paths: /realms/{realmId}/pix-dict: get: tags: - Pix Keys summary: List the realm's Pix keys description: Lists the Pix keys of every wallet of every organization in your realm. operationId: getRealmsByRealmIdPixDict parameters: - name: realmId in: path required: true description: |- ID of your realm. Format: `UUID` schema: type: string format: uuid example: f495ff0c-ab54-4f99-8e92-ca8682e4de9b - name: x-environment in: header required: false description: >- Environment whose Pix keys you list: `LIVE` (production) or `TEST` (sandbox). When you omit it, you get the `TEST` keys; any other value is rejected. schema: type: string enum: - LIVE - TEST example: LIVE - name: status in: query required: false description: >- Only keys in these statuses (case-insensitive): `ACTIVE`, `PENDING_CONFIRMATION`, `REMOVED` or `FAILED`. Other values match no key; each value can have at most 64 characters. --- Example: `?status=ACTIVE` schema: type: array items: type: string maxLength: 64 style: form explode: false responses: '200': description: Successful response content: application/json: schema: type: array items: type: object properties: _id: type: string description: ID of the Pix key — use it as `pixDictId`. example: 6728b1e2b4d3e80012c9a5a1 realmId: type: string description: ID of the realm. example: f495ff0c-ab54-4f99-8e92-ca8682e4de9b organizationId: type: string description: ID of the organization. example: c4bd3f21-dfbd-44e8-8055-68ba15bed410 accountId: type: string description: ID of the organization's account. example: 66f2a1c7b4d3e80012c9a0b4 walletId: type: string description: ID of the wallet that holds the key. example: 66f2a3d1b4d3e80012c9a0d2 environment: type: string enum: - LIVE - TEST description: 'Environment of the key: `LIVE` or `TEST`.' example: LIVE account: type: object properties: bankIspb: type: string description: >- ISPB code of Portão 3's banking partner, which holds the account (8 digits). `failed` when the key could not be registered. example: '12345678' branch: type: string description: >- Branch of the account. `failed` when the key could not be registered. example: '001' number: type: number description: >- Number of the account. `-1` when the key could not be registered. example: 10023456 type: type: string enum: - CACC - SLRY - SVGS - TRAN description: >- Type of the account: `TRAN` (payment account) for the wallets' keys. `CACC` when the key could not be registered. example: TRAN required: - bankIspb - branch - number - type description: The bank account the key points to. external: type: object properties: entryId: type: string description: >- ID of the key's entry in the Pix directory. `failed` when the key could not be registered. example: b6f1d2c3-4e5a-4b7c-9d8e-1f2a3b4c5d6e description: The key's identifiers in the Pix directory. status: type: string enum: - ACTIVE - PENDING_CONFIRMATION - REMOVED - FAILED description: >- Status of the key: - `ACTIVE` — registered: Pix sent to the key reach the wallet. - `PENDING_CONFIRMATION` — waiting for the confirmation code sent to the phone number or e-mail address (request one with `request-otp`, then confirm it). - `REMOVED` — removed from the wallet, or claimed by another institution. A removed key stays listed. - `FAILED` — registering failed; `failReason` says why. When the bank refused the key, nothing was registered; when it failed or didn't answer in time, the key may have been registered anyway. example: ACTIVE failReason: type: string description: >- Why the registration was refused, as ` | ` — for example `ENTRY_KEY_OWNED_BY_DIFFERENT_PERSON | The key already exists in the provider, but is linked to another person.` Only on `FAILED` keys. example: >- ENTRY_KEY_OWNED_BY_DIFFERENT_PARTICIPANT | The key is linked to another institution. type: type: string enum: - PHONE - EMAIL - CPF - CNPJ - EVP description: >- Kind of key: `EVP` (random key), `CNPJ`, `CPF`, `EMAIL` or `PHONE`. example: EVP value: type: string description: >- The key: a lowercase UUID for `EVP`, digits only for `CPF` and `CNPJ` (a CNPJ may carry letters in its first 12 positions), a lowercase e-mail address, or a phone number as `+` and digits (`+5511987654321`). On a `FAILED` key, what was sent — empty for an `EVP` that was never generated. example: 9f1c2e7a-4b3d-4e8f-a6c1-2d5b7e9f0a13 createdAt: type: string description: When the key was created (ISO 8601). example: '2026-11-04T14:05:12.348Z' updatedAt: type: string description: When the key was last updated (ISO 8601). example: '2026-11-04T14:05:12.348Z' __v: type: number description: Internal version of the record. example: 0 required: - _id - realmId - organizationId - accountId - walletId - environment - account - external - status - type - value - createdAt - updatedAt - __v description: >- A Pix key of a wallet: an alias (a random key, a CPF or CNPJ, an e-mail address or a phone number) registered in the Pix directory so that payers can send Pix to the wallet without its bank details. '422': description: >- `BAD_REQUEST` — The realm ID or a query parameter is invalid; `fields` lists each one. content: application/json: schema: type: object properties: traceId: type: string description: >- Identifier of the request that failed. Quote it when contacting support. example: 1-68ee2a1b-3c4d5e6f7a8b9c0d1e2f3a4b code: type: string enum: - BAD_REQUEST description: >- Stable, machine-readable error code. Branch on this, never on `message`. origin: type: string enum: - BANKING description: Service that produced the error. message: type: string description: >- Human-readable explanation. Its wording may change without notice. fields: type: array description: >- One entry per invalid request field (validation errors only). items: type: object properties: field: type: string description: >- Path of the invalid field, e.g. `label` or `values[0].value`. example: label message: type: string description: Why the field was rejected. example: label is required code: type: string description: >- `_` — e.g. `LABEL_REQUIRED`, `TYPE_ONE_OF`, `VALUES_VALUE_TYPE_ERROR`. example: LABEL_REQUIRED values: type: array items: type: string description: >- The accepted values, when the field is an enumeration. required: - field - message - code required: - traceId - code - origin - message example: traceId: 1-68ee2a1b-3c4d5e6f7a8b9c0d1e2f3a4b code: BAD_REQUEST origin: BANKING message: >- Bad Request: Your request is invalid or incomplete. Please make sure you are requesting with the right fields. fields: - field: realmId message: Invalid UUID code: REALMID_UUID ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.