Reference
API Limitations
Provider APIs do not always expose complete account history. This table records current Valo importer support by provider and product area, so additional API connections can be added as new rows over time.
Coverage table
Current importer support
| Provider | Spot | Staking | Convert | Futures | Margin | Notes |
|---|---|---|---|---|---|---|
Trading 212 | Partial | N/A | N/A | N/A | N/A | Trading 212 states that the Public API is beta and limited to Invest and Stocks ISA accounts. Valo imports account data, positions, and filled order history where the API exposes it. Multi-currency detail, cash movements, dividends, pies, corporate actions, and other non-trade activity may still need manual review. |
Kraken | Supported | Partial | Partial | Not imported | Not imported | Valo currently uses Kraken spot balances, trade history, and ledgers. Funding transfers, staking/Earn rewards, margin, futures, and other advanced activity may be incomplete or require manual entries. Balance differences are shown for review and are not converted into taxable synthetic trades. |
Coinbase | Supported | Partial | Partial | Not imported | N/A | A view-only Coinbase Developer Platform key gives Valo balances, Advanced Trade fills, and the Coinbase app ledger. App buys and sells, conversions priced at their market value, and outbound sends are imported; sends are held for review. Staking and Earn rewards, incoming transfers, futures, and perpetuals are not imported and appear as balance differences. Coinbase requires an ECDSA key for these APIs. |
Interactive Brokers | Partial | N/A | N/A | Not imported | Not imported | IBKR offers individual accounts no unattended API other than the Flex Web Service, so Valo reads an Activity Flex Query you create. Stock, ETF, fund, and crypto trades import at execution level with commissions and stamp duty, plus open positions and cash. Options, futures, CFDs, and FX trades are skipped. Dividends, interest, deposits, and withdrawals are not imported. IBKR posts activity after its daily statement cycle, so trades appear the next day, and each request covers at most 365 days. |
Note: The notes column is intentionally conservative. If a provider exposes data but Valo does not import or reconcile it today, the table marks that area as partial or not imported.
Before connecting
Manual checks still matter
- 01Create read-only or query-only API keys. Do not grant withdrawal, transfer, or order-placement permissions.
- 02Compare imported balances and positions against the broker or exchange after the first sync.
- 03Review activity that often sits outside simple trade history: deposits, withdrawals, dividends, rewards, corporate actions, funding fees, and internal transfers.
- 04Add or adjust manual entries where provider records are unavailable or where Valo marks a balance difference for review.
Sources
Provider documentation can change without notice. These notes were checked on .
Trading 212 Public API limitationsTrading 212 historical events endpointsKraken trade history endpointKraken ledgers endpointKraken Spot REST Earn guideKraken Futures API introductionCoinbase Advanced Trade API referenceCoinbase App transactions APICoinbase App API key authenticationIBKR Flex Web Service guideIBKR Activity Flex Query referenceDelta article used for table-format inspiration