AVavaprotocol
Wallets

List the authenticated user's smart wallets

Changed on

Preview wallet resolve. Authorize with a user Bearer JWT or a partner assertion (scope: read) whose sub is the owner EOA.

Wallets are stored per chain, so the listing is per chain too. The chainId query selects which one, on the same precedence as POST /wallets: explicit value, then the JWT aud chain, then the gateway default. A JWT minted for one chain can therefore list another's wallets without a second signature — it proves EOA ownership, which is chain-independent.

get/wallets

Request

  • Base URL
    https://api.avaprotocol.org/api/v1
  • Auth
    • HTTP bearer
    • or API key in header X-Partner-Assertion

Query parameters

chainIdinteger

The chain to operate on (a single value). Omit to use the aggregator default (the request's JWT aud chain, then the gateway default).

Response

All wallets for the authenticated user.

Example response

{
  "data": [
    {
      "address": "0x82F2Dd9a552a69f2ceD7Ff2D05c43aB8430158FB",
      "factoryAddress": "0x82F2Dd9a552a69f2ceD7Ff2D05c43aB8430158FB",
      "delegate": "0x82F2Dd9a552a69f2ceD7Ff2D05c43aB8430158FB"
    }
  ]
}

Changes

  • 6b505ebcf3f7Revision changes
    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

  • 4ebf07931311Revision changes
    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status