OneBalance
OneBalance
  • Welcome to OneBalance
  • OneBalance Toolkit
    • Introduction
    • Get Started with OneBalance SCA
      • Setup OneBalance Toolkit with Privy
        • Step 1: Setting up Privy
        • Step 2: Setting configurations
        • Step 3: Initializing and Depositing onto the OneBalance Smart Account
        • Step 4: Displaying Chain-Aggregated Balances
        • Step 5: Fetch a quote for transaction execution
        • Step 6: Signing transactions with Privy
        • Step 7: Executing transactions
        • Step 8: Getting execution status
      • Contract calls guide
        • Usage code samples
  • OneBalance vision
    • Our vision
      • Mission of OneBalance
      • Use Cases
      • Credible Accounts and Credible Stack
      • Fellowship of OneBalance
      • Glossary
    • Why resource locks?
      • Technical Details
        • Resource lock
        • Permissions
        • Credible accounts
        • Credible Commitment Machine (CCM)
        • FAQ
          • How does this relate to account abstraction and 4337?
          • Where does the OneBalance account live?
          • Are OneBalance accounts non-custodial?
      • Credible Stack Deep Dive
        • Apps
        • SDK providers
        • Wallets / WaaS
        • Solver Networks
        • Oracle Providers
        • Data Providers
  • Other
    • OneBalance Demo App
      • Roadmap
      • Privacy Policy
      • Terms and Conditions
    • OneBalance Brand Assets
Powered by GitBook
On this page
  1. OneBalance Toolkit
  2. Get Started with OneBalance SCA
  3. Setup OneBalance Toolkit with Privy

Step 4: Displaying Chain-Aggregated Balances

PreviousStep 3: Initializing and Depositing onto the OneBalance Smart AccountNextStep 5: Fetch a quote for transaction execution

Last updated 7 months ago

You can access the relevant API endpoint for aggregated balances .

This API aggregates balances across the chains supported by the application and takes resource locks into account. When funds on the source chain are locked for asynchronous cross-chain execution, the balance may differ from the direct sum of RPC-based balances.

Example client-side query for retrieving balances:

fetch(`https://be.onebalance.io/api/balances/aggregated-balance?address=${'<ONEBALANCE SCA ADDRESS HERE>'}`, {
    headers: {
      "x-api-key": '<YOUR ONEBALANCE API KEY HERE>',
    },
  })

The address expected in the Search Params of the request is the OneBalance SCA you have retrieved from the /predict-address endpoint previously.

For more details, see the implementation in our sample application .

here
here