Coin-M futures dapi/v1/income result differs from UI and transaction history file

API Futures API
1

Hello,
I’m trying to use Coin-M futures’ GET /dapi/v1/income endpoint (https://binance-docs.github.io/apidocs/delivery/en/#get-income-history-user_data) but I noticed that the income slightly differs from the website UI and transaction history file (last digit).
My guess is that the rounding is different between the API and the UI+file but I may be wrong.

You can see in the following API response and screenshots that the XLMUSD_PERP funding is 15.09154602 from the API and 15.09154603 in the file and UI.

API response
{'symbol': 'XLMUSD_PERP', 'incomeType': 'FUNDING_FEE', 'income': '15.09154602', 'asset': 'XLM', 'time': 1632931201000, 'info': 'FUNDING_FEE', 'tranId': 4956258083919547620, 'tradeId': ''}

Transaction History file (from https://www.binance.com/en/my/orders/futures/transactionhistory)

Screenshot from 2021-09-30 10-53-43
Screenshot from 2021-09-30 10-53-43952×23 3.64 KB

Website UI

Screenshot from 2021-09-30 10-53-27
Screenshot from 2021-09-30 10-53-271586×37 3.86 KB

Note: The website is showing UTC+9 so it is the same funding.

Is it an issue on my side, with the API or with the file+UI?
If it is an issue on Binance’s side, is it possible to have it fixed?

Regards,

2

that seems the issue from rounding.

3

Thank you for your reply dino, the data showed in the original message is the raw data from the API, website and history file. If it’s a rounding problem on Binance’s side, can it be fixed please?

4

Any chance of a reponse on this issue please?

5

@GG-lemon

The values from the API should now match the values from the UI.

Thanks for bringing this to our attention.

1 Like