ccxt: Binance started throwing 'Not all sent parameters were read'

OS: macOS Catalina
Programming Language version: TypeScript/JavaScript node v13
CCXT version: 1.29.50

import * as ccxtpro from 'ccxt.pro';
const b = new ccxtpro.binance();
b.enableRateLimit = true;
await b.createOrder('ETH/USDT’, ‘limit’, ‘sell’, 5.3, 244.94, {
  "type": "LIMIT”,
  "timeInForce": "GTC",
  "reduceOnly": true,
});

// Body of request: timestamp=XXXX&recvWindow=5000&symbol=ETHUSDT&type=LIMIT&side=SELL&quantity=5.3&price=244.94&timeInForce=GTC&reduceOnly=true&signature=XXXX

Throws error

{"code":-1104,"msg":"Not all sent parameters were read; read '9' parameter(s) but was sent '10'."}

Started happening just today. Same for another pair, just ‘Market’ type

arguments for create order: 'EOS/USDT' , 'market', 'buy', 409.9, null, {
  "type": "STOP_MARKET",
  "stopPrice": 2.772,
  "quantity": 409.9,
  "closePosition": true
}

-> {"code":-1104,"msg":"Not all sent parameters were read; read '8' parameter(s) but was sent '9'."}

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 17 (11 by maintainers)

Commits related to this issue

ccxt.d.ts order type definition fix #7082 — committed to ccxt/ccxt by kroitor 4 years ago

Most upvoted comments

I think TypeScript def should be updated then:

 export interface Order {
        id: string;
        datetime: string;
        timestamp: number;
        lastTradeTimestamp: number;
        status: 'open' | 'closed' | 'canceled';
        symbol: string;
        **type: 'market' | 'limit';** <-- should have other types as well or just 'any'
        side: 'buy' | 'sell';
        price: number;
        average?: number;
        amount: number;
        filled: number;
        remaining: number;
        cost: number;
        trades: Trade[];
        fee: Fee;
        info: any;
    }

with type=‘stop_market’ as:

const type: any = 'stop_market'; // then just call createOrder with this parameter as type-arg

all works then. Thanks a lot!

radiant-alex on Jun 8, 2020

Ah, seems during refactoring I removed “future” type! Thanks a lot for your time! Issue is resolved now!

radiant-alex on Jun 7, 2020