The current connector covers the Trading account

OKX separates Trading, Funding, Earn and Web3 product surfaces. The launch connector reads the account balance contract for Trading and does not fold other products into the total. Displaying the scope is more useful than a larger but ambiguous number that users cannot reconcile with the provider.

Read is the only required OKX permission

OKX credentials consist of an API key, secret and passphrase. Enable Read and keep Trade and Withdraw disabled. The passphrase is part of the credential and cannot be recovered from OKX if lost. Collect all three values securely, send them only to your backend and never retain them in browser storage.

Cash and available balances remain distinct

The Trading response contains currency-level cash and available values plus account valuation fields. The normalized account preserves supported quantities and prices positions independently. A Funding balance missing from this response is an intentional scope boundary, not a failed aggregation.

Signed refreshes need bounded retries

OKX signing includes provider-specific headers, timestamps and the passphrase. ChainsFlow API owns those details and maps provider failures into stable errors. Respect the synchronization cooldown and Retry-After, and reconcile account state after an ambiguous response instead of launching concurrent refreshes from multiple user sessions.

IP restrictions and inactivity rules affect keys

OKX can bind keys to IP addresses and applies provider security policies to unbound credentials. Configure restrictions for the actual server egress model and monitor official guidance. If a key expires or is rejected, ask the user for a replacement Read key rather than broader permissions or a trading credential.