Wallet State

Use these reads to explain token movements and inspect wallet configuration. Send your server API key and use the Swig config address in wallet routes.

​

What you can query

​

Filters and results

• Set network=NETWORK_MAINNET or network=NETWORK_DEVNET on wallet and rent-recipient reads. Policy lookup takes its ID, without a network.
• Token history accepts limit: the default is 25 and the maximum is 100. It returns recent entries without a continuation cursor.
• Use decimal-string amountRaw for exact token arithmetic. Display amounts and USD values serve presentation; token movements are relative to the wallet, while DEX actions describe individual venue operations.
• Token-history and role reads use recorded wallet data. The rent-recipient endpoint reads finalized chain state; an absent recipient on a valid config differs from an account or RPC error.

​

Quota

Each admitted call consumes one API request, including a retry or a call that later returns an error. These reads share the plan’s API-request allowance with other metered operations; they do not use DEX queries. See pricing and quotas.

​

Reference and SDK examples

• Wallet REST fields
• Read balances for holdings and USD values
• Wallet-read SDK examples
• Rent-recipient REST fields
• Rent-claimer SDK examples
• Public wallet lookup and status for client-side wallet discovery