Skip to main content
GET
Wallet Details
Returns wallet details, a structured funding block describing both funding paths (external deposit and vault allocation), and — for backward compatibility — a flat funding_instructions string.

Response

Fields

Top level

funding.external_deposit

The Deposit to Wallet path. This is the universal funding method: an external on-chain USDC transfer into the wallet’s address. It works for every org regardless of signing mode.

funding.vault_allocation

The Allocate from Vault path. This is an internal vault → pocket transfer, and it is only available when the server holds the vault private key (i.e., the org is in full / server-signed mode). Browser-signed orgs cannot allocate.

reason_unavailable values

Funding modes at a glance

In v1, every AXON wallet is reachable via the external deposit path. Vault allocation is an optimisation for server-signed orgs: it avoids an on-chain round-trip by moving balance inside the same custody boundary.

Error handling

  • 404 NOT_FOUND — wallet_id doesn’t exist or the caller isn’t authorized to see it.
  • VAULT_ALLOCATION_UNAVAILABLE is never returned by this GET — it surfaces from POST /v1/wallets/:id/fund and POST /v1/orgs/:id/transfers/fund when a caller tries to allocate on a browser-signed org. This GET route tells you ahead of time whether that call would succeed (funding.vault_allocation.available).