nautechsystems/nautilus_trader · error

No account state returned from OKX

Error message

No account state returned from OKX

What it means

After a successful get_balance() call, the client takes resp.first() to obtain the account state. OKX returned an empty data array, so `.ok_or_else` produces `No account state returned from OKX`. It means the API responded but contained no balance record for the account.

Source

Thrown at crates/adapters/okx/src/http/client.rs:2325

    /// Requests the account state for the `account_id` from OKX.
    ///
    /// # Errors
    ///
    /// Returns an error if the HTTP request fails or no account state is returned.
    pub async fn request_account_state(
        &self,
        account_id: AccountId,
    ) -> anyhow::Result<AccountState> {
        let resp = self
            .inner
            .get_balance()
            .await
            .map_err(|e| anyhow::anyhow!(e))?;

        let ts_init = self.generate_ts_init();
        let raw = resp
            .first()
            .ok_or_else(|| anyhow::anyhow!("No account state returned from OKX"))?;
        let account_state = parse_account_state(raw, account_id, ts_init)?;

        Ok(account_state)
    }

    /// Sets the position mode for the account.
    ///
    /// Defaults to NetMode if no position mode is provided.
    ///
    /// # Errors
    ///
    /// Returns an error if the HTTP request fails or the position mode cannot be set.
    ///
    /// # Note
    ///
    /// This endpoint only works for accounts with derivatives trading enabled.
    /// If the account only has spot trading, this will return an error.
    pub async fn set_position_mode(&self, position_mode: OKXPositionMode) -> anyhow::Result<()> {

View on GitHub (pinned to 18893faf8b)

Solutions

1. Log in to OKX and confirm the account exists and has a balance record (deposit or enable trading).
2. Verify the API key's account is the intended one and the request filters (ccy, inst_type) are not excluding all rows.
3. Handle the empty case in caller code by treating it as 'no state yet' instead of a hard failure if appropriate.
4. Retry after account initialization; enable trading/derivatives on the account if needed.

// Confirm the account has at least one balance record before relying on account state
// e.g. check via OKX web UI or a prior funded deposit.

let state = match client.get_account_state(account_id).await {
    Ok(s) => s,
    Err(e) if e.to_string().contains("No account state returned") => {
        log::warn!("OKX account has no balance records yet; using defaults");
        default_account_state(account_id)
    }
    Err(e) => return Err(e),
};

When it happens

Trigger: get_balance returns Ok with an empty payload — e.g. account not yet initialized for the requested product type, API key bound to no trading account, or OKX returning empty data array for a filtered query.

Common situations: Fresh OKX account with no funding/trading activity; querying with credentials whose account has no configured position mode or no balance records; wrong ccy/filters yielding zero rows.

Understand the failure class

Background: EmptyResultError / "no results found": when an API or scraper succeeds but returns zero rows — this error's family across 9 libraries.

Related errors

• instrument update lock poisoned
• option_summary_family_subs mutex poisoned
• Conditional order types must use OKXAlgoOrderType
• Invalid `OrderType` cannot be represented on OKX: {value:?}
• Timeout waiting for account {account_id} to be registered af

AI-assisted analysis of nautechsystems/nautilus_trader@18893faf8b (2026-09-08). Data as JSON: /api/errors/337cbcb67eb792aa. Report an issue: GitHub.