聊天记录
共 2 条,显示第 1-2 条
**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.
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.