Thanks a lot for the help, really appreciate it
Thanks a lot for the help, really appreciate it
该用户的聊天记录定位。
Thanks a lot for the help, really appreciate it
Thanks a lot for the help, really appreciate it
Strange, tried again just now using same code and it works now
Strange, tried again just now using same code and it works now
OK it does reject the request without time_in_force field: Error: 400 - {"error":{"code":"missing_parameters","message":"missing parameters","details":"Key: 'CreateOrderV2Request.TimeInForce' Error:Field validation for 'TimeInForce' failed on the 'required' tag"}}
OK it does reject the request without time_in_force field: Error: 400 - {"error":{"code":"missing_parameters","message":"missing parameters","details":"Key: 'CreateOrderV2Request.TimeInForce' Error:Field validation for 'TimeInForce' failed on the 'required' tag"}}
It should as time_in_force is a required field. To create a good-til-cancel order with expiration time from Kalshi webpage, I need to select Custom as time_in_force though. Custom is not listed as a valid API value so I am wondering there might be a bug.
It should as time_in_force is a required field. To create a good-til-cancel order with expiration time from Kalshi webpage, I need to select Custom as time_in_force though. Custom is not listed as a valid API value so I am wondering there might be a bug.
i.e., the order is a true good-til-cancel order
i.e., the order is a true good-til-cancel order
The request goes through with expiration_time set, it is just not picked up Kalshi
The request goes through with expiration_time set, it is just not picked up Kalshi
The document says: To place an expiring order, set time_in_force to good_till_canceled and provide this expiration_time.
The document says: To place an expiring order, set time_in_force to good_till_canceled and provide this expiration_time.
Is anybody having issue with time_in_force + expiration_time combination? I am sending REST request according to the documentation but it is silently failing behind the scenes
Is anybody having issue with time_in_force + expiration_time combination? I am sending REST request according to the documentation but it is silently failing behind the scenes