No, DESC does not work for the purpose of extracting account history for tax purposes. Polymarket does not allow using offset values of more than 3500, which means you will be able to get the 3500 most recent activity items, but you will not be able to fetch data older than that. Theoretically, you should be able to do it by tinkering with the `start=<timestamp>`, but it does not work.
No, DESC does not work for the purpose of extracting account history for tax purposes. Polymarket does not allow using offset values of more than 3500, which means you will be able to get the 3500 most recent activity items, but you will not be able to fetch data older than that. Theoretically, you should be able to do it by tinkering with the `start=<timestamp>`, but it does not work.
The data API maintenance that you did today appears to have been unsuccessful. I am still unable to fetch my account history with the data API. I am unable to fetch it with ASC. I am unable to fetch it with DESC. I am unable to fetch it with the web ui feature.
The data API maintenance that you did today appears to have been unsuccessful. I am still unable to fetch my account history with the data API. I am unable to fetch it with ASC. I am unable to fetch it with DESC. I am unable to fetch it with the web ui feature.
<@624575779023355904> If you are unable to fix the bugs, can you just please revert back to the implementation you had 1-2 months ago, since that was working?
<@624575779023355904> If you are unable to fix the bugs, can you just please revert back to the implementation you had 1-2 months ago, since that was working?
Or provide users with an alternative way of fetching their account data.
Or provide users with an alternative way of fetching their account data.
Thanks that's very detailed !
Fortunately/Unfortunately I am taking over the data engineering platform and there's a lot to do to move enterprise grade API delivery.
We've worked on this today and this will come in the next release (tomorrow). I'll make sure to update the (very outdated) docs on polymarket for the endpoint.
This fix sorting, and as for the documentation, make sure you read the start/end parameters, especially the default start parameter that prune partitions to 3 years old of data.
I'll be doing a full sweep of the endpoints in the next few days to spot other inconsistencies.
Thanks that's very detailed !
Fortunately/Unfortunately I am taking over the data engineering platform and there's a lot to do to move enterprise grade API delivery.
We've worked on this today and this will come in the next release (tomorrow). I'll make sure to update the (very outdated) docs on polymarket for the endpoint.
This fix sorting, and as for the documentation, make sure you read the start/end parameters, especially the default start parameter that prune partitions to 3 years old of data.
I'll be doing a full sweep of the endpoints in the next few days to spot other inconsistencies.
**Cursor-based pagination (instead of offset)**
-> This is already in scope;; we've implemented this already, though it requires a breaking change as it would totally change both endpoint's response (given how api response was created ---- flat array..).
The improvement with this is pretty massive in terms of performance, especially for large offset.
That should also unblock the fact to go full history on trades.
The `/v1/positions/combos` & `/v1/activity/combos` endpoints already holds the cursor keyset pagination feature and this is what will be coming in the next few weeks for /trades & /positions.
**Cursor-based pagination (instead of offset)**
-> This is already in scope;; we've implemented this already, though it requires a breaking change as it would totally change both endpoint's response (given how api response was created ---- flat array..).
The improvement with this is pretty massive in terms of performance, especially for large offset.
That should also unblock the fact to go full history on trades.
The `/v1/positions/combos` & `/v1/activity/combos` endpoints already holds the cursor keyset pagination feature and this is what will be coming in the next few weeks for /trades & /positions.
can confirm just had this issue, docs isnt updated
can confirm just had this issue, docs isnt updated