2026-06-25 · Kalshi · 51 条相关讨论
Did the ws user order update object change? I swear it used to have a `status` property for resting, canceled, and executed. https://docs.kalshi.com/margin-ws/websockets/user-orders
Did the ws user order update object change? I swear it used to have a `status` property for resting, canceled, and executed. https://docs.kalshi.com/margin-ws/websockets/user-orders
It does have `status` or at least I implemented it that way and it has worked. Currently expecting `resting`, `executed`, or `canceled`. Strange that it doesn't seem to be in the docs...
It does have `status` or at least I implemented it that way and it has worked. Currently expecting `resting`, `executed`, or `canceled`. Strange that it doesn't seem to be in the docs...
When in doubt or maybe always, just look at the actual raw payload 😅
When in doubt or maybe always, just look at the actual raw payload 😅
The docs are completely different from a couple of weeks ago...not sure what I can trust lol
The docs are completely different from a couple of weeks ago...not sure what I can trust lol
<@726121864438481027> do you have a raw payload you could verify?
<@726121864438481027> do you have a raw payload you could verify?
Yeah I'll give it a test shortly to confirm, now I'm wondering...
Yeah I'll give it a test shortly to confirm, now I'm wondering...
I know it used to have it, but I turned off my order placement for a bit.
I know it used to have it, but I turned off my order placement for a bit.
I could share the data model I was using previously.
I could share the data model I was using previously.
My code assumes a status field so it must have been there before
My code assumes a status field so it must have been there before
I don't rely on the status field for much so not certain
I don't rely on the status field for much so not certain
I tested an order, here's the raw payload. Status is present. ``` { "type": "user_order", "sid": 1, "msg": { "order_id": "11111111-1111-1111-1111-111111111111", "user_id": "22222222-2222-2222-2222-222222222222", "ticker": "KXWCGAME-26JUN24SUICAN-TIE", "status": "resting", "side": "yes", "is_yes": true, "outcome_side": "yes", "book_side": "bid", "yes_price_dollars": "0.0300", "fill_count_fp": "0.00", "remaining_count_fp": "1.00", "initial_count_fp": "1.00", "taker_fill_cost_dollars": "0.000000", "maker_fill_cost_dollars": "0.000000", "taker_fees_dollars": "0.000000", "maker_fees_dollars": "0.000000", "client_order_id": "sandbox-user-orders-raw-1782333000205306", "self_trade_prevention_type": "maker", "created_time": "2026-06-24T20:30:00.366574Z", "last_update_time": "2026-06-24T20:30:00.366574Z", "created_ts_ms": 1782333000366, "last_updated_ts_ms": 1782333000366, "subaccount_number": 0 } } ```
I tested an order, here's the raw payload. Status is present. ``` { "type": "user_order", "sid": 1, "msg": { "order_id": "11111111-1111-1111-1111-111111111111", "user_id": "22222222-2222-2222-2222-222222222222", "ticker": "KXWCGAME-26JUN24SUICAN-TIE", "status": "resting", "side": "yes", "is_yes": true, "outcome_side": "yes", "book_side": "bid", "yes_price_dollars": "0.0300", "fill_count_fp": "0.00", "remaining_count_fp": "1.00", "initial_count_fp": "1.00", "taker_fill_cost_dollars": "0.000000", "maker_fill_cost_dollars": "0.000000", "taker_fees_dollars": "0.000000", "maker_fees_dollars": "0.000000", "client_order_id": "sandbox-user-orders-raw-1782333000205306", "self_trade_prevention_type": "maker", "created_time": "2026-06-24T20:30:00.366574Z", "last_update_time": "2026-06-24T20:30:00.366574Z", "created_ts_ms": 1782333000366, "last_updated_ts_ms": 1782333000366, "subaccount_number": 0 } } ```
ty, I wonder if they're planning on phasing out the fields then?
ty, I wonder if they're planning on phasing out the fields then?
Just came to say I'm receiving it as well
Just came to say I'm receiving it as well
It would be extremely strange to remove it.
It would be extremely strange to remove it.
The doc changes somewhat correspond with the V2 order API changes.
The doc changes somewhat correspond with the V2 order API changes.
Some statuses can't be inferred afaict so it would require an API call to fill in.
Some statuses can't be inferred afaict so it would require an API call to fill in.
Depends how bad this would be for them in that it depends on how much people are relying on REST vs WS for their order tracking
Depends how bad this would be for them in that it depends on how much people are relying on REST vs WS for their order tracking
Is there anyone we can ping to confirm why the docs are different from the payload rn?
Is there anyone we can ping to confirm why the docs are different from the payload rn?
I see `status` in `userOrderPayload` appearing in asyncapi.yaml in my git repository on 2026-02-17 and it is gone on 2026-04-10.
I see `status` in `userOrderPayload` appearing in asyncapi.yaml in my git repository on 2026-02-17 and it is gone on 2026-04-10.
I know it was on the website still (status) at some point in june.
I know it was on the website still (status) at some point in june.