PolymarketHi Poly, I would like to report an issue regarding the /data/orders API endpoint. During testing, I noticed that the API response is not always consistent. For the same user and under similar conditions, the endpoint sometimes returns the expected open orders data, while at other times it returns an empty response even though open orders exist. For authentication, I am sending all required headers with the request: - POLY_ADDRESS - POLY_API_KEY - POLY_PASSPHRASE - POLY_SIGNATURE - POLY_TIMESTAMP The request is authenticated successfully, but the response from /data/orders still appears to be unreliable, as it occasionally returns empty results where I would expect active/open orders to be returned. Could you please clarify: - Is there any known issue or limitation with the /data/orders endpoint? - Are there any caching mechanisms, indexing delays, or synchronisation delays that could cause intermittent empty responses? - Is there a recommended polling interval or best practice for retrieving open orders reliably? - Is there an alternative endpoint that should be used for obtaining the most up-to-date open orders? Any details regarding the expected behaviour of this endpoint would be greatly appreciated, as we are trying to determine whether this behaviour is expected or if there is an issue with our implementation. Thank you.
Hi Poly, I would like to report an issue regarding the /data/orders API endpoint. During testing, I noticed that the API response is not always consistent. For the same user and under similar conditions, the endpoint sometimes returns the expected open orders data, while at other times it returns an empty response even though open orders exist. For authentication, I am sending all required headers with the request: - POLY_ADDRESS - POLY_API_KEY - POLY_PASSPHRASE - POLY_SIGNATURE - POLY_TIMESTAMP The request is authenticated successfully, but the response from /data/orders still appears to be unreliable, as it occasionally returns empty results where I would expect active/open orders to be returned. Could you please clarify: - Is there any known issue or limitation with the /data/orders endpoint? - Are there any caching mechanisms, indexing delays, or synchronisation delays that could cause intermittent empty responses? - Is there a recommended polling interval or best practice for retrieving open orders reliably? - Is there an alternative endpoint that should be used for obtaining the most up-to-date open orders? Any details regarding the expected behaviour of this endpoint would be greatly appreciated, as we are trying to determine whether this behaviour is expected or if there is an issue with our implementation. Thank you.