nautechsystems/nautilus_trader · error · BinanceSpotHttpError::ValidationError

BinanceSpotHttpError::ValidationError(message.into())

Error message

BinanceSpotHttpError::ValidationError(message.into())

What it means

command_validation_error wraps a message into BinanceSpotHttpError::ValidationError and returns it as an anyhow::Error. It is the adapter's standard way of reporting that a command (submit, modify, cancel, etc.) failed pre-flight validation before an HTTP request was made or based on a rejected response.

Source

Thrown at crates/adapters/binance/src/spot/http/client.rs:2590

    /// Returns the SBE schema ID.
    #[must_use]
    pub const fn schema_id() -> u16 {
        SBE_SCHEMA_ID
    }

    /// Returns the SBE schema version.
    #[must_use]
    pub const fn schema_version() -> u16 {
        SBE_SCHEMA_VERSION
    }

    /// Generates a timestamp for initialization.
    fn generate_ts_init(&self) -> UnixNanos {
        self.clock.get_time_ns()
    }

    fn command_validation_error(message: impl Into<String>) -> anyhow::Error {
        anyhow::anyhow!(BinanceSpotHttpError::ValidationError(message.into()))
    }

    fn response_parse_error(message: impl Into<String>) -> anyhow::Error {
        anyhow::anyhow!(BinanceSpotHttpError::ResponseParseError(message.into()))
    }

    /// Retrieves an instrument from the cache.
    fn instrument_from_cache(&self, symbol: Ustr) -> anyhow::Result<InstrumentAny> {
        self.instruments_cache
            .get_cloned(&symbol)
            .ok_or_else(|| anyhow::anyhow!("Instrument {symbol} not in cache"))
    }

    /// Caches multiple instruments.
    pub fn cache_instruments(&self, instruments: Vec<InstrumentAny>) {
        self.instruments_cache.rcu(move |cache| {
            for instrument in &instruments {
                cache.insert(instrument.raw_symbol().inner(), instrument.clone());

View on GitHub (pinned to 18893faf8b)

Solutions

1. Read the wrapped message to identify the exact invalid field
2. Validate order parameters (type, TIF, precision) against Binance spot rules before submission
3. Check exchangeInfo filters (LOT_SIZE, PRICE_FILTER, NOTIONAL) during strategy setup
4. Update to latest adapter version if validation is overly strict

// pre-validate against Binance spot rules: order type, TIF, quantity step, price tick
assert!(matches!(order_type, LIMIT | MARKET | LIMIT_MAKER | STOP_LOSS..));
assert!(qty % lot_size_step == 0);

match result { Err(e) if e.to_string().contains("ValidationError") => log_invalid_command_params(e), Err(e) => return Err(e), Ok(_) => continue }

When it happens

Trigger: Any spot HTTP client command whose parameters fail adapter validation — e.g. invalid symbol mapping, missing order fields, unsupported order type or time-in-force for Binance spot.

Common situations: Submitting order types Binance spot does not support (e.g. certain trailing-offset combos), wrong precision/quantity rounding, or strategy code constructing commands with invalid values.

Understand the failure class

Background: Schema validation failed / invalid input schema: payload rejected because its shape doesn't match the expected schema — this error's family across 28 libraries.

Related errors

• Unsupported `OrderSide` for Binance: {value:?}
• Invalid tickSize of 0 for symbol '{}', cannot create instrum
• custom data request requires `instrument_id` metadata
• Order type {order_type:?} requires a trigger price
• Conditional orders require a trigger price

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