秋田预测市场 · Discord 审计

API v3订单行为与WebSocket成交报告不一致问题

2026-07-15 · Kalshi · 4 条相关讨论

MisakaIsNameless 2026-07-15 01:14:20

I am a bit confused about the newest API version. I can no longer place limit NO bid orders at 45 cents through the API. Instead, I have to submit limit YES sell orders at 55 cents. If those orders get filled, what will the WebSocket report? Will it tell me that I sold YES at 55 cents, or that I bought NO at 45 cents? Though I understand these two trades are mathematically equivalent. Sometimes I see that I "bought NO," while other times it looks like I "sold YES." Is this expected behavior, and what is the correct way to interpret the WebSocket fills in the latest API version?

I am a bit confused about the newest API version. I can no longer place limit NO bid orders at 45 cents through the API. Instead, I have to submit limit YES sell orders at 55 cents. If those orders get filled, what will the WebSocket report? Will it tell me that I sold YES at 55 cents, or that I bought NO at 45 cents? Though I understand these two trades are mathematically equivalent. Sometimes I see that I "bought NO," while other times it looks like I "sold YES." Is this expected behavior, and what is the correct way to interpret the WebSocket fills in the latest API version?

betaclone 2026-07-15 01:26:19

I'm not sure why action is still being reported anywhere. Ignore it. The important fields are book_side and outcome_side

I'm not sure why action is still being reported anywhere. Ignore it. The important fields are book_side and outcome_side

betaclone 2026-07-15 01:26:41

Practically, book_side is all that matters really

Practically, book_side is all that matters really

betaclone 2026-07-15 01:27:46

But outcome_side will align with market_result when the ticker closes

But outcome_side will align with market_result when the ticker closes