Wallaby
  • Introduction
    • Welcome
    • Getting Started
    • Key Architecture Overview
    • SDK vs API
    • Authentication Overview
    • Security Overview
      • Wallaby System Security
      • Securing User Access Token
      • Securing API keys
      • Securing Device Auth Key
      • Securing the Seed Phrase
        • API only: Choosing encryption factors for the seed phrase
  • Capabilities
    • Core Wallet
      • Wallet Creation
      • Wallet Recovery
      • Wallet Export
      • Wallet Import
      • Seed Phrase Recovery (Beta)
    • Wallet Services
      • Asset Listings By Wallet Holders
      • Transfers
      • Spending Authorization
    • Wallet Data
      • View Assets, Addresses, & Balances
      • Transaction History & Status
      • Service Availability
  • Consumer Application SDK
    • SDK Quick Start
    • Authentication with the SDK
      • Account Creation
      • Login
      • Refresh Access
      • Update Client Public Key
    • Core Wallet SDK
      • Creating a wallet with the SDK
      • Recovering a wallet with the SDK
      • Exporting a wallet with the SDK
      • Importing a wallet with the SDK
    • Wallet Services SDK
      • Spending Authorization (Allowance) with the SDK
      • Transfers with the SDK
        • Use Case: Preparing a Transfer
    • Wallet Data SDK
      • Assets, Addresses, & Balance Fetching with the SDK
      • Transaction History with the SDK
      • Transaction Status with the SDK
      • Service Availability with the SDK
  • Consumer Application APIs
    • API Quick Start
    • API Authentication
      • Sign Up
      • Sign In
    • Core Wallet APIs
      • Creating a wallet with APIs
      • Recovering a wallet with APIs
      • Export a wallet with APIs
      • Import a wallet with APIs
    • Wallet Data APIs
      • Assets, Addresses, & Balance Fetching APIs
      • Transaction History APIs
      • Transaction Status APIs
    • Wallet Services APIs
      • Asset Listings By Wallet Holders API
      • Transfer API
      • Spending Authorization (Allowance) API
      • Algorand Opt In
    • Blockchain Specific APIs
      • Algorand Only APIs
      • EVM Only APIs
    • Error Codes
  • Wallet Administration
    • Admin Applications
      • Admin Authentication
      • Admin Security
      • Programmatically Listing Assets with the SDK
      • Programmatically Listing Assets as a Business
    • Admin Portal
      • Asset Listings By Your Business
        • Manually List Assets
        • Automate Listing Assets
Powered by GitBook
On this page
  • Use Case Examples
  • How to fetch assets, addresses, and balances
  1. Capabilities
  2. Wallet Data

View Assets, Addresses, & Balances

PreviousWallet DataNextTransaction History & Status

Last updated 11 months ago

One unique aspect of our wallet is that we've made assets a part of the core model. This means that each time a wallet is created, assets are initialized. The assets that are initially included are determined by assets listed as default by your business.

An asset that is part of a wallet has an associated address that it can be sent and received. New assets can be added by the wallet holder or by your business. To learn more about how wallet holders can manage (add, hide, remove) assets, view the wallet service -> Asset Listings By Wallet Holders. To learn more about how you can list assets in embedded wallets, check out Asset Listings By Your Business.

Use Case Examples

The benefit of a headless solution is that you can always customize the experience as per your use case.

Asset Overview Pages

On pages where you want to provide an overview of multiple assets, we provide the ability to pull that data all at once. This is often utilized when trying to give the wallet holder a full picture of their holdings, but may be useful in other scenarios as well.

{wireframes of standard asset overview page & available assets for payment use case}

Asset Oriented Pages

Depending on the use case, the current page of your application may be oriented around a specific asset. In this case, you can pull data for that asset specifically (including asset information, balance, and address) and display it as desired.

{wireframes of standard asset details page & item details page for a game}

Address Oriented Pages

On pages that are address oriented, you will need to utilize the same asset endpoints. You can grab the native asset for each blockchain and the address associated with that asset. This enables you to create address oriented We currently do not support multiple addresses per blockchain. However, if you'd like to request this capability please reach out to our team.

{wireframes of standard address listings and contact pages}

Other

If you'd like to fetch balances at any point to restrict experiences to token holders, you are able to do that with balance APIs.

{wireframes of token gated page and token gated functionality}

If you have some other unique use cases that can't be serviced with our existing APIs, please reach out to our team.

How to fetch assets, addresses, and balances

Page cover image