Or provide users with an alternative way of fetching their account data.
Or provide users with an alternative way of fetching their account data.
该用户的聊天记录定位。
Or provide users with an alternative way of fetching their account data.
Or provide users with an alternative way of fetching their account data.
<@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?
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.
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.
most of polymarket customers are losing traders and near-break-even traders, so inflating stated pnl numbers was probably helping retention
most of polymarket customers are losing traders and near-break-even traders, so inflating stated pnl numbers was probably helping retention
previously polymarket used to sneakily inflate your pnl by not counting fees
previously polymarket used to sneakily inflate your pnl by not counting fees
gm - thanks for promising to fix this! i want to clarify that the API is broken in a different way than the way you described. you described the current behavior as "ASC just makes the last item (whatever limit you set) your latest activity". i took a video to demonstrate that it does not currently function that way. in the video you can see me run the same query with limit parameter 5, 6, 7, 8, 9, 10, and 15, and you can see that the first item in response is always the same. but when i change the limit parameter to 150, the first item changes. so, sometimes changing the limit parameter causes the first item to change, sometimes it doesn't. i also want to clarify that all of these are extremely old items on a dormant account, so there's nothing actually changing.
gm - thanks for promising to fix this! i want to clarify that the API is broken in a different way than the way you described. you described the current behavior as "ASC just makes the last item (whatever limit you set) your latest activity". i took a video to demonstrate that it does not currently function that way. in the video you can see me run the same query with limit parameter 5, 6, 7, 8, 9, 10, and 15, and you can see that the first item in response is always the same. but when i change the limit parameter to 150, the first item changes. so, sometimes changing the limit parameter causes the first item to change, sometimes it doesn't. i also want to clarify that all of these are extremely old items on a dormant account, so there's nothing actually changing.
Easy way to reproduce the issue: take this query and run it many times using a different limit parameter: https://data-api.polymarket.com/activity?user=0x584eee598b341109592b985c1a253ab044fa090f&limit=3&offset=0&sortBy=TIMESTAMP&start=0&sortDirection=ASC&excludeDepositsWithdrawals=false
Easy way to reproduce the issue: take this query and run it many times using a different limit parameter: https://data-api.polymarket.com/activity?user=0x584eee598b341109592b985c1a253ab044fa090f&limit=3&offset=0&sortBy=TIMESTAMP&start=0&sortDirection=ASC&excludeDepositsWithdrawals=false
and it doesn't show all the items, except sometimes, randomly
and it doesn't show all the items, except sometimes, randomly
so you have broken the API in a way that it just randomly shows random items?
so you have broken the API in a way that it just randomly shows random items?
Example of how the API is broken in a super weird way: - when I ask for my first 2 activity items, it says that the first activity item was a CONVERSION - when I ask for my first 3 activity items, it says that the first activity item was a REWARD - obviously the first result is supposed to be the same result across both of these requests, there is no logical reason it should change - the actual first activity item was neither CONVERSION nor REWARD, it was a DEPOSIT - if i hit these endpoints repeatedly many times over a long time period, it will sometimes correctly show that the first activity item was indeed a DEPOSIT
Example of how the API is broken in a super weird way: - when I ask for my first 2 activity items, it says that the first activity item was a CONVERSION - when I ask for my first 3 activity items, it says that the first activity item was a REWARD - obviously the first result is supposed to be the same result across both of these requests, there is no logical reason it should change - the actual first activity item was neither CONVERSION nor REWARD, it was a DEPOSIT - if i hit these endpoints repeatedly many times over a long time period, it will sometimes correctly show that the first activity item was indeed a DEPOSIT
To reproduce the issues you need `sortDirection=ASC`
To reproduce the issues you need `sortDirection=ASC`
The API currently returns non-deterministic results. It randomly misses trades.
The API currently returns non-deterministic results. It randomly misses trades.
<@624575779023355904> Since you just now announced that you are working on the /activity API, I thought this might be a good time to raise some issues. You said in the announcement that using start=timestamp "works well". It does not. It's completely broken. It used to work just fine 1-2 months ago, but you broke it, and now it no longer works. This is a very bad issue for me because I rely on this API to file my taxes. Luckily I managed to do my taxes for the previous tax period before you broke the API, but I really really hope you will fix it before the next tax period. I'm currently not aware of *any* Polymarket-provided API or web UI feature that successfully exports trades, because all the features that you've built for this are broken. I can produce reproducible examples of broken-ness if that helps.
<@624575779023355904> Since you just now announced that you are working on the /activity API, I thought this might be a good time to raise some issues. You said in the announcement that using start=timestamp "works well". It does not. It's completely broken. It used to work just fine 1-2 months ago, but you broke it, and now it no longer works. This is a very bad issue for me because I rely on this API to file my taxes. Luckily I managed to do my taxes for the previous tax period before you broke the API, but I really really hope you will fix it before the next tax period. I'm currently not aware of *any* Polymarket-provided API or web UI feature that successfully exports trades, because all the features that you've built for this are broken. I can produce reproducible examples of broken-ness if that helps.
depends on city. your question sounds like you might be looking at top left corner in WU. dont look at that. it doesnt come from the airport.
depends on city. your question sounds like you might be looking at top left corner in WU. dont look at that. it doesnt come from the airport.
Does anyone know where I could get pre-clarification announcements programmatically? I've tried these approaches now: - Went through Polymarket API documentation. Nothing there. - Looked through Polymarket web UI to see if there's a page that gives a feed of clarifications or related info. Nothing there. - Tried Discord "follow" feature to relay the posts in Polymarket Discord server <#1179538916504776724> channel to my own server. This Discord feature appears to be broken. Nothing happens and no error message is shown. - Tried to inspect Betmoar network traffic to see where Betmoar is getting its clarifications data, but it has a huge amount of network traffic and I was unable to find the clarification data anywhere in there. It's somewhere, yes, but I can't find it.
Does anyone know where I could get pre-clarification announcements programmatically? I've tried these approaches now: - Went through Polymarket API documentation. Nothing there. - Looked through Polymarket web UI to see if there's a page that gives a feed of clarifications or related info. Nothing there. - Tried Discord "follow" feature to relay the posts in Polymarket Discord server <#1179538916504776724> channel to my own server. This Discord feature appears to be broken. Nothing happens and no error message is shown. - Tried to inspect Betmoar network traffic to see where Betmoar is getting its clarifications data, but it has a huge amount of network traffic and I was unable to find the clarification data anywhere in there. It's somewhere, yes, but I can't find it.