该用户的聊天记录定位。
A long time
A long time
Yes
Yes
Hi Polymarket team, I’ve been frequently receiving 500 and 503 Error responses from the Gamma API when paginating through closed markets using the /markets/keyset endpoint. ``` Status: 500 Reason: Internal Server Error URL: https://gamma-api.polymarket.com/markets/keyset?include_tag=true&order=volume1wk&ascending=false&limit=100&closed=true&after_cursor=fzV1L43TuNHvTVQIkc8_hsN6crg1g6TVpk5dw_pRi8B7InYiOjEsImsiOiJtYXJrZXRzIiwib2giOiIzNjk5MDQ2ZDU5OWQ4NjQ5OGEwOTQ2ZjJiMjFlMjZjMGUyYTc3N2FhMGVkZDE3YWIyNDBmZmYyYmI5ZDEzMGZlIiwia2V5cyI6W3sidCI6ImZsb2F0IiwidiI6MTkxMjY3NS45NDQ4MzkwMDA3fSx7InQiOiJzdHJpbmciLCJ2IjoiNjQ4MDk3In1dfQ Params: {'include_tag': 'true', 'order': 'volume1wk', 'ascending': 'false', 'limit': '100', 'closed': 'true', 'after_cursor': 'fzV1L43TuNHvTVQIkc8_hsN6crg1g6TVpk5dw_pRi8B7InYiOjEsImsiOiJtYXJrZXRzIiwib2giOiIzNjk5MDQ2ZDU5OWQ4NjQ5OGEwOTQ2ZjJiMjFlMjZjMGUyYTc3N2FhMGVkZDE3YWIyNDBmZmYyYmI5ZDEzMGZlIiwia2V5cyI6W3sidCI6ImZsb2F0IiwidiI6MTkxMjY3NS45NDQ4MzkwMDA3fSx7InQiOiJzdHJpbmciLCJ2IjoiNjQ4MDk3In1dfQ'} Headers: {'Date': 'Thu, 25 Jun 2026 17:00:33 GMT', 'Content-Type': 'application/json', 'Content-Length': '58', 'Connection': 'keep-alive', 'Set-Cookie': '__cf_bm=PRB4_nZ8ozgYWJNi2wdEJ2x3Eo5A2KUlL7TpEtvo7PE-1782406831.350107-1.0.1.1-ulunroUeQftfy2kKASxM9ZWqeaUASb.GAPsazAfEZQ_xJv2RLoiUn_NG.lQaeI9CiDW1yU1cC.Lat41TwAtUnjME49In5dqPfS1gTntpF9evi9DjGUlZtlan0DNTMxrE; HttpOnly; SameSite=None; Secure; Path=/; Domain=polymarket.com; Expires=Thu, 25 Jun 2026 17:30:33 GMT', 'Vary': 'Origin, accept-encoding', 'cf-cache-status': 'BYPASS', 'Strict-Transport-Security': 'max-age=7776000; includeSubDomains', 'Server': 'cloudflare', 'CF-RAY': 'a1158767ea65e046-FRA', 'alt-svc': 'h3=":443"; ma=86400'} Response body: {"type":"internal error","error":"internal server error"} ```
Hi Polymarket team, I’ve been frequently receiving 500 and 503 Error responses from the Gamma API when paginating through closed markets using the /markets/keyset endpoint. ``` Status: 500 Reason: Internal Server Error URL: https://gamma-api.polymarket.com/markets/keyset?include_tag=true&order=volume1wk&ascending=false&limit=100&closed=true&after_cursor=fzV1L43TuNHvTVQIkc8_hsN6crg1g6TVpk5dw_pRi8B7InYiOjEsImsiOiJtYXJrZXRzIiwib2giOiIzNjk5MDQ2ZDU5OWQ4NjQ5OGEwOTQ2ZjJiMjFlMjZjMGUyYTc3N2FhMGVkZDE3YWIyNDBmZmYyYmI5ZDEzMGZlIiwia2V5cyI6W3sidCI6ImZsb2F0IiwidiI6MTkxMjY3NS45NDQ4MzkwMDA3fSx7InQiOiJzdHJpbmciLCJ2IjoiNjQ4MDk3In1dfQ Params: {'include_tag': 'true', 'order': 'volume1wk', 'ascending': 'false', 'limit': '100', 'closed': 'true', 'after_cursor': 'fzV1L43TuNHvTVQIkc8_hsN6crg1g6TVpk5dw_pRi8B7InYiOjEsImsiOiJtYXJrZXRzIiwib2giOiIzNjk5MDQ2ZDU5OWQ4NjQ5OGEwOTQ2ZjJiMjFlMjZjMGUyYTc3N2FhMGVkZDE3YWIyNDBmZmYyYmI5ZDEzMGZlIiwia2V5cyI6W3sidCI6ImZsb2F0IiwidiI6MTkxMjY3NS45NDQ4MzkwMDA3fSx7InQiOiJzdHJpbmciLCJ2IjoiNjQ4MDk3In1dfQ'} Headers: {'Date': 'Thu, 25 Jun 2026 17:00:33 GMT', 'Content-Type': 'application/json', 'Content-Length': '58', 'Connection': 'keep-alive', 'Set-Cookie': '__cf_bm=PRB4_nZ8ozgYWJNi2wdEJ2x3Eo5A2KUlL7TpEtvo7PE-1782406831.350107-1.0.1.1-ulunroUeQftfy2kKASxM9ZWqeaUASb.GAPsazAfEZQ_xJv2RLoiUn_NG.lQaeI9CiDW1yU1cC.Lat41TwAtUnjME49In5dqPfS1gTntpF9evi9DjGUlZtlan0DNTMxrE; HttpOnly; SameSite=None; Secure; Path=/; Domain=polymarket.com; Expires=Thu, 25 Jun 2026 17:30:33 GMT', 'Vary': 'Origin, accept-encoding', 'cf-cache-status': 'BYPASS', 'Strict-Transport-Security': 'max-age=7776000; includeSubDomains', 'Server': 'cloudflare', 'CF-RAY': 'a1158767ea65e046-FRA', 'alt-svc': 'h3=":443"; ma=86400'} Response body: {"type":"internal error","error":"internal server error"} ```
Using Gamma-API
Using Gamma-API
<@707597210845446214>
<@707597210845446214>
Hi, has anything changed recently regarding the Gamma API rate limits? I’ve seen some users reporting similar issues, and I’m currently experiencing the same problem. Requests that used to work normally are now intermittently returning `429 Too Many Requests` Just wanted to confirm whether there was any recent change in the rate limit policy or API behavior.
Hi, has anything changed recently regarding the Gamma API rate limits? I’ve seen some users reporting similar issues, and I’m currently experiencing the same problem. Requests that used to work normally are now intermittently returning `429 Too Many Requests` Just wanted to confirm whether there was any recent change in the rate limit policy or API behavior.
Got it. Which `settlements` endpoint are you referring to exactly?
Got it. Which `settlements` endpoint are you referring to exactly?
Oh shit. How do you usually work around this and recalculate the correct PnL?
Oh shit. How do you usually work around this and recalculate the correct PnL?
I found a bug in the Polymarket API related to the World Cup event. Some winning wallets are not having their values updated correctly in the `/closed_positions` route. Even after winning and redeeming thousands of dollars, the route shows `realized_pnl` as zero and `current_price` as 1. When comparing this with the `https://data-api.polymarket.com/activity` route, we noticed that the issue occurs because the `closed_position` update date only takes into account the date of the last trade before the redemption. Wallet - 0x084425dedaa0a4d92164adb33b294005518df46a condition - 0xCE19DE12B7C2D024A682D407F84B9A6EA91B77872B95758FDA4B0FA928368C9B
I found a bug in the Polymarket API related to the World Cup event. Some winning wallets are not having their values updated correctly in the `/closed_positions` route. Even after winning and redeeming thousands of dollars, the route shows `realized_pnl` as zero and `current_price` as 1. When comparing this with the `https://data-api.polymarket.com/activity` route, we noticed that the issue occurs because the `closed_position` update date only takes into account the date of the last trade before the redemption. Wallet - 0x084425dedaa0a4d92164adb33b294005518df46a condition - 0xCE19DE12B7C2D024A682D407F84B9A6EA91B77872B95758FDA4B0FA928368C9B
I found a bug in the Polymarket API related to the World Cup event. Some winning wallets are not having their values updated correctly in the `/closed_positions` route. Even after winning and redeeming thousands of dollars, the route shows `realized_pnl` as zero and `current_price` as 1. When comparing this with the `https://data-api.polymarket.com/activity` route, we noticed that the issue occurs because the `closed_position` update date only takes into account the date of the last trade before the redemption. Wallet - 0x084425dedaa0a4d92164adb33b294005518df46a condition - 0xCE19DE12B7C2D024A682D407F84B9A6EA91B77872B95758FDA4B0FA928368C9B
I found a bug in the Polymarket API related to the World Cup event. Some winning wallets are not having their values updated correctly in the `/closed_positions` route. Even after winning and redeeming thousands of dollars, the route shows `realized_pnl` as zero and `current_price` as 1. When comparing this with the `https://data-api.polymarket.com/activity` route, we noticed that the issue occurs because the `closed_position` update date only takes into account the date of the last trade before the redemption. Wallet - 0x084425dedaa0a4d92164adb33b294005518df46a condition - 0xCE19DE12B7C2D024A682D407F84B9A6EA91B77872B95758FDA4B0FA928368C9B