Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

help with okex v3 spot cancel_batch_orders

See original GitHub issue

OS: mac/ubuntu 16.04
Programming Language version: python
CCXT version: latest
Exchange: okex v3
Method: spot_post_cancel_batch_orders

import ccxt

ex = ccxt.okex3({
    'apiKey': '',
    'secret': '',
    'password': ''
})

result = ex.spot_post_cancel_batch_orders(
    params={
        'instrument_id': 'BTC-USDT',
        'order_ids': ['3135975779928064', '3135975777510400']
    }
)

The above code gives me error:

Traceback (most recent call last):
  File "/home/ubuntu/workspace/yurenji/bricks/okex-cancel-batch.py", line 11, in <module>
    'order_ids': ['3135975779928064', '3135975777510400']}
  File "/home/ubuntu/.pyenv/versions/3.6.5/envs/bricks/lib/python3.6/site-packages/ccxt/base/exchange.py", line 433, in inner
    return entry(_self, **inner_kwargs)
  File "/home/ubuntu/.pyenv/versions/3.6.5/envs/bricks/lib/python3.6/site-packages/ccxt/base/exchange.py", line 462, in request
    return self.fetch2(path, api, method, params, headers, body)
  File "/home/ubuntu/.pyenv/versions/3.6.5/envs/bricks/lib/python3.6/site-packages/ccxt/base/exchange.py", line 458, in fetch2
    return self.fetch(request['url'], request['method'], request['headers'], request['body'])
  File "/home/ubuntu/.pyenv/versions/3.6.5/envs/bricks/lib/python3.6/site-packages/ccxt/base/exchange.py", line 551, in fetch
    self.handle_errors(response.status_code, response.reason, url, method, headers, http_response, json_response)
  File "/home/ubuntu/.pyenv/versions/3.6.5/envs/bricks/lib/python3.6/site-packages/ccxt/okex3.py", line 2615, in handle_errors
    raise ExchangeError(feedback)  # unknown message
ccxt.base.errors.ExchangeError: okex3 {"message":"Invalid JSON format"}

I am not sure am I using the api correctly, or there is a bug with the api. Can you help me a bit here?