COSS UPDATE: 20th November 2019
API & other improvements

An improved API documentation has already been circulated among a few members of the community for review. Their feedback is being incorporated. We are aiming for a release of the new documentation by next week.

The COSS platform has brought onboard additional specialist resources.

Their priorities cover resolving issues like:

- resolving issues faced by the CCXT platform in interacting with our APIs

CCXT is a library of exchange APIs. The COSS API is verified by CCXT and can be used by platforms integrating more than one exchange at a time. This bypasses the need to integrate each exchange’s APIs individually.

There’s a long standing issue reported by several CCXT users integrating COSS on https://github.com/ccxt/ccxt/issues/5591.

Resolving this issue will allow more trading platforms to easily integrate COSS and also resolve issues faced by Gimmer users trying to trade on COSS.

Error codes included in the API also require an update, allowing users to identify and resolve any errors faced when performing an integration.

- improving API performance

Large traders, market makers and liquidity providers regularly request a lower cancellation limit via our API which currently limits cancellation to 10 seconds since placing the order. This allows them to respond to market movements quicker.

Once a solution is deployed, we will be able to accept requests from traders who wish to be excluded from these limits. It will be made available to all API users by default at a later date.

We will begin to plan other major improvements and upgrades on the exchange following addressal of a few other important tasks assigned to the new resources.

Which includes…
[]
['Cryptocurrency Investment', 'Bitcoin', 'Cryptocurrency News', 'Ethereum', 'Cryptocurrency']