[cryptocom] fetch_my_trades does not work when specifying since=

• OS: Mac OS X
• Programming Language version: Python 3.8.9
• CCXT version: 1.67.21

import time
import ccxt.async_support as ccxt

ONE_HOUR_IN_MS = 1000 * 60 * 60 * 1

def now_milliseconds():
    return int(time.time() * 1000)

params = {
            'apiKey': key,
            'secret': secret,
            'verbose': True,
        }
exchange = ccxt.cryptocom(params)
trades = await exchange.fetch_my_trades(since=now_milliseconds()-ONE_HOUR_IN_MS)

  File "/Volumes/Data/personal/newbot/core/exchange/exchange.py", line 69, in fetch_trades
    trades = await self._exchange.fetch_my_trades(since=self._ts_last_fetch_trades)
  File "/Volumes/Data/personal/newbot/venv/lib/python3.8/site-packages/ccxt/async_support/cryptocom.py", line 1023, in fetch_my_trades
    response = await getattr(self, method)(self.extend(request, query))
  File "/Volumes/Data/personal/newbot/venv/lib/python3.8/site-packages/ccxt/async_support/base/exchange.py", line 103, in fetch2
    return await self.fetch(request['url'], request['method'], request['headers'], request['body'])
  File "/Volumes/Data/personal/newbot/venv/lib/python3.8/site-packages/ccxt/async_support/base/exchange.py", line 168, in fetch
    self.handle_errors(http_status_code, http_status_text, url, method, headers, http_response, json_response, request_headers, request_body)
  File "/Volumes/Data/personal/newbot/venv/lib/python3.8/site-packages/ccxt/async_support/cryptocom.py", line 1725, in handle_errors
    raise Exception(self.id + ' ' + message)
ccxt.base.errors.BadRequest: cryptocom INVALID_DATE_RANGE

For instance, it seems that inserting end_ts along with start_ts fixes the problem (in cryptocom.py).

[oliviera9]

Thanks @kroitor. I also contacted Crypto.com to understand if ours is just a workaround to a problem of their API. From the docs, it seems end_ts is not required… Let you know

[kroitor]

@oliviera9 thx for pointing it out, fixed in CCXT 1.67.66, the new build will arrive in ~20 minutes. Please, let us know if that solves the issue for you or not.