The current scope is the OKX Trading account

ChainsFlow reads non-zero assets from the OKX account balance endpoint for the Trading account. Funding, Earn and Web3 wallet balances are separate product surfaces and are not folded into the total without a supported API contract.

Choose Read and keep Trade and Withdraw disabled

OKX defines separate Read, Trade and Withdraw permissions. A portfolio key needs Read only. Trade can place or cancel orders and initiate funding transfers, while Withdraw can move assets; neither belongs on a balance-tracking credential.

OKX reports cash and available balances

The Trading account response includes cash balance, available balance and account valuation fields. The integration normalizes the per-currency quantities without claiming that a Funding balance or a different OKX product is present.

History coverage remains explicit

Portfolio snapshots establish the value series, and supported bills or transfer history can improve cash-flow adjustments. Provider windows, permissions and unavailable historical prices can make the estimate incomplete, so the UI labels coverage rather than hiding the limitation.

The passphrase is part of the credential

OKX requires the API key, secret key and the passphrase chosen when the key was created. The passphrase cannot be recovered by OKX if lost. Store the three values carefully, verify that only Read is enabled and revoke the key in OKX after removing the connection.