聊天记录
共 3 条,显示第 1-3 条
https://polymarket.com/api/chainlink-candles?symbol=SOL&interval=5m&limit=15&endTime=1782975899999 shows ```{"error":"limit must be 30"}```
https://polymarket.com/api/chainlink-candles?symbol=SOL&interval=5m&limit=30&endTime=1782975899999
it works when I change it to 30, but if I remove limit I get the same error:
https://polymarket.com/api/chainlink-candles?symbol=SOL&interval=5m&endTime=1782975899999
what's the point? if limit must always be 30 then why even include it as a parameter? Why not just remove it altogether?
https://polymarket.com/api/chainlink-candles?symbol=SOL&interval=5m&limit=15&endTime=1782975899999 shows ```{"error":"limit must be 30"}```
https://polymarket.com/api/chainlink-candles?symbol=SOL&interval=5m&limit=30&endTime=1782975899999
it works when I change it to 30, but if I remove limit I get the same error:
https://polymarket.com/api/chainlink-candles?symbol=SOL&interval=5m&endTime=1782975899999
what's the point? if limit must always be 30 then why even include it as a parameter? Why not just remove it altogether?
Please add optional start_time and end_time params to the api for /closed_positions, /positions and /trades because currently it returns ~5000 rows which is incomplete. Adding date filters would mean it can return the complete results and require fewer api calls
Please add optional start_time and end_time params to the api for /closed_positions, /positions and /trades because currently it returns ~5000 rows which is incomplete. Adding date filters would mean it can return the complete results and require fewer api calls
wtf is this? Bitcoin Up or Down - June 7, 8:00PM-8:05PM ET. The websocket lagged by nearly 45 seconds! In this image the red line is the actual on-chain trade, the yellow line is the bitcoin price change - they both match. Green line is the ask and the dots are simulated orders along the Ask. For nearly a minute the websockets, both orderbook and trades lagged massively behind. It caught up after. How are we supposed to trade like this if the live price information is that stale???
wtf is this? Bitcoin Up or Down - June 7, 8:00PM-8:05PM ET. The websocket lagged by nearly 45 seconds! In this image the red line is the actual on-chain trade, the yellow line is the bitcoin price change - they both match. Green line is the ask and the dots are simulated orders along the Ask. For nearly a minute the websockets, both orderbook and trades lagged massively behind. It caught up after. How are we supposed to trade like this if the live price information is that stale???