You say you have gone through all pages via the cursor. Is the value of ‘cursor’ different for each page? Or are pages 3, 4, … identical to page 2?
I had the same issue, and it seems to be related to the cursor value not functioning properly. To fetch all transactions, simply replace the cursor with the timestamp of the last returned transaction. I’ve started developing a Python library to address this problem (still a work in progress).
“To fetch all transactions, simply replace the cursor with the timestamp of the last returned transaction.”
Sadly it’s not quite that simple. The cursor should be the executed timestamp – but that field is not populated.
My solution is to match up the record in the CSV statement and get the executed datetime from there.
Alternatively, if the record you look at was a purchase, there’s a good likelihood it had a tax charge – within there is a timestamp that is probably identical to the order executed timestamp.
API reports wrong ticker
The portfolio endpoint (/api/v0/equity/portfolio)
says “BVS” when it means ‘VTY’,
and says “PMO” when it means ‘HBR’.
The mind boggles how that is even possible.
The ‘history/orders’ endpoint has the same bug, so it might be across all endpoints.
Has anyone been getting 400 “Bad Request” error for Request to delete a pie?
Example url passed is https://demo.trading212.com/api/v0/equity/pies/544186
I use DELETE method.
Based on the doc (https://t212public-api-docs.redoc.ly/#operation/delete), integer type pie id seems be sufficient. Any idea how to resolve it or do you think it is the backend issue?