You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
spec-drift/kalshi: Fill schema — side + action deprecated (May 14 2026); outcome_side, book_side missing #1188
The Kalshi v2 API deprecated side and action on the Fill schema (same May 14, 2026 deadline as Trade) and added outcome_side and book_side as replacements. The PMXT spec (core/specs/kalshi/Kalshi.yaml v3.7.0) retains the deprecated fields and does not include the replacements.
API changes — Fill schema
Deprecated (removal deadline May 14, 2026)
side — was "yes" or "no"
action — was "buy" or "sell"
Added
Field
Type
Description
outcome_side
string
"yes" or "no" — which outcome was filled
book_side
string
"bid" or "ask" — which side of the book was filled
Impact
Any normalizer code reading side or action from fill data may receive null/undefined for fills settled after the deprecation deadline. The new fields are unavailable for P&L or trade direction display.
Spec file
core/specs/kalshi/Kalshi.yaml — Fill schema needs side and action marked deprecated and the two new fields added.
See also: companion issue for Trade schema deprecations (#1187).
Triage: removed P1: high because the Kalshi deprecation deadline (May 14 2026) has now passed — today is June 24 2026, 41 days after the deadline. The side + action fields have been removed from Fill responses and outcome_side / book_side are now required. Fill data is silently wrong or broken in production. Added P0: critical instead.
Triage: removed P0: critical because, unlike the repo's other P0 spec-drift issues (which describe complete request failures or fully broken data), this one's impact is side/action becoming null/undefined on fills — a data-completeness gap affecting P&L/trade-direction display, not a crash or full outage. Added P1: high instead (breaking API change needed, but not production-down).
Closing as duplicate of #514. Same underlying finding: Kalshi's outcome_side/book_side field migration replacing legacy direction-style fields on the Order/Fill/Trade family in core/specs/kalshi/Kalshi.yaml. The Fill-specific detail from this issue (deprecated side/action fields, May 14 2026 deadline) has been copied over to #514 as a comment so it isn't lost.
Activity
realfishsam commentedon Jun 24, 2026
Triage: removed
P1: highbecause the Kalshi deprecation deadline (May 14 2026) has now passed — today is June 24 2026, 41 days after the deadline. Theside+actionfields have been removed from Fill responses andoutcome_side/book_sideare now required. Fill data is silently wrong or broken in production. AddedP0: criticalinstead.Generated by Claude Code
realfishsam commentedon Aug 4, 2026
Triage: removed
P0: criticalbecause, unlike the repo's other P0 spec-drift issues (which describe complete request failures or fully broken data), this one's impact isside/actionbecomingnull/undefinedon fills — a data-completeness gap affecting P&L/trade-direction display, not a crash or full outage. AddedP1: highinstead (breaking API change needed, but not production-down).Generated by Claude Code
realfishsam commentedon Sep 4, 2026
Closing as duplicate of #514. Same underlying finding: Kalshi's
outcome_side/book_sidefield migration replacing legacy direction-style fields on the Order/Fill/Trade family incore/specs/kalshi/Kalshi.yaml. The Fill-specific detail from this issue (deprecatedside/actionfields, May 14 2026 deadline) has been copied over to #514 as a comment so it isn't lost.Generated by Claude Code