> ## Documentation Index > Fetch the complete documentation index at: https://developers.circle.com/llms.txt > Use this file to discover all available pages before exploring further. # List all recipient addresses > Returns a list of recipient addresses that have each been verified and are eligible for transfers. Any recipient addresses pending administrator verification are not included in the response. ## OpenAPI ````yaml openapi/account.yaml get /v1/businessAccount/wallets/addresses/recipient openapi: 3.0.2 info: version: ${version} title: Core Functionality description: > All of Circle's APIs share a common set of core functionality that lets you manage your Circle Account in a programmatic way. With a Circle Account your business can deposit traditional money from 80+ countries and seamlessly convert them into "digital currency dollars": USDC. You can then use USDC for everyday payments and treasury flows. servers: - url: https://api-sandbox.circle.com - url: https://api.circle.com security: [] tags: - name: Balances description: Get information on settled and unsettled balances. - name: Payouts description: Create and get information on 1st party payouts. - name: Wires description: >- Create, get instructions, and get information on 1st party bank accounts for wire transfers. - name: CUBIX description: Create and get information on CUBIX accounts. - name: PIX description: Create and get information on PIX accounts. - name: Transfers description: Create and get information on 1st party transfers. - name: Addresses description: Generate and get information on blockchain addresses. - name: Deposits description: Get information on 1st party deposits. - name: Payments description: Create, cancel, refund, and get updates on card payments. - name: Settlement Bank Routing description: View and manage settlement bank routing preferences for fiat accounts. - name: Reporting description: >- Retrieve transaction and balance reports, including ISO 20022 (CAMT.053) statements and managed-payment reports. paths: /v1/businessAccount/wallets/addresses/recipient: get: tags: - Addresses summary: List all recipient addresses description: > Returns a list of recipient addresses that have each been verified and are eligible for transfers. Any recipient addresses pending administrator verification are not included in the response. operationId: listBusinessRecipientAddresses parameters: - $ref: '#/components/parameters/From' - $ref: '#/components/parameters/To' - $ref: '#/components/parameters/PageBefore' - $ref: '#/components/parameters/PageAfter' - $ref: '#/components/parameters/PageSize' responses: '200': description: Successfully retrieved a list of recipient addresses. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: title: listBusinessRecipientAddressesResponse properties: data: type: array items: $ref: '#/components/schemas/BusinessRecipientAddressObject' examples: response: value: data: - id: b8627ae8-732b-4d25-b947-1df8f4007a29 address: '0x8381470ED67C3802402dbbFa0058E8871F017A6F' addressTag: '123456789' chain: ALGO currency: USD description: My USDC address at a cryptocurrency exchange status: active '401': $ref: '#/components/responses/NotAuthorized' security: - bearerAuth: [] components: parameters: From: name: from description: Queries items created since the specified date-time (inclusive). in: query required: false schema: type: string format: date-time example: '2020-04-10T02:13:30.000Z' To: name: to description: Queries items created before the specified date-time (inclusive). in: query required: false schema: type: string format: date-time example: '2020-04-10T02:13:30.000Z' PageBefore: name: pageBefore description: > A collection ID value used for pagination. It marks the exclusive end of a page. When provided, the collection resource will return the next `n` items before the id, with `n` being specified by `pageSize`. The items will be returned in the natural order of the collection. The resource will return the first page if neither `pageAfter` nor `pageBefore` are specified. SHOULD NOT be used in conjuction with pageAfter. in: query required: false schema: type: string PageAfter: name: pageAfter description: > A collection ID value used for pagination. It marks the exclusive begin of a page. When provided, the collection resource will return the next `n` items after the id, with `n` being specified by `pageSize`. The items will be returned in the natural order of the collection. The resource will return the first page if neither `pageAfter` nor `pageBefore` are specified. SHOULD NOT be used in conjuction with pageBefore. in: query required: false schema: type: string PageSize: name: pageSize description: > Limits the number of items to be returned. Some collections have a strict upper bound that will disregard this value. In case the specified value is higher than the allowed limit, the collection limit will be used. If avoided, the collection will determine the page size itself. in: query required: false schema: type: integer minimum: 1 example: 5 headers: XRequestId: description: >- Universally unique identifier (UUID v4) for the request. Helpful for identifying a request when communicating with Circle support. schema: type: string format: uuid example: 2adba88e-9d63-44bc-b975-9b6ae3440dde schemas: BusinessRecipientAddressObject: type: object properties: id: $ref: '#/components/schemas/Id' address: $ref: '#/components/schemas/Address' addressTag: $ref: '#/components/schemas/AddressTag' chain: $ref: '#/components/schemas/Chain' currency: $ref: '#/components/schemas/Currency' description: $ref: '#/components/schemas/AddressDescription' status: type: string enum: - active - pending_verification - verification_succeeded Id: type: string description: Unique system generated identifier for the entity. format: uuid example: b8627ae8-732b-4d25-b947-1df8f4007a29 Address: type: string description: > An alphanumeric string representing a blockchain address. Formatting varies by blockchain. Be sure to preserve the exact formatting and capitalization of the address. **Important:** For Ripple (XRP) addresses, only the classic address format is supported (for example, `rPEPPER7kfTD9w2To4CQk6UCfuHM9c6GDY`). The `x-address` format is NOT supported currently (for example, `XV5sbjUmgPpvXv4ixFWZ5ptAYZ6PD2q1qM6owqNbug8W6KV`). example: '0x8381470ED67C3802402dbbFa0058E8871F017A6F' AddressTag: type: string description: >- The secondary identifier for a blockchain address. An example of this is the memo field on the Stellar network, which can be text, id, or hash format. nullable: true example: '123456789' Chain: type: string description: > A blockchain that a given currency is available on. **Note:** Arc (`ARC`) is only available in the sandbox environment (`api-sandbox.circle.com`). enum: - ALGO - APTOS - ARB - ARC - AVAX - BASE - BTC - CELO - CODEX - ETH - HBAR - HYPEREVM - INK - LINEA - NEAR - NOBLE - OP - PLUME - PAH - POLY - SEI - SOL - SONIC - SUI - UNI - WORLDCHAIN - XDC - XLM - XRP - ZKS - ZKSYNC Currency: type: string description: A currency associated with a balance or address. nullable: true enum: - USD - EUR - BTC - ETH - CIRBTC AddressDescription: type: string description: An identifier or sentence that describes the recipient. example: My USDC address at a cryptocurrency exchange responses: NotAuthorized: description: >- The request has not been applied because it lacks valid authentication credentials. headers: X-Request-Id: $ref: '#/components/headers/XRequestId' content: application/json: schema: type: object title: NotAuthorized required: - code - message properties: code: type: integer example: 400 message: type: string example: Something went wrong. example: code: 401 message: Malformed authorization. examples: response: value: code: 401 message: Malformed authorization. securitySchemes: bearerAuth: type: http scheme: bearer ````