I am aware it was already deprecated. Just surprised to see the API changing on a non-Thursday morning.
I am aware it was already deprecated. Just surprised to see the API changing on a non-Thursday morning.
该用户的聊天记录定位。
I am aware it was already deprecated. Just surprised to see the API changing on a non-Thursday morning.
I am aware it was already deprecated. Just surprised to see the API changing on a non-Thursday morning.
Looks like `category` was removed from the event object?
Looks like `category` was removed from the event object?
I noticed this a while back because my schema has a constraint that a series cannot be an empty string. I just commented out that constraint because it kept being broken.
I noticed this a while back because my schema has a constraint that a series cannot be an empty string. I just commented out that constraint because it kept being broken.
Get Exchange Schedule (https://docs.kalshi.com/api-reference/exchange/get-exchange-schedule) has a `maintenance_windows` property. They have never used this, as far as I know. I don't think they have a process for populating this, so it is another red herring. They most recently posted to <#946568456759812096> (e.g., https://discord.com/channels/871819895443189862/946568456759812096/1507191484137603193) and have used that before. The standard maintenance window is 0300-0500 ET Thursday. This is currently published by the API. (https://external-api.kalshi.com/trade-api/v2/exchange/schedule)
Get Exchange Schedule (https://docs.kalshi.com/api-reference/exchange/get-exchange-schedule) has a `maintenance_windows` property. They have never used this, as far as I know. I don't think they have a process for populating this, so it is another red herring. They most recently posted to <#946568456759812096> (e.g., https://discord.com/channels/871819895443189862/946568456759812096/1507191484137603193) and have used that before. The standard maintenance window is 0300-0500 ET Thursday. This is currently published by the API. (https://external-api.kalshi.com/trade-api/v2/exchange/schedule)
They made a hasty change a couple years ago when they split the exchange into two to support the 2024 election. It is just cleaning up that mess a couple years later.
They made a hasty change a couple years ago when they split the exchange into two to support the 2024 election. It is just cleaning up that mess a couple years later.
Just don’t assume that anything in the documentation is serious.
Just don’t assume that anything in the documentation is serious.
Yes. It is confusing.
Yes. It is confusing.
v2 in the path doesn’t mean the same as v2 in the new endpoints. There are order management endpoints that are v1 in the v2 URL space and v2 in the v2 URL space.
v2 in the path doesn’t mean the same as v2 in the new endpoints. There are order management endpoints that are v1 in the v2 URL space and v2 in the v2 URL space.
The “v1” path has nothing to do with the v2ness of the new endpoints on v2.
The “v1” path has nothing to do with the v2ness of the new endpoints on v2.