Bitcoin exchange Bitfinex has recently unveiled a new suite of reporting tools with the aim of enabling users to have more control over trades and also provide them with useful information regarding activities on the exchange platform. Bitfinex added that users would be able to view account data as they please by removing data limits.

New Reporting Tools

The company stated that the UI of the new tools is premised on “modern web technology” thereby working on a better presentation of data and boosting responsiveness. The new toolkit is developed to be simpler and more accessible and to automatically compile an overview of account information when required as to be a similitude of the old account itself. The announcement reads:

“As institutions and professional traders enter the digital asset trading space, Bitfinex remains committed to creating the tools required to thoroughly meet their needs. We are of the belief that our suite of tools work to accelerate the rate of global adoption and help facilitate an increasingly mature market.”

The new toolkit is designed in a way that users can work offline as their activities would be recorded on a local database, with this, live internet connection is no longer needed. Also, the new kit is on the verge of transforming into an open-source solution that offers users customizing tools and submitting features to individual users.

 Bitfinex API

With the instrumentality of Bitfinex API, the new reporting suite will now offer a field wallet added to the end-point ledger, giving requisite information that identifies the wallet involved in movements. The list of virtual currencies available on the platform with ID and full name would be revealed by end-point ‘currencies.’ Information about the users’ profile would be brought up by ‘userInfo,’ with certain changes made to end-points ‘accountTrades’, ‘orderHistory’, ‘fundingOfferHistory’, ‘fundingLoanHistory’ and ‘fundingCreditHistory.’

Also, users will now have access to use the same tool locally on the Bitfinex web platform owing to the existence of authToken which substitute apiKeys.