Wallets and exchanges in one overview
Centrally held balances can appear beside on-chain holdings without being labeled as wallet assets. Provider and connection remain visible so you can understand where a balance is held and how it was retrieved.
Exchange portfolio tracker
Track exchange holdings beside your wallets
Part of a crypto portfolio often remains on centralized exchanges while other assets move to self-custodied wallets. Separate interfaces make the overall picture harder to read and can conceal different update times. AssetFable brings exchange balances, holdings, subaccounts, and snapshots into the same portfolio context as public wallet data.
The connection is explicitly designed for read-only API credentials. AssetFable does not request trading, transfer, or withdrawal permissions and does not execute trades or withdrawals at an exchange. You remain responsible for the key and can remove it in AssetFable as well as revoke it directly with the provider.
Centralized holdings with a clear permission boundary
The benefit comes from a traceable data connection, not from granting broader account access.
Read-only rather than trading access
API keys used with AssetFable must be restricted to viewing data. The app does not need permission to trade, transfer, or withdraw and is not a replacement for security-critical exchange controls.
Sync and snapshot context
Connection state, balances, holdings, subaccounts, snapshots, sync times, and errors can document how a value was retrieved. That context helps distinguish a recent sync from a connection that needs attention.
Server-side credential protection
The documented architecture stores credentials in encrypted form through Supabase Vault or server-side security mechanisms. This reduces unnecessary exposure but does not replace minimal permissions, account protection, and regular key review.
Connect an exchange carefully
Create a dedicated API connection with only the permissions needed to read portfolio information.
Create a read-only API key
Open the API settings at your exchange and enable viewing permissions only. Trading, transfers, and withdrawals must stay disabled. Use a dedicated key for AssetFable rather than reusing credentials from another service.
Validate the connection in AssetFable
Enter the fields required by the provider and review the validation response. Once connected, available balances, holdings, subaccounts, and sync context can be added to the portfolio view.
Monitor and revoke access when needed
Check connection state and sync time. After a provider change, unexpected error, suspected compromise, or account deletion, remove the connection in AssetFable and revoke the key directly at the exchange.
Provider availability and security limits
Read-only access still processes sensitive portfolio information and depends on a third-party interface.
- The documented integration scope mentions Bitpanda, Binance, Coinbase, and OKX. Actual availability and data fields can vary by region, account type, API version, and current product status.
- Exchange APIs can apply rate limits, enter maintenance, return incorrect permission responses, or delay balances. AssetFable cannot guarantee a complete or continuously current copy and does not perform substitute transactions during an outage.
- Encrypted storage is not an absolute security guarantee. Protect the exchange account with its available controls, never share credentials, and revoke a key immediately if compromise is suspected.
An exchange connection can process credentials, provider, status, balances, holdings, subaccounts, snapshots, sync times, errors, and audit events. It does not require a wallet seed phrase or a full payment card number.
Exchange portfolio tracker questions
Which permissions may my API key have?
Read-only permissions only. Do not enter a key that can trade, transfer, or withdraw. If the provider cannot separate those rights clearly enough, do not create the AssetFable connection.
Which exchanges are in scope?
The product and privacy documentation mention Bitpanda, Binance, Coinbase, and OKX. This does not guarantee every connection in every region or for every account. The current status displayed in the app is authoritative.
What happens when I disconnect an exchange?
AssetFable removes the internal connection and credentials under its deletion process. Revoke the API key at the exchange too, because only the provider can terminate its validity at the source.
Related topics
Add exchange context with minimum permissions
Check the available provider and create a separate read-only API key before connecting an account.