Closed mess-maker closed 5 months ago
Thanks for the report again. Unfortunately, the response from TR is so unstructured, since it was designed for webapp and mobile app rendering, so it does not have fixed structure. Here it fails because it expects a portion of JSON to exist in the response while it's not. I will divide it into 2 split fixes:
Thanks again!
Could you please help me with the transaction 50? I would like to understand what "Basiswert: CAC" means in this case. Is this something that should end up in the csv file or it is not important? I am asking because I never owned such instruments. Thanks in advance!
hi thanks for thoose fix and future one
for the transaction 50 the product is a turbo (can be long or short) it's a leveraged product on and underlying stock or indice (here the underlying is the CAC 40 hence the Basiswert: CAC)
here some explanation on how they work https://www.ig.com/ie/exchange-traded-products/turbo24-trading/what-are-turbo-certificates-how-do-you-trade-them
you can find them in the derivatives section in trade republic (by searching "cac 40" or "S&P 500" for example) I think all derivatives should have this JSON section. By definition they are a derivative of an underlying
Here an ISIN of a comparable product : DE000SW7J4D0 you can search for it in trade republic to have the detailled informations
Thank you for the explanation. I implemented support for these transactions. Please note, that some data is still missing in the csv file as I am planning to add more details later once I better understand these transaction. I would really appreciate if you could run the binary again and let me know if you get more errors as you still may have transactions that the app is not familiar with yet. And one more thing: Transactions that you mentioned earlier: we are planning to add full support for those transactions soon, it just feels like it makes no sense to include those until we implement better calculation of what happens with the money deposited.
Long story short: I hope this fix would finally generate you a full csv with all purchases and sales, deposits will come soon and I can inform you once it is done.
@mess-maker FYI I added including deposit transactions in csv. The latest version v0.6.0 now.
OS LINUX Opensuse Tumbleweed VM on win 11 host
here are the log with ./portfoliodownloader --debug --trace -w with some errors. the program exit after having processed only 50 of the 2k+ transaction
some errors are from deposit that are skipped it's maybe a normal behaviour but it's not clear in the readme if the deposits should be listed in the csv should be great to be able to reconstruct the value over time of the porfolio in external tools to have the deposit and withdraw listed
to lighten the file I've ommited the "OK" transaction and the recurring deposit errors (same as transaction 3 hereunder) and i added the json part corresponding from the ''timeline transactions'' folder
and here the transaction 50.json from ''timelineDetailV2'' folder