Today I'm rolling out a new version of the Bitcoin-Central backend.
It introduces heavy architectural changes to the way things work :
- The precision of the trading engine is pushed to a full 8 decimal places
- The execution of trade orders becomes asynchronous
- The execution of outbound transfers becomes asynchronous
- Bugs are fixed on the way depth is shown in the order book
- E-mails are sent asynchronously, leading to better overall responsiveness
- A private websocket over HTTPS user specific channel is deployed, allowing to listen for account events as they happen
- A public websocket endpoint pushes the ticker updates as they happen
Unfortunately, due to the deep nature of these changes it is not possible to keep the API as is (responding synchronously to calls).
As a consequence, some calls (transfer money, place trade order) won't be usable until they are replaced with asynchronous versions.
A new API will be progressively rolled-out, it should be much simpler to use and comprehend, it will be versioned, be OAuth2 compliant, and expose much less of our internal data model in order to be much more intuitive.
Please in this thread
to tell me which API calls are the highest priority for you.