Relating to this issue:
I managed to programatically import my conversion records by watching the network tab in Chrome then copying the data payload returned. I then saved this as json on my machine. I imported it using Typescript, then did a little converting the data into Koinly format. I then converted the newly formatted data to CSV and then uploaded my CSV successfully to Koinly without any issues.
The api endpoint with current query strings is:
https://www.binance.com/bapi/margin/v1/private/new-otc/query-trade-history?startTime=1636203600000&endTime=1638881999999&page=1&rows=20
I am not sure if the API key would work with this network call though, I couldnt see my api key at all in the headers. It seemed to have its own token in the headers under the csrftoken header which I havent bothered to work out where it comes from. Who knows, maybe there’s an endpoint that would do a token swap of your API key to obtain your csrftoken. Then Koinly could maybe do this integration automatically for people
I’m happy to share my typescript converter on github, you can find me [at]noccer on github or twitter, or just reply here with your interest.
Note: some web development experience/software will be required to run my converter
- chrome devtools network tab
- Postman if you want to extend range of conversions queried
- NodeJS with npm installed
My background:
- Frontend dev, specialising in api integrations. the Chrome Devtools Network tab helps pay my bills
