search

gateio / gateapi-go

100 stars 32 forks source link

APIv4 transaction and position reporting issue: SHIB5L_USDT/SHIB5S_USDT #30

Open marosier opened 2 years ago

marosier commented 2 years ago

Hi, I need help with a transaction and position reporting problem. I set up an APIv4 feed to pull transactions into Cointracker but transactions for SHIB5L_USDT and SHIB5S_USDT pairs in December 2021 are not showing up in the APIv4 feed. Further, they don't show up as current holdings even though they are currently held. Other holdings do show up accurately in Cointracker after using the APIv4 to sync. The SHIIB5L_USDT and SHIB5S_USDT first started trading on December 8, 2021.

Please help resolve. Thanks!

revilwang commented 2 years ago

Which method are you using to retrieve the transactions?

marosier commented 2 years ago

Thank you for the response. I used the Cointracker web page ( https://www.cointracker.io/add_wallet?t=gate-io-v2) to add the gate.io wallet contents to my account there.

When I followed the instructions on their website to create a new APIv4 key ( https://help.cointracker.io/en/articles/5654586-integrating-gate-io-with-apiv4-keys) and establish the import of holdings and transactions, transactions and current holdings in those positions are not reflected.

Please let me know if any other questions...

Thanks again, Mark

On Mon, Feb 7, 2022 at 5:28 PM revilwang @.***> wrote:

Which method are you using to retrieve the transactions?

— Reply to this email directly, view it on GitHub https://github.com/gateio/gateapi-go/issues/30#issuecomment-1032148240, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXURP6IB4OXMIVUZ3IUUXA3U2B5UXANCNFSM5NWOYFXQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>