该用户的聊天记录定位。
I think if the getTrades results are sorted by match_time, I can use the before and after parameters to paginate through the entire trade history and retrieve all trades for a given token_id.
I think if the getTrades results are sorted by match_time, I can use the before and after parameters to paginate through the entire trade history and retrieve all trades for a given token_id.
I am using the getTrades API to calculate the total number of shares filled for a specific token_id. I noticed that the current limit is 100 records. Is there a way to retrieve all trades for a token_id? If pagination is required, what is the recommended way to fetch all pages and ensure I don't miss any trades?
I am using the getTrades API to calculate the total number of shares filled for a specific token_id. I noticed that the current limit is 100 records. Is there a way to retrieve all trades for a token_id? If pagination is required, what is the recommended way to fetch all pages and ensure I don't miss any trades?
Hi everyone. For the getTrades API, what field is used for sorting the results by default?
Hi everyone. For the getTrades API, what field is used for sorting the results by default?
thank you
thank you
Hi everyone. I place a limit order and use clob.get_balance_allowance() to check how many tokens/shares have been filled. When the order expires, I call cancelAllOrders() to make sure all remaining orders are canceled. After that, I keep checking the balance for about 1 minute (every 5 seconds) using clob.get_balance_allowance(). During that period, it always returns 0, so I assume nothing was filled. However, in some cases, the order was actually partially filled (for example, 10 shares were filled), even though get_balance_allowance() kept returning 0. This issue happens occasionally. Is there any delay, caching, or synchronization issue that could cause get_balance_allowance() to not immediately reflect recently filled shares after an order expires or is canceled? What is the recommended way to reliably detect filled shares in this situation?
Hi everyone. I place a limit order and use clob.get_balance_allowance() to check how many tokens/shares have been filled. When the order expires, I call cancelAllOrders() to make sure all remaining orders are canceled. After that, I keep checking the balance for about 1 minute (every 5 seconds) using clob.get_balance_allowance(). During that period, it always returns 0, so I assume nothing was filled. However, in some cases, the order was actually partially filled (for example, 10 shares were filled), even though get_balance_allowance() kept returning 0. This issue happens occasionally. Is there any delay, caching, or synchronization issue that could cause get_balance_allowance() to not immediately reflect recently filled shares after an order expires or is canceled? What is the recommended way to reliably detect filled shares in this situation?
I place a limit order and use clob.get_balance_allowance() to check how many tokens/shares have been filled. When the order expires, I call cancelAllOrders() to make sure all remaining orders are canceled. After that, I keep checking the balance for about 1 minute (every 5 seconds) using clob.get_balance_allowance(). During that period, it always returns 0, so I assume nothing was filled. However, in some cases, the order was actually partially filled (for example, 10 shares were filled), even though get_balance_allowance() kept returning 0. This issue happens occasionally. Is there any delay, caching, or synchronization issue that could cause get_balance_allowance() to not immediately reflect recently filled shares after an order expires or is canceled? What is the recommended way to reliably detect filled shares in this situation?
I place a limit order and use clob.get_balance_allowance() to check how many tokens/shares have been filled. When the order expires, I call cancelAllOrders() to make sure all remaining orders are canceled. After that, I keep checking the balance for about 1 minute (every 5 seconds) using clob.get_balance_allowance(). During that period, it always returns 0, so I assume nothing was filled. However, in some cases, the order was actually partially filled (for example, 10 shares were filled), even though get_balance_allowance() kept returning 0. This issue happens occasionally. Is there any delay, caching, or synchronization issue that could cause get_balance_allowance() to not immediately reflect recently filled shares after an order expires or is canceled? What is the recommended way to reliably detect filled shares in this situation?
I place a limit order and use clob.get_balance_allowance() to check how many tokens/shares have been filled. When the order expires, I call cancelAllOrders() to make sure all remaining orders are canceled. After that, I keep checking the balance for about 1 minute (every 5 seconds) using clob.get_balance_allowance(). During that period, it always returns 0, so I assume nothing was filled. However, in some cases, the order was actually partially filled (for example, 10 shares were filled), even though get_balance_allowance() kept returning 0. This issue happens occasionally. Is there any delay, caching, or synchronization issue that could cause get_balance_allowance() to not immediately reflect recently filled shares after an order expires or is canceled? What is the recommended way to reliably detect filled shares in this situation?
I place a limit order and use clob.get_balance_allowance() to check how many tokens/shares have been filled. When the order expires, I call cancelAllOrders() to make sure all remaining orders are canceled. After that, I keep checking the balance for about 1 minute (every 5 seconds) using clob.get_balance_allowance(). During that period, it always returns 0, so I assume nothing was filled. However, in some cases, the order was actually partially filled (for example, 10 shares were filled), even though get_balance_allowance() kept returning 0. This issue happens occasionally. Is there any delay, caching, or synchronization issue that could cause get_balance_allowance() to not immediately reflect recently filled shares after an order expires or is canceled? What is the recommended way to reliably detect filled shares in this situation?
Polymarket