List bound wallets

List all wallets currently bound to a user.

GET /api/v4/dexbuilder/wallet/list

List wallets

cURL

curl --request GET \
  --url https://api.dexbuilder.com/api/v4/dexbuilder/wallet/list \
  --header 'KEY: <api-key>' \
  --header 'SIGN: <api-key>' \
  --header 'Timestamp: <api-key>' \
  --header 'X-User-Wallet-Address: <x-user-wallet-address>'

200

Example

{
  "code": 0,
  "message": "success",
  "reason": "<string>",
  "trace_id": "<string>",
  "data": {
    "items": [
      {
        "wallet_id": "<string>",
        "address": "<string>",
        "status": "<string>",
        "is_primary": true,
        "bound_at": 123,
        "vm": "<string>"
      }
    ]
  }
}

List all wallets currently bound to a user.

Use a Broker API Key and pass the target user’s wallet in X-User-Wallet-Address. The gateway checks that the wallet belongs to your Broker. See Broker API Key and signing.

​

Usage notes

• The response lists all bound wallets without pagination. Each wallet’s vm identifies the virtual machine type (evm or solana); query asset networks for the specific network. bound_at is a Unix timestamp in milliseconds.

Authorizations

KEY · string · header · required

Broker API Key

Timestamp · string · header · required

Unix timestamp in seconds

SIGN · string · header · required

Hexadecimal HMAC-SHA512 signature generated with the Broker Secret Key

Headers

X-User-Wallet-Address · string · required

Target user's wallet address. The gateway verifies that the user belongs to the current Broker.

Response

200

application/json

Query successful

code · integer

Business code; 0 indicates success

Example:

0

message · string

Human-readable message; success responses use success

Example:

"success"

reason · string

Error reason identifier; usually empty on success

trace_id · string

Trace ID to provide when requesting support

data · object

Show child attributes